iOS and Android apps, designed before they are built. Swift and Kotlin when a product needs the platform underneath it; Flutter or React Native when one codebase is the better trade. Which of those a project should use is a decision worth making deliberately, in writing, before the first screen — not by habit.
You are probably here because
- You need an app in both stores and one person who understands the platforms.
- A cross-platform framework was chosen by habit and now fights the platform.
- The web product works and customers keep asking for the app.
What you walk away with
- A written platform decision — native or cross-platform — with the reasoning shown, before any code
- Designed screens signed off before they are built, so the build does not become the design review
- An app in both stores with the release pipeline, signing and crash reporting handed over
- Offline behaviour, background work and push decided on purpose rather than discovered in review
Other services.
Product engineering
From a whiteboard to something your users can break.
We build and ship product software end to end — domain model, API, interface, pipeline, on-call runbook. Small teams, short feedback loops, and a codebase your...
Read moreScalability & performance
Find the ceiling before your customers do.
Traffic rarely grows politely. We measure where a system actually bends, fix the handful of things that matter, and leave you with the load model and...
Read moreLegacy modernisation
Change the engine without stopping the car.
Most systems we meet are not bad, just rigid: every change costs more than the last. We make them movable again through incremental strangler work, with...
Read moreTell us what is not working.
An hour on a call, no charge and no deck. We will tell you honestly whether this is work we are good at — and if it is not, who to talk to instead.
- Reply within
- One working day
- First call
- One hour, free
- Notice period
- One month, either way
- Based in
- Odense & Copenhagen