Hacker News Reader

Comment by billdybas | Hacker News Reader

What I don't see anyone talking about is how Private Cloud Compute is behind an iCloud subscription.

From what I can tell, this means any app that is using their foundation model is sharing against a user's pooled usage quota & Apple takes all the revenue upside if a user chooses to upgrade their plan.

Why would an app developer choose their model which has a minuscule 32K context window, might get throttled because of usage in another app, and doesn't share revenue over any frontier model vendor (where you can package/pass along token costs to your customers)?

View on HN

Apple will deploy the same security/ privacy / ease of use /packaging strategy they have done for every other product.

Same reason developers continue to use Apple payments even when they have to shell out 30% of the revenue.

I can see Apple, setting App store rules around declaring AI usage, or could start labeling apps not using their models with strong language designed to amplify the increasing user concerns around AI and so on.

The product strategy has to be better the product itself does not have to be objectively better for the developer for them to have to choose it.

I have consumed a decent amount of literature coming out of WWDC and I do not understand how the billing and model availability side of things will work.

Its definitely the case that Apple said that some AI capabilities will rely on cloud hosted models; and that some of these capabilities will be metered; and that "some paid iCloud+ plans" include increased usage. Its unclear what the full extent of capabilities that rely on cloud models are. We know that Spatial Reframing is a capability that relies on cloud models and will be metered; this was stated on-stage. The typical conversations with Siri are, supposedly, a mix, possibly based on how complex the query is? We know there are two cloud-hosted models (what they call internally "Cloud" and "Cloud Pro"); are both of these metered? Does it depend on the use-case (e.g. is Spatial Reframing metered because of its use-case or because of which model it uses?)

A lot of this would be easier to figure out if there was, somewhere, a "meter" you could see drop every time you used a metered feature; but there isn't. There is zero indication of metered AI usage anywhere in the settings that I have found (I am on the 27 dev beta). There is also zero indication that any of the iCloud+ plans include metered AI usage. It is also of note that Apple very specifically said on-stage that "some iCloud+ plans" include increased usage; implying that the $2.99/mo plan likely does not.

Apple has also announced that developers under a certain revenue number can use their foundation models in private cloud compute for free [1]. This implies: third party developers will pay for it. In other words: it might be the case that your shared iCloud+ pool of AI usage only applies to AI capabilities from first-party Apple apps, while in third-party apps the developers are expected to front the bill. Which further reinforces your point: Why would anyone choose to integrate with these cloud models?

Strange situation, and unlike Apple; they seem very frantic.

[1] https://techcrunch.com/2026/06/08/apple-bets-cheaper-ai-will...

Freemium is a potentially interesting model for app developers. If you're small enough to be in the free tier, you can avoid the risk of someone turning your app into the next backend for Chipotlai Max and running up your AI bill.

Once you get enough downloads to where Apple starts wanting to charge you money, you can consider switching to OpenAI or Anthropic or Google or Deepseek or whatever. Sounds like they've even made that relatively easy to do in the Foundation Models framework -- just implement the LanguageModel protocol. I expect open-source or provider-written adapters to pop up that would let you use your vendor of choice.

Motra, my workout app on iPhone (with great Apple Watch support, including counting reps), uses Apple foundation models to build a workout.

Not all use cases will be big agentic coding things that will use millions of tokens.

Some on device (or on server) stuff might be small one shot calls that just use what’s the OS provides.

Reply on news.ycombinator.com