Swiss Fintech SaaS: Legacy hybrid app replaced with native mobile platform - and four years of continuous biweekly releases.

The Challenge

The client had a clear product vision, which was to make document and mail management genuinely mobile-first, but its existing mobile apps could not deliver it. The apps had been built on Ionic Framework, a hybrid technology that offered cross-platform convenience at the cost of feature depth and native performance. As user expectations rose and the product roadmap grew more ambitious, Ionic became a ceiling rather than a foundation. The problems compounded. Backend services connecting the mobile apps were inconsistent, causing frequent data synchronization failures that frustrated users managing financial documents where accuracy is non-negotiable. On the organizational side, the product team’s attention was structurally weighted toward the web platform. Mobile improvements were treated as secondary, leaving the apps progressively underserved relative to the web experience. Cross-team coordination between web and mobile functions had calcified into siloes. Decisions that required input from both sides moved slowly, and feature rollouts that depended on shared API logic stalled repeatedly. The cumulative effect was a mobile product that failed to match the promise of the platform it was supposed to represent. For a company whose entire value proposition rests on seamless, reliable digital access to sensitive documents, an unstable mobile experience was a direct threat to customer trust and competitive position. The enterprise needed a partner who could take complete ownership of the mobile layer, not just write code, but drive the transformation from the ground up while bridging the gap between mobile and web development functions.

The Approach

Gradion approached the engagement as a platform transformation, not a patch cycle. The first decision was also the most consequential: replace the Ionic hybrid framework entirely with native iOS and Android development. This removed the performance ceiling that had constrained feature depth and unlocked full access to each platform’s native capabilities, such as camera, secure storage, push notifications, biometric authentication, and deeper OS-level integrations relevant to financial document workflows. In parallel, Gradion worked to stabilize the backend architecture. APIs were audited, inconsistencies addressed, and data synchronization logic rebuilt to the reliability standard that financial document handling demands. Backend and mobile work proceeded in coordinated sequences, ensuring that stability improvements in the API layer were matched by the new native apps taking advantage of them. The UX was redesigned from first principles. The goal was intuitive navigation for everyday tasks, which included scanning a document, tagging an invoice, and initiating a payment. Each flow was designed around real-world user behavior rather than inherited from the desktop-first mental model that had shaped the original interface. Critically, Gradion embedded close collaboration channels between the mobile and web teams. Shared API documentation, joint planning sessions, and aligned product roadmaps converted the existing silo structure into a coordinated product organization. This was as important as the technical work, as a well-coordinated team sustains velocity, whereas a fragmented one depletes it. The result was a delivery model built for continuous improvement rather than one-off releases, providing biweekly feature cycles that gave the client a consistent cadence of progress without the instability risk of infrequent large releases.