Next Project Contacts
Two phones on slim clear stands against a dark studio backdrop, each screen showing the same glowing shapes.

Mobile

Flutter for design-led apps.

A single codebase that renders its own UI on both platforms. Best for design-led apps that must look identical everywhere, with the trade-offs stated plainly.

Contacts Technology map

Flutter draws every pixel itself. That is the whole trade: you get an interface that is identical on iOS and Android and fully under the designer’s control, and you give up the platform’s own widgets underneath it.

Two identical blank display frames of different sizes standing side by side on a dark bench.

Where the real work sits

  1. Where that trade is a good one

    Branded consumer apps, products with a strong bespoke design system, internal tools that must behave the same on every device, and anything where "why does the Android version look different" has been a recurring argument.

  2. Where it is not

    Apps that should feel native above all — an accessibility-critical utility, a finance app users expect to match the system, or a product built around platform components that Flutter has to re-implement. There, native Swift and Kotlin win.

  3. How we build it

    • State management chosen once, documented, and not mixed three ways
    • Layouts checked against text scaling and screen reader output, since the framework does not inherit platform accessibility for free
    • Native channels kept few and explicit for the device APIs that need them
    • Golden tests on the screens the brand cares about most

  4. Performance notes

    Flutter is fast when the widget tree is not rebuilt more than it needs to be. Most jank we are asked to fix comes from rebuilding a whole screen for a change that affected one line of it. We profile on real mid-range hardware, not on a simulator.

  5. Release

    Both stores from one pipeline, with staged rollout on Android and TestFlight on iOS. Crash reporting is wired before the first external build, not after the first crash.

    Compare with React Native, or see the wider mobile development picture and the full technology map.

Discuss the next step

Tell us what you want to build or improve. We reply with a plan, an indicative budget and a start date.

Contacts Browse the service map