What is a cross-platform app?
A cross-platform app is a mobile application built from a single codebase that runs natively on both iOS and Android, and often the web. It accesses device hardware directly (unlike a web app) but ships from one codebase instead of two, which compresses timelines and cuts maintenance cost. Businesses choose it when speed-to-market matters more than platform-specific features. To see how fireup.pro handles these decisions in practice, see our mobile app development service.
Flutter vs React Native vs Native vs PWA: the framework map
The choice of technology shapes everything that follows team structure, hiring, maintenance costs, migration path. Here’s how the main options compare:
| Flutter | React Native | Native (Swift/Kotlin) | PWA | |
|---|---|---|---|---|
| Language | Dart | JavaScript / TypeScript | Swift, Kotlin | HTML, CSS, JS |
| Performance | ★★★★★ | ★★★★☆ | ★★★★★ | ★★★☆☆ |
| Code sharing | 95–99% | 85–95% | 0% | 100% |
| UI fidelity | Custom renderer (Skia/Impeller) | Native components | Fully native | Web-rendered |
| Device hardware access | Full (plugins) | Full (JSI) | Full | Limited |
| Time to MVP | 12-16 weeks | 10-14 weeks | 20-28 weeks per platform | 6-10 weeks |
| Best for | Custom UI, IoT, automotive | JS teams, legacy migration | Games, AR/VR, complex animation | Content sites, B2B dashboards |
| Avoid for | Deep native ecosystem apps | Heavy computation | Startups with tight budget | Apps needing offline hardware access |
| Known examples | eBay Motors, BMW, Nubank | Shopify, Walmart, Bloomberg | Instagram, Spotify | Starbucks, Pinterest web |
| Developer adoption (2025) | 9.4% (Stack Overflow) | 8.4% (Stack Overflow) | – | – |
Cross-platform frameworks now power 40–45% of new mobile apps released globally (Statista, 2025). Flutter has 177,900 GitHub stars; React Native has 126,242.
8 real cross-platform apps, and why these businesses chose this path
The companies below range from a Polish e-commerce startup to BMW. The framework choices, the reasoning, and the results are different in each case. What they share: someone had to make a real decision under real constraints, and they documented it.
1. eBay Motors – Flutter | Beta in 3 months, 98.3% shared code
The problem: eBay Motors needed a standalone app for automotive buyers: separate from the main eBay app, with vehicle-specific features like VIN lookup, inspection history, and dealer contact. Building it natively on both platforms would have doubled the timeline and the team.
Why Flutter: The team needed a production-quality beta fast. Flutter’s Impeller renderer delivered smooth car galleries on older Android devices without custom optimization work.
Result: Beta launched in 3 months. 98.3% of code is shared between iOS and Android. Internal retrospective logged 100% developer satisfaction.
What this tells you: If you’re building a product vertical alongside an existing platform, a dedicated sub-app, a partner-facing tool, Flutter lets you ship production-quality without hiring separate iOS and Android teams.
2. Shopify (Shop App) – React Native | 1.8 million lines of redundant code deleted
The problem: Shopify’s mobile apps grew through years of parallel iOS and Android development. Two separate codebases meant double the bugs, double the review cycles, and slowing feature velocity as the company scaled.
Why React Native: Shopify’s engineering team already used JavaScript. React Native reused existing talent. It also supports brownfield migration: replace existing screens one by one rather than rewriting everything at once.
fireup.pro uses the same approach when helping clients refactor and modernize existing mobile applications – replacing screens incrementally to reduce risk.
Result: Shopify deleted 1.8 million lines of redundant code. Today 86% of the Shop app codebase is shared between iOS and Android. Shopify later became one of React Native’s largest open-source contributors, sponsoring the New Architecture development.
What this tells you: If your team already builds in JavaScript and you’re managing an existing app that needs modernization, React Native’s brownfield migration is the most practical path. You don’t commit to a full rewrite, you replace screen by screen.
3. Nubank- Flutter | Insurance product live in 3 months
The problem: Nubank serves 100 million customers across Latin America. Launching a new insurance product meant shipping on iOS and Android at the same time, with no tolerance for platform inconsistencies.
Why Flutter: One codebase: one team, one review cycle, one QA pass. No „iOS got it first” problem.
This mirrors what fireup.pro has done for fintech clients, see the QuickPay and TransRisk case studies for context on delivery under similar constraints.
Result: The insurance product went from zero to production in 3 months – the fastest product launch in Nubank’s history. The engineering team reported a 30% improvement in merge success rates after standardizing on Flutter.
What this tells you: When you’re adding new products to an existing app ecosystem, Flutter’s single codebase compresses timelines. The security plugin ecosystem means fintech compliance requirements can be met without custom native code.
4. BMW – Flutter | 300 engineers, 30+ markets, one codebase
The problem: BMW’s My BMW app serves customers in more than 30 markets. Separate iOS and Android teams worked from divergent codebases: every feature had to be built twice, and the two platforms still looked different.
Why Flutter: BMW wanted a framework that could unify their mobile engineering organization, not just the code. Google’s long-term commitment to Flutter gave them the confidence to make a multi-year platform bet.
Result: BMW grew its Flutter team to roughly 300 engineers: one of the biggest Flutter engineering organizations outside Google. Every My BMW feature now ships simultaneously on iOS and Android: vehicle status, remote lock, charging management, all identical across devices.
That number, 300 engineers on one framework, is either reassuring or mildly alarming depending on your appetite for lock-in. For BMW, the consistency gains made it worth it.
What this tells you: Flutter works at enterprise scale. If you’re building a companion app for a hardware product (IoT, automotive, smart home), Flutter is now the standard choice.
5. Walmart – React Native | 95% code shared after migration, zero outages
The problem: Walmart’s app carries billions in transactions. Maintaining separate iOS and Android versions of every feature was expensive, but a full rewrite of a mission-critical app was too risky.
Why React Native: The brownfield migration model lets you replace screens incrementally while keeping the existing native shell intact.
This incremental approach to legacy app refactoring applies directly to any e-commerce or enterprise app on an aging native codebase.
Result: Walmart achieved 95% code sharing on all migrated screens without a user-facing outage. The iOS and Android teams merged into one, cutting hiring costs and coordination overhead.
What this tells you: You don’t need a greenfield project. React Native’s migration path reduces risk while delivering the efficiency gains of a unified codebase. Walmart is the cleanest proof of this.
6. Tencent – Flutter | 77% increase in development efficiency
The problem: Tencent runs apps across different verticals, AI tools, cloud services, enterprise communication, each with separate teams. Cross-product consistency and delivery speed were both problems.
Why Flutter: Flutter’s widget system supports a shared design system across apps. Tencent built shared UI components reused across multiple products and teams.
Result: Tencent reported a 77% increase in development efficiency across Flutter-migrated products. Over 700 Flutter developers now work within the organization, across AITeacher, Mr. Interpreter, and Tencent Cloud Chat.
What this tells you: For product companies managing multiple apps simultaneously, Flutter’s component-sharing model scales across teams. One design system, multiple products.
7. QuintoAndar – Flutter | App store rating from 3.8 to 4.5 in 5 months
The problem: QuintoAndar is Latin America’s largest proptech platform. Their mobile app had performance problems and inconsistent UI that drove down ratings and retention.
Why Flutter: Flutter’s Impeller renderer performs consistently on mid-range Android devices, which are the majority in their Brazilian market. The faster iteration cycle let them respond to user feedback within weeks rather than months.
Result: After migrating to Flutter, QuintoAndar’s Google Play rating went from 3.8 to 4.5 in 5 months. For a marketplace, that improvement directly affects organic installs.
What this tells you: A bad app store rating is a distribution problem. If mid-range Android performance is hurting your numbers, Flutter’s renderer is a concrete fix, not a rewrite for its own sake.
8. Sportano.pl – React Native | 5,000 installs in week one, shipped in 6 weeks
The problem: Sportano is a European sports equipment e-commerce platform that needed a mobile app to compete with mobile-first marketplaces. Budget was tight, timeline was short, and they needed to test the mobile channel before committing to a native build.
Why React Native: The web frontend team already worked in JavaScript. React Native let them build a mobile app without hiring native specialists.
Result: The app shipped on both iOS and Android in 6 weeks and reached 5,000 installs in its first week, enough to justify continued investment.
What this tells you: For e-commerce teams already in JavaScript, React Native is the fastest path from zero to mobile. Payments, analytics, and push notifications are covered by mature packages out of the box.
When cross-platform won’t work?
Not every app fits Flutter or React Native. Here’s where native still wins:
| Scenario | Why native wins | Example |
|---|---|---|
| Computationally intensive apps (AR/VR, image processing, ML) | Direct GPU and CPU access without a bridge layer | Snapchat filters, Google Lens |
| Platform-differentiating features as core UX | Deep integration with platform-specific APIs as primary features, not add-ons | Apple Watch complications, Android widgets |
| Real-time 3D games | Game engines (Unity, Unreal) or Metal/Vulkan access required | Fortnite Mobile |
| Specialized hardware from day one | Custom Bluetooth stacks, medical-grade sensors, camera pipelines | Medical diagnostic devices |
Decision framework: which technology fits your project?
| Your situation | Best choice | Why |
|---|---|---|
| Greenfield app, startup, tight budget | Flutter | Fastest MVP, strong visual output, growing ecosystem |
| Existing JS/React team | React Native | No new language, brownfield migration possible |
| Existing native app that needs modernization | React Native | Screen-by-screen migration see fireup’s refactoring approach |
| IoT / automotive companion app | Flutter | BMW, Toyota, Philips Hue – proven at scale |
| Fintech / banking app | Flutter | Nubank, Credit Agricole, SoFi – enterprise track record |
| Multi-app design system | Flutter | Component sharing across products (Tencent model) |
| Content-heavy app, existing web team | PWA or React Native | Lower overhead, reuse web skills |
| Maximum performance, platform-differentiating UX | Native | No framework overhead, full OS integration |
Key numbers: cross-platform development in 2026
- 40–45% of new mobile apps use cross-platform frameworks (Statista, 2025)
- 30–40% faster development cycles vs. building native on both platforms separately (RipenApps, 2025)
- Flutter MVPs ship in 12–16 weeks vs. 20–28 weeks for separate native builds
- Cross-platform reduces engineering effort by 50–80% compared to dual native builds
- The cross-platform framework market is projected to grow from $15.67B (2025) to $47.61B (2035), CAGR of 11.75%
- Flutter: 177,900 GitHub stars, 2.8M monthly active developers worldwide
- React Native: 10.3M npm downloads per week (July 2026), up 105.6% year-over-year
- eBay Motors: 98.3% code sharing between iOS and Android (Flutter)
- Walmart: 95% code sharing on migrated screens (React Native)
- Shopify: 1.8M lines of redundant code deleted (React Native)
- Nubank: new product live in 3 months with Flutter vs. 6–9 months typical for native
What the 8 examples have in common?
3 things pushed every company toward cross-platform:
1. Speed. eBay Motors needed a beta in 3 months. Nubank needed an insurance product in 3 months. Sportano needed to test mobile in 6 weeks. Cross-platform compressed sequential iOS + Android builds into one timeline.
2. Cost of duplication. Shopify deleted 1.8 million lines of code. Walmart merged its iOS and Android teams. BMW put 300 engineers on one framework. These savings compound over years.
3. Team fit. No company chose a framework for its own sake. JavaScript teams went React Native. Teams starting fresh or prioritizing visual quality went Flutter.
The examples above handle hundreds of millions of users, billions in transactions and mission-critical financial and automotive workloads. Cross-platform is production-ready. The question is which framework fits your team, timeline, and product.
🚀 fireup.pro’s mobile team has delivered cross-platform and native apps across fintech, logistics, healthtech, and e-commerce. See our case studies.
Sources: Quash – Flutter vs React Native Statistics 2026 · RipenApps – Cross-Platform App Development Statistics · Very Good Ventures – Top Companies Using Flutter 2026 · Netguru – React Native Production Examples · Stack Overflow Developer Survey 2025 · Statista Mobile Development Frameworks Survey 2025
