A Native App Experience for a Leading Automotive Customer Portal
A leading Swiss automotive group provides its employees with a comprehensive intranet -internal information, tools, and services for daily work - but had no native presence on employees' mobile devices. Rebuilding the intranet as a fully native app would have meant duplicating years of existing web functionality and running two parallel codebases going forward.
Goal: Native Access to the Intranet Without Duplicating It
The goal was to give employees a native iOS and Android app that feels like a first-class mobile experience, while reusing the existing intranet as the single source of truth — including its login flow, so employees stay securely signed in when moving between native and web content.
Key requirements included:
- a native app for the existing employee intranet
- a secure, seamless authentication flow between the native app and the web content
- native app icon, splash screen, and a store-ready presence for both platforms
- a foundation that could be extended with native features (e.g. push notifications) over time
Web-to-App Implementation
Prime Force brought the existing intranet to iOS and Android as a native app, rather than reimplementing its functionality from scratch.
A key focus was the authentication flow: session and login state are securely carried over into the native app, so employees move between native screens and web-rendered intranet content without being asked to log in twice or losing their session.
The greatest challenge was making this handoff between native and web layers seamless and secure - ensuring a consistent, trustworthy experience without compromising on session security.
Result: A Seamless Native Entry Point to an Existing Intranet
By bringing the existing intranet into a native app instead of rebuilding it, employees gained a fully branded native app on iOS and Android while the company kept a single web codebase as the source of truth.
The key benefits:
- Seamless authentication: employees move between native and web content within the app without repeated logins or broken sessions.
- One intranet, two platforms: the existing intranet remains the single source of truth, avoiding duplicated business logic across platforms.
- Native first impression: a dedicated app icon, splash screen, and store-ready presence give the intranet a fully native feel from first launch.
- Built to extend: the app's foundation is ready for additional native features, such as push notifications, as requirements grow.
Conclusion
This project shows how an existing, security-sensitive intranet can become a native mobile app — combining a secure, seamless authentication experience with the speed of a Web-to-App approach over a full native rebuild.
Technology Stack
This project was implemented using Flutter, enabling a single native codebase for both iOS and Android, built around an integrated WebView.