Building a mobile app for a startup: the complete guide
A mobile app for a startup is not a responsive site. The cost depends on complexity, cross-platform, and the provider, and the paywall is part of the MVP.
Article summary
- The app is the right choice when use is regular and mobile. A responsive site reproduces neither notifications nor retention.
- At a French agency, a simple MVP sits between €8,000 and €25,000. With a subscription and a paywall, between €25,000 and €60,000.
- React Native covers iOS and Android with a single codebase. RevenueCat measures 2.2% download-to-trial, versus 1.9% for native.
- The hard paywall converts at 10.7% download-to-paid at D35, versus 2.1% for freemium, with one-year retention close by.
- 77% of users leave within 72 hours. Refocusing Sticker Editor's onboarding on the first sticker raised conversion by 20%.
Summarize this article with
Building a mobile app for a startup is one of the most structuring decisions you will make. The wrong technology, the wrong provider, the wrong timing: every mistake is expensive. firstapp gives you the complete guide: from validating the idea to launch, including real costs, technologies, and the traps to avoid.
Why build a mobile app for a startup
The competitive advantages of a mobile app
A well-built mobile app is not one more tool. It is a direct channel with your user, available 24 hours a day, personalizable, and able to create a lasting relationship. Where a website is consulted, an app is used. The difference is huge.
Push notifications, access to the phone's native features (camera, GPS, biometrics), the ability to work offline, and a permanent presence on the user's home screen: advantages no website can reproduce. And in a market where retention is the heart of the fight, these advantages make all the difference.
Use cases by type of startup
Not every startup needs a mobile app, but many more than people think do need one. Here are the cases where it is clearly the right choice:
✓ B2C startup with daily or weekly use: fitness, nutrition, wellness, personal finance, education. The habit is built on mobile, not on desktop.
✓ Marketplace or matching platform: the app smooths interactions and creates a stronger network effect than the web.
✓ Startup with a community component: push notifications and native social features create engagement that is impossible to reproduce on the web.
✓ Donation, solidarity, or social-impact app: mobile access makes the spontaneous act of commitment easier, on the subway, away from the office.
David, founder of Jam Solidaire, could have built a website to collect donations for associations. He chose the mobile app, because giving is spontaneous, emotional, and mobile by nature. Result: €1M in revenue in 2 years, 15,000+ active donors, and about ten partner associations signed even before the app launched.
Mobile app vs website: which should you choose?
The question is not "app or website?". It is "where does my users' main experience happen?". If the answer is on mobile, with regular use, and with a need for notifications or native features, the app is the right choice. If the answer is an occasional look on desktop, a website is enough.
A responsive website is not a mobile app. The user experience, retention, and technical capabilities are fundamentally different. Do not confuse the two to save budget in the short term. You will pay for it in long-term retention.
Newsletter
Once a week.
Last issue
We opened 10 apps to see how they sell a subscription.
+534 people read us each week
The key steps to build a mobile app
Define the idea and the positioning
An app idea is worth nothing without a clear answer to two questions: what precise problem am I solving, and for whom? The more precise you are on these two points, the more useful your app will be, and the easier it will be to sell.
Positioning is defined in one sentence: "My app helps [who] to [do what] better than [the current alternative]." If you struggle to fill in that sentence, your idea is not clear enough yet to be built.
Validate the need with an MVP
Before writing a line of code, go into the field. Talk to your future users. Look for concrete commitments, not "that's a good idea". A user who gives you their email, signs a pre-agreement, or agrees to pay before the product exists: that is validation.
The founder of Calyra (formerly Nutria) prepared his TikTok content strategy in parallel with building the app, not after. When the app shipped, the audience was already there. The first revenue arrived in the first month. Validation was not done with a survey. It was done with a real, engaged audience.
Write an effective specification
A good specification does not list features. It describes user journeys. "The user can create a profile" says nothing. "The user creates their profile in 3 steps, with only their email, their first name, and their main goal": that is a specification that guides development.
Focus on the main journey of your typical user. Everything else is secondary for v1.
Choose the right development model
Three options: in-house development, freelance, or a specialized agency. Each option has its place, but not for the same projects. We come back to this in detail below.
Test and improve before launch
TestFlight (iOS) and Google Play beta tests are your best friends before launch. Distribute your app to 20 to 50 real users, not your friends: real target users. Watch how they use it. Where do they stop? What do they not use? Every friction identified before launch saves you a star on your App Store rating.
To validate before you build:How to validate your app idea before building it
Which type of mobile app to choose for a startup
Native app (iOS / Android)
Native means an app built specifically for one platform: Swift/SwiftUI for iOS, Kotlin for Android. Performance is maximum, and access to system features is total. It is also the most expensive: two codebases, two teams, twice the maintenance.
In 2026, pure native is rarely justified for an early-stage startup. It is relevant when your app depends on very advanced hardware features (intensive AR, real-time video processing, deep system integrations). In every other case, cross-platform is the right choice.
Hybrid / cross-platform app, our recommendation
React Native is the framework we use at firstapp for all of our clients, and that is not an accident. A single codebase for iOS and Android, performance close to native for 95% of use cases, and the most mature ecosystem on the market.
React Native - Our recommendation
The industry standard for cross-platform apps in 2026. A single iOS + Android codebase, native performance on 95% of use cases, and the largest JavaScript ecosystem in the world. It is the choice Facebook, Shopify, and Airbnb made in their early days. And ours for all of our clients. RevenueCat 2026 data confirms that React Native apps have the best median conversion of every framework: 2.2% download-to-trial versus 1.9% for native.

