At Volvo Group Connected Solutions, our team manages a wide range of mobile applications—from performance-heavy apps like Volvo Connect, which delivers real-time fuel insights and vehicle diagnostics, to business-focused solutions such as the Truck Charging app, built to make electric truck charging simple and seamless.
As our mobile ecosystem expanded, we naturally explored cross-platform development. The idea was compelling:
a shared codebase, faster releases, and consistent experiences for users across devices.
But anyone who has taken an app from concept to production knows that reality rarely matches the theory.
This isn’t a comparison of frameworks, nor a hunt for the “best” technology.
Instead, it’s an honest look at what we’ve learned building both native and cross-platform apps—what delivers results, what falls short, and how we choose the right approach for each project.
My hope is that these insights help guide your next mobile decision with clarity—not just optimism.
Why We Still Choose Native for Certain Applications
Some of our apps demand uncompromising performance and deep integration with the device.
For Volvo Connect, native development remains the most reliable path because the app must deliver:
✔ Real-time fuel efficiency insights
✔ Live vehicle diagnostics
✔ Reliable background processing
✔ Smooth performance even on lower-end Android hardware used in some regions
For mission-critical tools like these, native technologies give us the precision, speed, and stability we need.
When Cross-Platform Becomes the Smarter Choice
Not every app in our portfolio requires low-level device access or heavy background processing.
For business apps where agility and delivery speed matter more than raw performance, cross-platform shines.
The Truck Charging app is a perfect example.
From day one, React Native was the natural choice because it allowed us to:
Share core logic across iOS and Android
Sync releases with Agile sprint cycles
Ensure consistent UI behavior across platforms
Tap into existing JavaScript expertise
The result? Faster development, smoother iterations, and a unified user experience.
In short:
Native for performance.
Cross-platform for speed and scalability.
Where Cross-Platform Shows Its Limitations
After working on both native and hybrid mobile apps for over a decade, we’ve learned that cross-platform frameworks often introduce their own challenges:
1. UI/UX Doesn’t Always Show Up as “Native”
Frameworks like Flutter get close—but subtle design cues, gestures, and platform-specific behaviors still differ.
Our users—drivers, technicians, fleet managers—notice these inconsistencies in apps like Volvo Connect or Daily Inspection, where precise, intuitive UX is not optional.
2. Performance Bottlenecks Become Visible
Apps that depend on real-time updates or background tasks can push cross-platform frameworks to their limits.
Animations and data-heavy screens can struggle, especially on low-spec Android devices.
3. Plugin Dependencies Can Slow You Down
Cross-platform tools often rely on community-maintained plugins.
When iOS or Android releases a major update (like iOS 17 or Android 14), we sometimes scramble to update or rebuild plugins, whereas native teams can react more quickly.
4. Testing Isn’t Always Simpler
“Write once, test everywhere” often becomes:
“Debug everywhere.”
A single bug might behave differently on iOS and Android, increasing testing effort instead of reducing it.
Why Cross-Platform Has Become a Strategic Necessity
Modern apps must deliver high-quality experiences across all platforms—phones, tablets, and in some enterprise cases, desktops. Maintaining two fully independent native stacks increases:
Development time
Testing overhead
Release cycle delays
Cost of long-term maintenance
Cross-platform technologies address these pressures by enabling teams to build once and ship anywhere.
In fast-moving business environments, this agility is a significant advantage.
At Volvo Group Connected Solutions, we saw these benefits clearly while building the Truck Charging app, where maintaining separate native stacks was slowing down innovation.
React Native allowed us to:
Unify our development team
Reduce delivery timelines
Keep releases aligned with Agile cycles
Maintain consistent platform behavior
A Look at Today’s Leading Cross-Platform Frameworks
Among the most widely used cross-platform tools, React Native and Flutter dominate the landscape.
React Native (from Meta) uses JavaScript and the React ecosystem.
Flutter (from Google) uses Dart and a custom rendering engine.
Both allow code to be deployed across iOS and Android from a single codebase.
For us, the choice leaned toward React Native, largely due to our existing JavaScript skillset and the need to streamline development across product teams.
In the Truck Charging app, React Native enabled consistent UI behaviors and efficient backend integrations across platforms.