We chose to develop directly within the host application's codebase. While we accepted the trade-off of shared release cycles, this approach delivered critical advantages:

• Immediate Start: Allowed us to meet a strict time budget without battling existing organizational processes.
• Zero Pipeline Changes: Avoided disrupting other teams' infrastructure by leaving existing Angular templates and deployment pipelines intact.
• Trivial Component Reuse: Leveraged the clean host repository to easily move shared UI components into a centralized module.
• Future-Proof: Kept the architecture simple for now, keeping the door open to migrate to Module Federation later if frontend teams scale up.

Froots' web app was already built with React and Next.js, making React Native the obvious choice. Code reuse, existing knowledge, and a shared monorepo meant we could hit the ground running.

React Native & Expo: Natural evolution from React/Next.js
Tamagui: Replacing Mantine while keeping design consistent
Monorepo: Share code between web and mobile

Bonus: Expo can render on the web, meaning it could eventually replace the web app entirely. Plus, &amp has already built multiple Expo apps used by tens of thousands simultaneously—we know how to move fast.

Close coordination with Oberbank’s internal IT teams was a cornerstone of the project’s success. Rather than working in a silo, we functioned as a strategic partner to their technical experts, ensuring a seamless integration into the bank's existing infrastructure.

Our approach:

• Scrum-driven delivery cycles to maintain a structured, iterative, and predictable pace toward the launch.
• Asynchronous Sprint cycles between &amp and Oberbank. This staggered approach allowed us to remain in a constant "build-and-review" loop without the teams blocking each other’s progress.
• Joint backlog refinement where business logic, regulatory needs, and technical constraints were discussed and prioritized in real-time.
• Continuous feedback loops between &amp and Oberbank, ensuring that sprint results were reviewed and adjusted without administrative delay.

This communication-heavy Scrum model was essential for managing the project’s technical complexity within a six-month window. By maintaining an "open-door" policy with Oberbank’s developers, we bypassed traditional approval bottlenecks and maintained a high development velocity without compromising on quality or compliance.

Three months. That's all the time it took to develop a complete mobile app from a vision.Today, froots users can natively manage their financial future on iOS and Android. The complete dashboard with all depots, the thoughtful onboarding flow, the entire transaction history, and depot tracking—everything they know from the web app is also there in the native app. Everything works quickly and intuitively; everything feels like an app that was developed from the ground up for mobile.

This only succeeds when an experienced team relies on proven technologies while proceeding strategically. The project showed us that even the most ambitious goals can be achieved in the shortest time with a methodical approach and the right team setup—while also being really enjoyable.