When we use Flutter and React Native.
When the app has to exist on iOS and Android and there is no point in building it twice. One codebase, two app stores, and one place to fix things when they go wrong.
They work well for apps that show data, manage a workflow, or communicate with a system. In other words, most apps.
This is where they pay off: two platforms, one budget, and a product that needs to stay aligned on both.
The technologies we work with
The technologies we work with
When we do not use it
When we do not use it
When the app relies heavily on operating-system-specific features, or when graphics and responsiveness are the product. Native is still better there, and it is worth paying for twice.
What we have used it for
What we have used it for
BuildEmbedded & IoT
Mechit — control software for driving simulators.
3 yearsActive
[REDACTED]
BuildPublishing & Media
Reading app — delivered on the launch date.
1 yearCompleted
The way we work is the same across technologies: peer review before release, separate environments, and automated pipeline checks. How we work