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.
Apps SDK
51–60 of 397 posts
Re: Apps SDK
#52There 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…
I was really hoping Apple would make some innovations on the UX side, but they certainly haven’t yet.
Re: Apps SDK
#53This feels like the death of the app, and the rise of the micro-app.
Re: Apps SDK
#54Earlier 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
That 1T figure is real, but it includes things like if you buy a refrigerator using the Amazon iOS app.
Re: Apps SDK
#55I 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.…
Conservational user interfaces are opaque; they lack affordances. https://en.wikipedia.org/wiki/Affordance
Re: Apps SDK
#56This 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 "
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
#57Re: Apps SDK
#58Re: Apps SDK
#59I 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
#60In 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?