In 2018, I founded a startup specializing in chatbot for events. At the time the platforms were Alexa Skills, Actions on Google, and Messenger Platform (and LINE Bot, for people in Asia). I guess what's old is new again, but with fancier tech. This time will be different?
Apps SDK
241–250 of 397 posts
Re: Apps SDK
#242Earlier quoted context omitted.
Yes, because it seems that Zillow exposes those specific filters as a part of the input schema. As long as it's a part of the schema, then ChatGPT can generate a useful input to the widget. But my point is that is very brittle.
Isn't that as brittle as any system being constrained to providing only some type of outputs? Please elaborate.
I think most software will follow this trend and become generated on-demand over the next decade.
Re: Apps SDK
#243I don't understand, what could be built with this platform that wouldn't be made obsolete by conceivable updates to ChatGPT? Another commenter suggested a hotel search function: > Find me hotels in Capetown that have a pool by the beach .Should cost between 200 dollars to 800 dollars a night ChatGPT can already do this. Similarly, their own pizza lookup example seems like it would exist or nearly exist with current f…
Re: Apps SDK
#244A bit underwhelming when you see what's actually on offer. "Apps" are really just MCP servers, with an extension to allow returning HTML. A lot of the fundamental issues with MCP are still present: MCP is pretty single-player, users must "pull" content from the service, and the model of "enabling connections" is fairly unintuitive compared to "opening an app." Ideally apps would have a dedicated entry point, be able…
Once a service can actively involve you and/or your LLM in ongoing interaction, MCP servers start to get real sticky. We can safely assume the install/auth process will also get much less technical as pressure to deliver services to non-technical users increases.
Re: Apps SDK
#245Re: Apps SDK
#246The biggest bottleneck for this for the past two years imo wasn't the models, but the engineering and infra around it, and the willingness of companies to work with openaio directly. Now that they've grown and have a decent userbase, companies are much more willing to pay/or involve themselves in these efforts.
This has eventual implications outside user-heavy internet use (once we see more things built on the SDK), where we're gonna see a fork in the web traffic of human centric workflows through chat, and an seo-filled, chat/agent-optimized web that is only catered to agents. (crossposted)
Re: Apps SDK
#247Earlier quoted context omitted.
> This means OAI won't need ads. Ads are defenitely there. Just hidden so deeply in the black box which is generating the useful tips :)
If you ask it to build a headless frontend web app, it immediately starts generating code with Next.js. I’ve always wondered how it was trained to default to that choice, given the smorgasbord of web frameworks out there. Next.js is solid, but it’s also platform-ware, tightly coupled to commercial interests. I wish there were more bias toward genuinely open-source technologies.
Re: Apps SDK
#248Re: Apps SDK
#249Earlier quoted context omitted.
deploying an app to 700M people?
That's like saying making a website is like deploying an app for 7B people. Sure, but deploying a website or app doesn't mean anyone's going to use it, does it? I could make an iOS app, I could make a website, I could make a ChatGPT app... if no one uses it, it doesn't matter how big the userbase of iOS, the internet, or ChatGPT is...
Re: Apps SDK
#250Why would I want to enable OpenAI to collect an Apple Tax from me down the road? Sure, this helps app partners access their large user base and grows their functionality too - but the end game has to be lock-in with a 30% tax right?