After WWDC26, Reselecting What an Indie Should Build Right Now

Now that on-device AI is free for small developers, the premises of app planning have quietly shifted. Here are five questions to choose what to build with Rork at the concept stage.

Rork⁴⁹⁸ app planning on-device AI⁵ indie developer³⁶ WWDC

✦ Premium Article

After WWDC 2026 wrapped, the first thing I jotted down was not a new UI. It was one line: developers with under two million first downloads can use Apple Foundation Models for free on Private Cloud Compute. For someone who builds apps as an indie developer, this changed the very premise of planning.

Until now, "add a smart feature to an app" came with metered external API costs and privacy worries. We have moved closer to a world where you can embed on-device-class AI at essentially zero cost. If so, our answer to "what to build with Rork right now" deserves a small update too. Today I lay out how to choose at the concept stage, as five questions.

Grasp precisely what changed

First, the facts. At WWDC 2026, developers with fewer than two million first App Store downloads gained free access to Apple Foundation Models. The Foundation Models framework added image input and server-side model integration, opening a path to call external models through the same Swift API. The framework itself is slated to be open-sourced this summer.

What matters from an indie standpoint is that this free tier is "a line drawn just for us." The under-2M-downloads condition targets precisely individuals and small teams. We have quietly moved from an era where AI cost held planning back, to one where you may plan with AI as a premise.

Question 1: Does this app only work because AI is free?

Start here. Not at the level of "adding AI makes the app nicer," but: can you say "this concept turns a profit for the first time precisely because AI is cheap to run"?

For example, a feature that summarizes or classifies user input used to have API charges eating into margin. If the free tier erases that, the same concept's economics change. When I look at a new concept, I always ask whether it becomes viable only now that AI cost approaches zero. Ideas where the answer is Yes are high-value candidates to start on now.

✦

Thank you for reading this far.

Continue Reading

What follows includes implementation code, benchmarks, and practical content we hope you'll find useful. This site runs without ads — server and development costs are supported entirely by members like you. If it's been helpful, we'd be truly grateful for your support.

WHAT YOU'LL LEARN

✦A concrete read on how the Apple Foundation Models free tier (under 2M first downloads) changed indie planning premises

✦Five questions to narrow down what to build now — including billing path, reason to return, and where AI belongs

✦How to use staged planning — validate fast with Rork, deepen as it grows — as a concept-doc template

Secure payment via Stripe · Cancel anytime

✦

Unlock This Article

Get full access to the rest of this article. Buy once, read anytime. This site is ad-free — your support goes directly toward keeping it running.

Unlock all articles with Membership →

Question 2: Is the reason to keep opening it inside the feature?

The most overlooked thing at the concept stage is the reason to return. Even with a smart feature, an experience that satisfies after one use will not grow retention. In the apps I have run, the ones that lasted generated a little meaning each day.

On-device AI shines here. An experience that interprets the user's data on the spot and returns a small insight for today is a cost you might hesitate over with an external API, but can run daily on the free tier. At the concept stage, put into words whether this feature becomes a reason to open the app every day. If it does not, it is a one-off convenience, not a business core.

Question 3: Is the billing path in the concept from the start?

If you chase revenue as an indie, billing is part of the concept, not an afterthought. At the concept-doc stage I draw a clear line between the value given for free and the value people pay for.

Three lines I write into the concept doc from the start (my template)
- Free value: the core of an experience worth opening daily (retention fuel)
- Paid value: an extension that deepens the free experience (ad removal / lifted limits / advanced AI)
- Billing placement: the natural moment right after the user feels the value

In the on-device AI context, "light AI features free, heavy or high-frequency AI features paid" draws a natural line. Because even a free tier has practical usage realities, a design where heavy users sustain you through a paid plan holds up without strain. If you combine AdMob ads with RevenueCat subscriptions, decide that split at the concept stage too.

Question 4: How many days to validate a minimal form with Rork?

Even a sound concept loses momentum if validation drags. This is where Rork (Expo) speed pays off. I take a new concept, build a minimal form in Rork first, hand out a share link, and confirm within a few days whether the reason to return is real.

In minimal validation, watch "did they open it again tomorrow," not "the numbers"
1. Generate just the one core screen in Rork, distribute via share link
2. Have 5-10 people use it for a week
3. Look only at whether they opened it the next day / stayed after a week
4. If they did not stay, drop the concept. If they did, move to the next question

You do not need to pay $200/month for Rork Max at this stage. Validate the core on Expo-based Rork, and only after you are convinced the reason to return is real, decide whether native depth is required. Not prepaying a heavy investment on concept validation is the realistic rhythm of indie development.

Question 5: When it grows, how much room is there to go deeper?

The final question is the ceiling. For a concept that survived validation, roughly estimate at the concept stage how deep it can later go. If the core you shipped with Rork (Expo) will eventually need native depth like widgets, Live Activities, or on-device Core ML, then a staged move to Rork Max enters the options at that point.

I call this "staged planning." Rather than aiming at the finished form from the start: ship fast with Rork, confirm the reason to return, and deepen with native features as it grows. Balancing investment against conviction at each stage is what wears me down the least while continuing indie development on limited time.

Conclusion: when the premise shifts, re-rank the concepts

On-device AI going free for indie developers is not a story about one new feature. It is a story about the premise of "what should be built" moving. A concept you gave up on, blaming AI cost, might pencil out now.

As a next step, write down three app ideas you have been nursing, and run each through today's five questions. The one with the most Yeses is the concept you should validate first with Rork. I am still in the middle of learning myself, but I would be glad to think it through together.

Thank You for Reading

Rork Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.