Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Apps SDK

developers.openai.com

Post reply on HN
Print view View original

21–30 of 397 posts

Re: Apps SDK

#21

Post by minimaxir »

naiv wrote: post #3

Remember "GPTs" and the thing before it which I don't even remember now. I think this will go the same route .. to nowhere

The GPT App Store (which is technically now obsolete with this SDK) was funny.

Re: Apps SDK

#22

Post by rushingcreek »

alvis wrote: post #18
rushingcreek wrote: post #6

I think this is very interesting, but it is reminiscent of what we built with Phind 2 where the answer could include dynamic, pre-built widgets. The problem with this approach is precisely that these apps/widgets have hard-coded input and output schema. They can work quite well when the user asks something within the widget's capabilities, but the brittleness of this approach starts showing quickly in real-world use.…

Given there is already a MCP-UI project, I’m not surprised it can be done. But even that I’m not very convinced that it’s the right approach. After all, it’s still far too slow for real usage…

Totally agree that it's too slow with conventional approaches, which is why we're training custom models for this that we can run fast

Re: Apps SDK

#23

Post by [deleted] »

markab21 wrote: post #11

The skepticism is understandable given the trajectory of GPTs and custom instructions, but there's a meaningful technical difference here: the Apps SDK is built on the Model Context Protocol (MCP), which is an open specification rather than a proprietary format. MCP standardizes how LLM clients connect to external tools—defining wire formats, authentication flows, and metadata schemas. This means apps you build aren'…

[deleted]

Re: Apps SDK

#24

Post by rushingcreek »

chatmasta wrote: post #16
rushingcreek wrote: post #6

I think this is very interesting, but it is reminiscent of what we built with Phind 2 where the answer could include dynamic, pre-built widgets. The problem with this approach is precisely that these apps/widgets have hard-coded input and output schema. They can work quite well when the user asks something within the widget's capabilities, but the brittleness of this approach starts showing quickly in real-world use.…

Phind is awesome. I often forget to use it until legacy search engines fail to surface what I’m looking for after a dozen searches. Phind usually finds it. That said, I used it a lot more a year ago. Lately I’ve been using regular LLMs since they’ve gotten better at searching.

Thanks for the feedback. I think that our main differentiator going forward will be this generative UI on the fly for answering questions as opposed to search alone.

Re: Apps SDK

#25

Post by disiplus »

Honestly I see how somebody like kayak.com would build a "app" they work through commission, they don't care from where is the booking coming from. But they will sort the flight tickets based where do they earn the best commission. What's in there for me as a user ?. Also will openai let different providers pay for the top placement when somebody tries to buy ticket on chatgpt ?

Re: Apps SDK

#26

Post by testfrequency »

Wow.

“CEO” Fidji Simo must really need something to do.

Maybe I’m cynical about all of this, but it feels like a whole lot of marketing spin for an MCP standard.

Re: Apps SDK

#27

Post by mhl47 »

p0seidon wrote: post #20
mhl47 wrote: post #12

There was a recent post here about how deeply ingrained the chat interface is in OpenAIs organization. This really doubles down on that, but does anyone really like to interact with so much language instead of visual elements? Also feels horrible that you are supposed to remember a bunch of app names like "zillow" and punch them in the chat. And like an opportunity for them to slowly introduce ads for this apps or "p…

Which post was that?

https://news.ycombinator.com/item?id=44573195 (in the article, search for:"Chat runs really deep")

Re: Apps SDK

#28

Post by babyshake »

rushingcreek wrote: post #6

I think this is very interesting, but it is reminiscent of what we built with Phind 2 where the answer could include dynamic, pre-built widgets. The problem with this approach is precisely that these apps/widgets have hard-coded input and output schema. They can work quite well when the user asks something within the widget's capabilities, but the brittleness of this approach starts showing quickly in real-world use.…

I know that AG-UI from copilot kit is in this space. But it hasn't worked well with the MCP model AFAIK
Post reply on HN