Apps SDK
211–220 of 397 posts
Re: Apps SDK
#212Earlier quoted context omitted.
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.
To me it feels like the default choice in the industry, perhaps it's not and I'm wrong but if I could have that feeling I can see how the AI can as well.
Re: Apps SDK
#213Earlier quoted context omitted.
more abstract than that, "I'm throwing a wedding/funeral/startup IPO/Halloween/birthday party for a whatever year old and need appropriate music". Or, without knowing specific bands, "I want to hear some 80's metal music". "more cowbell!"
You don't need AI for this, Spotify has, like, infinite playlists. Also their playlists are made by real people (mostly...), so they don't completely suck ass.
Also, following the Beatport top 100 tech house playlist, and hearing how many tracks aren't actually tech house makes me wonder about who makes that particular playlist.
Re: Apps SDK
#214Earlier quoted context omitted.
There's a lot of appropriate blowback against stupid AI hype and I'm all for it. But I do think in many respects it's a better interface than (1) bad search results, (2) cluttered websites, (3) freemium apps with upgrade nags, as well as the collective search cost of sorting through all those things. I remember reading some not-Neuromancer book by William Gibson where one of his near-future predictions was print maga…
I think you need to be careful here because you shouldn't be comparing chat apps to the current state of search results. Instead you compare it to the ideal or to the state of them before companies decided that instead of providing what people are looking for it was more profitable to provide them with related content that they're paid to show. We are at a moment where we're trying to figure out how to design good in…
But I think it's going to be like Kagi, you'll pay for a subscription to a good-enough one, but the main companies will try to make their proprietary ones too feature rich and too convenient so that you'll have no choice but to use their enshittified version. What we have now might be a golden age that we will miss having.
But, for better or worse, I do think what's coming may be a paradigm where they are effectively one big omniscient super-app.
Re: Apps SDK
#215This conception makes sense iff you believe in ChatGPT as the universal user interface of the future. If anything the agentic wave is showing that the chat interfaces are better off hidden behind stricter user interface paradigms.
One way to consider it that I like as an EE working in the energy model realm; consider the geometry of an oscilloscope.
Electromagnetism to be carved up into equations that recreate it.
Geometric generators that create bulk structure and allow for changing min/max parameters to achieve desired result.
Consider a hardware system that boots and offers little more than blender and photoshop like parameter UI widgets to manipulate whatever segment of the geometry that isn't quite right.
Currently we rely on an OS paradigm that is basically a virtual machine to noodle strings. The future will be a vector virtual machine that lets users noodle coordinates.
Way less resource intensive to think of it all as sync of memory matrix to display matrix and jettison all the syntax sugar developers stuck with string munging OS of history.
Re: Apps SDK
#216Earlier quoted context omitted.
Yea, I don't want to sit there at my computer, which can handle lots of different input methods, like keyboard, mouse, clicking, dragging, or my phone which can handle gestures, pinching, swiping... and try to articulate what I need it to do in English language conversation. This is actually a step backwards in human-computer interaction. To use an extreme example: imagine instead of a knob on my stereo for volume, I…
It's funny, because the chat bot designers seem to be continually attempting to recreate the voice computer interface from Star Trek: TNG. Yet if you watch the show carefully, the vast majority of the work done by all the Enterprise crew is done via touchscreens, not voice. The only reason for the voice interface is to facilitate the production of a TV show. By having the characters speak their requests aloud to the…
Maybe this is how we all get our own offices again and the open floor plan dies.
Re: Apps SDK
#217Earlier quoted context omitted.
>If anything the agentic wave is showing that the chat interfaces are better off hidden behind stricter user interface paradigms. I'm not sure that claim is justified. The primary agentic use case today is code generation, and the target demographic is used to IDEs/code editors. While that's probably a good chunk of total token usage, it's not representative of the average user's needs or desires. I strongly doubt th…
Having already seen this explored late '24, what ends up happening is that the end user generates apps that have lots of jank, quirks, and logical errors that they lack the ability to troubleshoot or resolve. Like the fast forward button corrupting their settings config, the cloud sync feature causing 100% CPU load, icons gradually drifting away from their original positions on each window resize event, or the GUI tu…
Re: Apps SDK
#218There 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…
counterpoint: a lot of people around me just type "zillow" in google to access it, so maybe it's not absurd to refer to it by name in a chat interface
Re: Apps SDK
#219This 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.
The UI 'cards' will naturally becoming ever increasing, and soon you end up back with a full app within ChatGPT or ChatGPT just becomes an app launcher.
The only advantage I can see is if ChatGPT can use data from other apps/ chats in your searches e.g. find me hotels in NYC for my upcoming trip (and it already knows the types of hotels you like, your budget and your dates)
Re: Apps SDK
#220Lots of folks (myself included) are reporting it doesn't: https://github.com/openai/openai-apps-sdk-examples/issues/1