Live data from Hacker News

Apps SDK

developers.openai.com

51–60 of 397 posts

Re: Apps SDK

#51
post #41

Earlier quoted context omitted.

That figure sounds way too high Edit: yes I understand it is correct, but still it sounds like an insane amount

It's true, though. It is now evident why Flash was murdered.

Because it was buggy, known for security holes and the single biggest source of application crashes in all software in the late 90's through early 00's.

Re: Apps SDK

#52
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…

Very much agreed. I think the dominance of the chat interface to LLMs has materially impaired the general usefulness of these tools — the sooner it goes away the better. It’s almost impossible to explain to a non-engineer how the illusion of a continuous conversation is crafted through context management and why past moments in a conversation might fall out of memory. My general advice to non-technical friends is to create a new conversation for each prompt so that they can get a more deterministic sense of how to formulate instructions and which are successful.

I was really hoping Apple would make some innovations on the UX side, but they certainly haven’t yet.

Re: Apps SDK

#54
post #41

Earlier quoted context omitted.

When the iPhone came out, there were like 6 apps, and no app store. In 2024, iOS App Store generated $1.3T in revenue, 85% of which went to developers.

That figure sounds way too high Edit: yes I understand it is correct, but still it sounds like an insane amount

They're confusing "sales facilitates by the app store" with sales from the app store itself.

That 1T figure is real, but it includes things like if you buy a refrigerator using the Amazon iOS app.

Re: Apps SDK

#55

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.…

The problem is not the limitations of the capabilities per se but their discoverability (https://en.wikipedia.org/wiki/Discoverability). The user doesn't know what the capabilities are, as they are added and -- infuriatingly -- removed. Google Assistant is a perfect example of this.

Conservational user interfaces are opaque; they lack affordances. https://en.wikipedia.org/wiki/Affordance

Re: Apps SDK

#56
post #42

This is honestly useful. "Find me hotels in Capetown that have a pool by the beach .Should cost between 200 dollars to 800 dollars a night "

[injected with guerilla ads]

I don't see how this is a significant upgrade over the many existing hotel-finder tools. At best it slightly augments them as a first pass, but I would still rather look at an actual map of options than trust a stream of generated, ad-augmented text.

Re: Apps SDK

#57
post #41

Earlier quoted context omitted.

That figure sounds way too high Edit: yes I understand it is correct, but still it sounds like an insane amount

https://finance.yahoo.com/news/apples-app-store-generated-ne...

[deleted]

Re: Apps SDK

#58
This feels like a fever dream. As a developer everything changes every week. A new model, a new tool, a new sdk, paradigm we have to learn. I'm getting tired of all that shit.

Re: Apps SDK

#59
post #55

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.…

The problem is not the limitations of the capabilities per se but their discoverability ( https://en.wikipedia.org/wiki/Discoverability ). The user doesn't know what the capabilities are, as they are added and -- infuriatingly -- removed. Google Assistant is a perfect example of this. Conservational user interfaces are opaque; they lack affordances. https://en.wikipedia.org/wiki/Affordance

Yep, this is a big problem as well. If the user doesn't know what features will or won't work, they lose confidence overall.

Re: Apps SDK

#60

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?

We've actually got systems that can understand English now. Chatbots don't have to be glorified regular expression matches or based on inferior NLP. I've thought more than once that the true value of LLMs could well be that they essentially solve the language comprehension problem and that their ability to consume language is relatively underutilized compared to our attempts to get them to produce language. Under all the generative bling their language comprehension and ability to package that into something that conventional computing can understand is pretty impressive. They've even got a certain amount of common sense built in.
Post reply on HN