TL;DR
You do not need much to build apps well. Start with Claude Code, Expo, and EAS, use App Store Connect and Play Console for the stores, add a simple spreadsheet for your numbers, and only add paid tools once a real need appears.
New builders often think success requires a pile of paid tools. It does not. Most of what you need to build and ship a solid app is free or nearly so, and a few tools do the heavy lifting. The goal is not to collect tools - it is to solve real problems as they come up. Every extra tool is one more thing to learn and maintain. Start lean and let genuine friction tell you what to add next.
Start with the core stack
Before adding anything, use the core tools well. Claude Code writes your app from plain-English descriptions. Expo runs it live on your phone as you build and gives you the framework to ship to both stores. EAS Build turns your project into a real release, and EAS Update pushes fixes over the air without a full resubmission. Learning this handful of tools deeply covers most of what you need, and it keeps your costs low while you find your feet.
Categories worth having
Beyond the build stack, a few categories genuinely help. The store consoles - App Store Connect and Google Play Console - for listings, review, and analytics. A place to store your icons and screenshots so you can find them. A simple spreadsheet to track revenue and costs. And a subscription tool like RevenueCat if you add in-app purchases. Notice these are categories, not a race to the priciest option - what matters is having something in each slot you actually use.
- Building: Claude Code plus Expo running live on your phone
- Shipping: EAS Build for releases and EAS Update for over-the-air fixes
- Stores: App Store Connect and Google Play Console for listings and analytics
- Numbers: one simple spreadsheet for revenue and costs
Keep your numbers in one place
The tool category that trips up new builders is record-keeping. Because no one tracks it for you, you need your own record of each app's revenue, the store cut, and your costs. Early on, a single spreadsheet does the job. This is less about software and more about the habit of writing down what each app earns and costs as it happens.
Add tools only when you feel the pain
The right time to add a tool is when a real problem makes you want it, not because someone online recommended it. If in-app purchases get complicated, look at RevenueCat. If you cannot keep track of your apps, tighten your spreadsheet. Let friction guide your stack. This keeps your setup lean, your costs low, and your attention on building apps rather than configuring tools.
Protect your accounts
Whatever tools you use, basic security matters. Use strong, unique passwords and turn on two-factor login for your Apple and Google developer accounts and the email tied to them, since those hold your apps, signing keys, and income. A hacked account can undo a lot of hard work. Good security is a quiet tool that costs nothing and protects everything you are building.
The best builder toolkit is small, mostly free, and consistently used. Master Claude Code, Expo, and EAS first, use the store consoles for listings and analytics, cover your numbers with a simple spreadsheet, and add paid tools only when a real need appears.
Common questions
What tools do I actually need to start building apps?
Far fewer than most people think. Claude Code writes your app, Expo runs it live on your phone, and EAS Build and Update ship it and patch it. Add the store consoles for listings and a simple spreadsheet for your numbers. Start lean and add more only when a real need appears.
Do I need to pay for expensive tools?
Usually not at the start. The core stack of Claude Code, Expo, and EAS has accessible tiers, and a spreadsheet handles record-keeping early on. Paid tools like RevenueCat make sense once you feel genuine friction, such as complex in-app purchases. The best tool is the one you consistently use.
What is EAS Update for?
EAS Update pushes certain fixes and changes to your live app over the air, so users get them without you cutting a full new release and waiting on store review each time. It is one of the biggest time-savers in the stack for shipping quick fixes once your app is live.
What should I use to track my revenue?
Early on, a simple spreadsheet recording each app's revenue, the store cut, and your costs is enough. The key is the habit of logging what each app earns and costs as it happens. You can move to dedicated dashboards as your business grows, but a sheet you keep current is enough.
When should I add a tool like RevenueCat?
When a real problem makes you want it - typically when in-app subscriptions across both stores get complicated enough that handling them by hand slows you down. Letting friction guide your stack keeps your setup lean and your costs low, so your attention stays on building apps.
How do I keep my builder accounts secure?
Use strong, unique passwords and turn on two-factor login for your Apple and Google developer accounts and the email tied to them, since they hold your apps, signing keys, and income. A hacked account can undo a lot of work. Good security costs nothing and protects everything.
Keep going
Build a lean toolkit that actually helps you ship
Get the other 12 in the starter stack, plus the full App Store Launch Club community - $9/mo, cancel anytime.
Join the Club