Ship a mobile app, and know where every euro goes
Six positions for a native app shipped to both stores: the mobile framework, the API, the database, the web front page, usage measurement and crash detection. The question that structures the kit is not which technology, it is where you pay.
Why
Mobile charges you where the web does not. On the web, you deploy and it is live. On mobile there are two app stores, two review processes, two rulebooks, and a build chain producing signed binaries. That is not an execution detail, it is half the work. This kit takes the six positions found in every shipped mobile app and says what each one actually costs. Expo makes iOS and Android fit in one codebase, FastAPI and PostgreSQL carry the service, Vercel holds the page that sells, PostHog tells you what people do and Sentry tells you what breaks. A mobile app that works is cheap to write and…
When
✅ This is your kit when You have to ship on iOS and Android, not a site people add to their home screen You have one person on the technical side, or zero mobile developers You want to know what you will pay before writing the first line ❌ Not for this kit A site, a landing page, a portfolio → vibecoder-website-stack A prototype to throw away in a week → proto-rapide An app needing exotic…
Tools included
- Expo
- Fastapi
- Postgresql
- Vercel
- Posthog
- Sentry