Live data from Hacker News

Apps SDK

developers.openai.com

111–120 of 397 posts

Re: Apps SDK

#111
post #64
post #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.

Who says you have to learn this? You are free to ignore it if it's overwhelming. I'd much rather see a thriving ecosystem full of competition and innovation than a more stagnant alternative.

For me the most annoying thing is APIs arbitrarily changing all the time. Completely change the entire Tailwind, ESLint, AWS SDK, etc APIs every 6 months? Why not! Heaven forbid you don't touch a project for a few months, blink and all your code is outdated.

Re: Apps SDK

#112

Earlier quoted context omitted.

> I get the impression that's the same reason their fine-tuning services never took off either Also, very few workloads that you'd want to use AI for are prime cases for fine-tuning. We had some cases where we used fine tuning because the work was repetitive enough that FT provided benefits in terms of speed and accuracy, but it was a very limited set of workloads.

> fine tuning because the work was repetitive enough that FT provided benefits in terms of speed and accuracy, can you share anymore info on this. i am curious about what the usecase was and how it improved speed (of inference?) and accuracy.

Very typical e-commerce use cases processing scraped content: product categorization, review sentiment, etc. where the scope is very limited. We would process tens of thousands of these so faster inference with a cheaper model with FT was advantageous.

Disclaimer: this was in the 3.5 Turbo "era" so models like `nano` now might be cheap enough, good enough, fast enough to do this even without FT.

Re: Apps SDK

#113

OpenAI launched an App Store in Nov 2023. A 23 month turnaround from major feature launch, to deprecation, to relaunch is a commitment to product longevity that’d put Google to shame.

product roadmap was also ai generated

Re: Apps SDK

#114

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.

Will this have a revenue share / marketplace built into it?

> Will this have a revenue share / marketplace built into it?

I'm genuinely surprised these companies went with usage-based versus royalty pricing.

Re: Apps SDK

#115

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

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 magazines but with custom printed articles curated to fit your interests. Which is cool! In a world where print magazines were still dominant, you could see it as a forward iteration from the magazine status quo, potentially predictive of a future to come. But what happened in reality was a wholesale leapfrogging of magazines.

So I think you sometimes get leapfrogging rather than iteration, which I suspect is in play as a possibility with AI driven apps. I don't think apps will ever literally be replaced but I think there's a real chance they get displaced by AI everything-interfaces. I think the mitigating factor is not some foundational limit to AI's usefulness but enshittification, which I don't think used to consume good services so voraciously in the 00s or 2010s as it does today. Something tells me we might look back at the current chat based interfaces as the good old days.

Re: Apps SDK

#116
post #37

It’s remarkable that will inevitably rush to build free apps that only reinforce OpenAI’s moat while cannibilizing their own opportunities.

This is nonsense. Why would they destroy the incentive to get real-time, live data and MCP actions that help their users?

Connecting these apps will, at times, require authentication. Where it does not require payment, it's a fantastic distribution channel.

Re: Apps SDK

#117
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.

> We now know why Flash was murdered

This is a stupid conspiracy given Apple decided not to support Flash on iPhone since before Jobs came around on third-party apps. (The iPhone was launched with a vision of Apple-only native apps and HTML5 web apps. The latter's performance forced Cupertino's hand into launching the App Store. Then they saw the golden goose.)

Re: Apps SDK

#118
post #8

Discovery, monetization. What is in it for developers?

deploying an app to 700M people?

Not only do you get to deploy your app to 700M users; you also get to provide responsive support for every single one of them!

Per the docs: 'Every app comes from a verified developer who stands behind their work and provides responsive support'

That's thinly veiled corporate speak for, Fortune 500 or GTFO

Re: Apps SDK

#119

Earlier quoted context omitted.

This has been the pitched playbook for decades. (Metamates!) I'm increasingly convinced its driven by a specific generation of tech entrepreneurs who cut their teeth while reading ca. 1980s science fiction. I could see chat apps becoming dominant in Slack-oriented workplaces. But, like, chatting with an AI to play a song is objectively worse than using Spotify. Dynamically-created music sounds nice until one consider…

Chatting with an AI to play a song whose title you know, sure. Getting an AI to play "that song that goes hmm hmmm hmmm hmmm ... uh, it was in some commercials when I was a kid" tho

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!"

Re: Apps SDK

#120
post #90

Earlier quoted context omitted.

As a JS developer for over 10 years who has seen multiple hype waves, here is my advice: You don't need to ride the first wave. You can wait until technology matures and see if it has staying power. For example, React and TypeScript were hard to set up initially. I deferred learning them for years until the tooling improved and they were clearly here to stay. Likewise, I'm glad I didn't dive into tech like LangChain…

LangChain has gone? I thought it was still around.

It's still around, but the hype has faded. Users discovered numerous issues with the project and began abandoning it. I remember one month when everyone was all, "LangChain is the future," and another month when the sentiment became: "LangChain is terrible."

You can see the hype cycle's timeline in HN's Algolia search: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

Post reply on HN