Selected work / Pandora Analytics
Moving an established SaaS application from Ionic to Flutter.
Client
Pandora Analytics
Product
ToolKitX
Mobile Application Modernisation · Ionic → Flutter · Flutter Engineering
Replacing a technology stack is easy to describe. Migrating a real product is not.
ToolKitX was already an established SaaS product. Pandora Analytics engaged Sayge to migrate its mobile application from Ionic to Flutter.
This was not a greenfield build. The work was to move an existing application onto a different technology foundation while preserving the product context and the functionality that already mattered.
The ToolKitX mobile application was migrated from Ionic to Flutter. That is the scope of the engagement—not a claim about the wider ToolKitX platform.
An existing product, with a mobile application that had to move.
ToolKitX is publicly described as a SaaS platform for field workforce and operations management. The public product talks about areas such as field workforce management, project and workflow management, mobile support, location, analytics and collaboration.
That context matters because it explains why a mobile application already existed, and why a migration had to respect journeys and behaviour that were already in use. It does not describe the work Sayge performed on the platform as a whole.
Sayge worked with Pandora Analytics on the ToolKitX mobile application. The rest of the product remained Pandora Analytics’ responsibility.
The product already existed. The technology needed to move.
Migrating an established application is a different problem from starting a new one. There is already a product in the world. People already know how it behaves.
The engineering team has to understand that product well enough to rebuild the mobile application in Flutter without treating the existing work as disposable.
- existing functionality
- existing user journeys
- existing application behaviour
- dependencies between features
- existing UI and interaction patterns
- what needs to remain consistent
- what has to change because the new foundation is Flutter, not Ionic
01
Existing mobile application
Ionic
02
Assessment
Existing journeys, existing behaviour, existing functionality
03
Flutter migration
04
Flutter mobile application
05
Continued product evolution
Moving the product, not just the screens.
The migration required understanding the existing application before rebuilding it in Flutter. Screens are the visible part. The work sits underneath: how journeys fit together, what the application already does, and what must still be true after the technology changes.
Sayge worked with Pandora Analytics through that transfer of product knowledge—from the Ionic mobile application into a Flutter implementation of the same product context.
- existing application analysis
- understanding user journeys
- mapping existing functionality
- implementing functionality in Flutter
- validating the migrated experience
- fixing issues discovered during migration
- stabilisation
- Developers
- 3–4
- Engagement
- ~6 months
What a migration actually has to hold.
A framework change is not an overlay. Ionic and Flutter do not arrange work the same way. Functionality has to be translated, not copied as a picture of the old screens.
The concerns that mattered here are the ones that belong to any serious mobile migration: keep the product recognisable, keep journeys continuous, and leave the new implementation stable enough to keep evolving.
- preserving existing product behaviour
- translating existing mobile functionality into Flutter
- maintaining user journey continuity
- handling the differences between the two frameworks
- validating functionality during the migration
- stabilising the new implementation
- preparing the application for continued development
A migration is not a rewrite of screens. It's a transfer of product knowledge from one technology foundation to another.
The outcome.
The engagement moved the ToolKitX mobile application from Ionic to Flutter, giving Pandora Analytics a Flutter-based mobile implementation to continue evolving.
At a glance.
- Client
- Pandora Analytics
- Product
- ToolKitX
- Engagement
- Mobile application modernisation
- Starting technology
- Ionic
- Target technology
- Flutter
- Team
- 3–4 developers
- Duration
- Approximately 6 months
- Focus
- Existing mobile application migration
- Sayge's role
- Mobile application migration from Ionic to Flutter
Technology.
- Ionic
- Flutter
Existing products deserve engineering decisions that respect what already works.
Pandora Analytics · ToolKitX
saygeThe ToolKitX engagement was about more than moving from Ionic to Flutter. It was about taking an established mobile product forward while keeping the product itself at the centre of the migration.