Flutter - A valid alternative
The serious competitor to React Native, pushed by Google. Excellent performance, very consistent UI. But the ecosystem is more closed, the community is smaller, and the Dart language is less widespread than JavaScript, which restricts the developer pool and raises costs. A good choice if you already have a team trained on Flutter.
PWA (Progressive Web App) - Not recommended for a startup
A PWA is not a real mobile app. It is an improved website. No presence on the App Store, no push notifications on iOS (still very limited), no full access to native features. If your target is mobile and your use is regular, the PWA is a false economy. You will pay the difference in retention.
No-code and low-code solutions
Bubble, Adalo, Glide, or FlutterFlow: these tools let you build an app without coding. They have their place for validating an idea very quickly at almost zero budget. But they have their limits: reduced customization, limited performance, total dependence on the platform, and no scalability beyond a certain volume.
Our advice: use no-code to validate, not to build. Once the market is confirmed, invest in real development.
How much does it cost to build a mobile app
Factors that influence the price
The cost of a mobile app depends on four main variables: functional complexity (number of features, third-party integrations), the technology chosen (native vs cross-platform), the provider's profile (offshore freelance, generalist agency, specialized agency), and the quality of onboarding and the paywall, often forgotten in quotes but decisive for revenue.
Budget by type of application
Here are the real market ranges in 2026, at a French agency:
→ Simple MVP (authentication, profile, main feature): €8,000 to €25,000 depending on the technology and the provider.
→ App with a subscription, a paywall, and third-party integrations: €25,000 to €60,000.
→ Complex app (marketplace, AI, advanced features): €60,000 to €150,000+.
→ Cross-platform vs native: cross-platform cuts costs by 20 to 40%, one codebase for iOS and Android.
The firstapp offers
Creation is on request. Monetization offers are on the Pricing page.
What sets firstapp apart from other agencies is not the code. It is what we do around it. Business thinking, optimized onboarding, paywall strategy, and growth support from v1. The code is the base. Growth is what we build together.
Hidden costs to anticipate
The development quote is never the total cost. Here is what many founders forget to budget:
Hosting and backend infrastructure: depending on complexity, from €50 to several hundred euros per month.
Third-party tools: RevenueCat, analytics, push notifications, attribution. Plan €100 to €200/month depending on volume.
Developer account: $99/year for the App Store, $25 one-time for Google Play.
ASO and acquisition: an app with no visibility strategy will not be found. Budget for it from launch.
In-house, freelance, or agency: which to choose
In-house development
If you have a CTO or a developer co-founder, that is your best scenario, provided they are experienced in mobile development. The monthly cost of a good mobile developer in France is between €4,000 and €7,000, or €50,000 to €84,000/year, before employer charges. That is relevant when development is the core of your business and you have the funds to hire.
Going through a specialized agency
An agency brings a complete team - developer, designer, project lead, monetization expert - and a proven method. The cost is higher than a freelance, but execution quality and risk management are not comparable. It is the natural choice when your priority is to move fast and do it right the first time.
The difference between a generalist agency and a specialized agency like firstapp: we do not just deliver code. We think product, monetization, and retention from the first meeting. Not after launch, when it is too late.
Freelance vs agency: the real comparison
Freelance
✓ Lower cost
✓ Flexibility
✗ Dependence on a single person
✗ Rarely an expert in monetization
✗ Risk of delays and dropouts
Specialized agency
✓ Complete team
✓ Method and process
✓ Product + growth expertise
✗ Higher cost
✗ Less flexibility
In-house
✓ Total alignment
✓ Fast iteration
✗ High fixed cost
✗ Long hiring
✗ Limited skills
Criteria for choosing the right provider
1. Apps shipped and in production, not mockups or demos. Ask for the App Store links.
2. Monetization expertise, not only code. Ask questions about onboarding, the paywall, retention. A provider who only talks about technology will not help you generate revenue.
3. Transparency on price. A provider who refuses to show their rates, or who cannot give you a range after a first call, is a warning signal.
How to build an effective MVP for your startup
Definition and goals of an MVP
An MVP, Minimum Viable Product, is not an incomplete app. It is an app that is complete on a tight scope. The difference is crucial. The goal of an MVP is not to ship something "unfinished". It is to validate a market hypothesis with the minimum possible investment.
Essential features to include
Use the MoSCoW method to prioritize:
Must have: what the app cannot exist without. The absolute minimum for the user to get value.
Should have: important but not blocking for launch. For v1.1.
Could have: nice to have. For when you have revenue and time.
Won't have: explicitly excluded from the MVP. Saying it clearly avoids scope creep.
The most dangerous feature in an MVP is the one the founder absolutely wants to include but that users did not ask for. Every feature not validated by real users is a complexity debt you will pay in development time and maintenance.
Avoid the common MVP mistakes
Confusing an MVP with a prototype. An MVP is published on the App Store and tested with real users who do not know you.
Not including the paywall in the MVP. If your app is free at launch "to see", you are not validating your revenue model. Include the paywall from v1.
Waiting for perfection. An MVP that ships in 6 months is not an MVP. If your MVP takes more than 3 months, it is too big.
The technologies for building a mobile app
Our position: React Native
At firstapp, we made an explicit choice: React Native for all of our clients. Not Flutter, not pure native, not no-code. React Native.
Why? Because it is the cross-platform framework with the best performance / maintainability / ecosystem ratio in 2026. A single codebase for iOS and Android, native performance on everyday use cases, and JavaScript, the most widespread language in the world, which means the largest developer pool and the best third-party integrations.
Flutter is technically excellent. But Dart is a niche language, the community is smaller, and third-party integrations are less mature. For a startup that wants to move fast and stay flexible, React Native wins every time.
Backend and infrastructure
For the backend, our recommended stack: Supabase (open-source BaaS, PostgreSQL, real time, auth included) or Firebase for simpler projects. Both let you move fast without investing in custom infrastructure you cannot afford to maintain at early stage.
Monetization tools
RevenueCat for subscription management. It is the standard. It handles receipt validation, entitlements, renewals, and gives access to the SOSA report, the best source of market benchmarks. We integrate it on all of our projects.
To choose your monetization tools:The best tools for managing your app's subscriptions
UX/UI: designing a high-performing app
Principles of a good user experience
Good mobile UX is not pretty UX. It is UX that guides the user to their first win as fast as possible. Every screen must have a single goal. Every action must be obvious. Every extra friction costs retention.
Onboarding, the most important screen
77% of users abandon an app within the first 72 hours. In almost every case, the cause is onboarding that did not deliver the value fast enough. Onboarding is not a formality before the app. It is the moment you win or lose your user.
By refocusing the onboarding of Sticker Editor around the aha moment, the first sticker created, the conversion rate rose by 20%. Nothing changed in the product. Only the order in which the value was presented to the user.
Optimizing the retention rate
Retention is decided in the first 24 hours, and more precisely in the first 15 minutes. If the user did not get their aha moment in their first session, they will not come back. Every UX optimization must aim at this goal: get the user to their aha moment as fast as possible.
Monetization strategies for a mobile app
The hard paywall, our recommendation
RevenueCat 2026 data is unambiguous: the hard paywall converts 5 times better than freemium (10.7% vs 2.1% download-to-paid conversion at D35), with one-year retention that is almost identical. The myth of "freemium so you do not scare users away" is definitively buried by the numbers.
Our advice: put a paywall in from launch. If your onboarding delivers the value correctly, users will pay. If your onboarding does not deliver the value, work on the onboarding, not on removing the paywall.
Freemium and subscriptions
The freemium has its place, mainly when free users create network value for paying users (marketplace, community) or when the viral effect of free users is a real acquisition lever. In every other case, it is a bad economic idea.
In-app purchases and credits
For AI apps with variable inference costs, a credits model is often more honest and better received than a fixed subscription. The user understands what they are buying: capacity, rather than undifferentiated access to an app.
Launch and promote your mobile app
Publish on the App Store and Google Play
App Store submission is a process that takes between 24 hours and 7 days depending on your app's complexity and Apple's workload. Prepare your submission at least 2 weeks before your target launch date. A last-minute rejection can push your launch back by several weeks.
ASO, the optimization everyone neglects
ASO (App Store Optimization) is the SEO of the App Store. A well-optimized title, screenshots that convert, and well-chosen keywords can multiply your listing conversion rate by 2 to 3. It is often the first high-ROI optimization, and the most neglected.
User acquisition strategies
The first users do not come from the algorithm. They come from you. Manual distribution, social networks, Product Hunt, niche communities: you have to go get your first 1,000 users by hand. It is thankless, and indispensable.
Mistakes to avoid when building a mobile app
Wanting to build everything from the start. Every feature not validated by real users is wasted money and time. Launch fast, learn fast, iterate.
Choosing the technology before understanding the need. Technology is a means, not an end. React Native for 95% of cases. Native only if your app truly requires it.
Launching without a paywall. A free app does not validate your business model. If nobody pays, you do not know whether your app has value, or whether people just like free things.
Ignoring onboarding. You have 15 minutes to convince a new user. If your onboarding does not deliver the value in that window, your app churns, no matter how well it is built.
Choosing a provider on price alone. The cheapest app is rarely the cheapest overall. The costs of taking it back, chaotic maintenance, and failed conversion pile up fast.
Succeeding at growing a mobile app
Continuous product iterations
The apps that succeed in 2026 are not the ones with the best v1. They are the ones that iterate the fastest. RevenueCat confirms that apps launched before 2020 still capture 69% of market revenue. Their advantage is not technological. It is the accumulation of years of iterations and user data.
Analyzing user data
You cannot improve what you do not measure. From launch, track: D1/D7/D30 retention rate, paywall conversion rate, MRR, churn, and your app's key events. These metrics will tell you exactly where to focus your optimization effort.
Retention and user engagement
Retention is less glamorous than acquisition, but infinitely more profitable. Cutting your churn from 2% to 1% can double your LTV. The levers: relevant push notifications, streaks, visible progress, and an aha moment renewed at every session.
You have a mobile app project for your startup? firstapp supports you from the idea to launch, and beyond. We handle development, onboarding, the paywall, and the growth strategy so you can focus on what you do best: building your business.
The most asked questions about building a mobile app
Who should you contact to build a mobile app?
To build a mobile app, you have three options: a freelance developer, a generalist agency, or an agency specialized in mobile development. The freelance is cheaper but exposes you to heavy dependence on a single person and a high risk on timelines. The generalist agency covers a wide spectrum but often lacks expertise on mobile monetization and retention. A specialized agency like firstapp brings a complete team and product expertise that goes beyond code: onboarding, paywall, ASO, growth strategy. The most important criterion: ask for links to apps in production on the App Store, not mockups.
What is the price to build a mobile app?
The budget to launch an app is not just the development cost. You need to anticipate four lines: initial development (between €11,000 and €60,000 depending on complexity), annual maintenance (15 to 25% of the initial cost), third-party tools (RevenueCat, analytics, push notifications, about €200 to €500/month), and user acquisition (variable depending on your channel). In practice, plan 30 to 40% of the development budget in recurring costs in the first year. An app launched with no budget to iterate after launch is an app that will stall. The first weeks of user feedback always generate indispensable adjustments.
What is the salary of a mobile app developer?
In France, the salary of an experienced mobile app developer sits between €45,000 and €75,000 gross per year depending on experience and location. A senior React Native developer in Paris is generally between €55,000 and €75,000. As a freelance, day rates run from €400 to €700/day for an experienced profile. That is why going through a specialized agency is often more economical for an early-stage startup: you get a complete team (dev, design, product) for a controlled fixed cost, without the charges and risks of hiring a developer in-house.