Mobile in a weekend, no native code.
You don't need a separate mobile team — or any native code — to ship iOS and Android. Here's the exact path from web app to App Store, in a weekend.
May 10, 2026
For most of the last decade, "we should have a mobile app" was the sentence that killed indie projects. Native code, two SDKs, App Store hoops, build pipelines you didn't understand. So you wrote a roadmap item and never touched it.
That trade is broken now. Expo + a shared backend means the mobile version of your web app is genuinely a weekend project — not a quarter.
The shape of the path:
Friday night. Scaffold the Expo app. Symlink your backend types so the mobile app speaks the same data as the web. The login screen takes 20 minutes because the auth client is identical.
Saturday. Port the screens you actually need. If you've kept your business logic in the backend (which the playbook will yell at you about), the mobile UI is mostly composition. The data fetching is the *same hook* you used on web.
Sunday. Build with EAS. Push to TestFlight. Send the link to a friend. The "we should have a mobile app" sentence is now "we have a mobile app."
The native engineers I respect are the first to tell you: 95% of indie apps don't need native. They need to be in your customer's pocket. Expo gets you there this weekend.