Flutter App Development in London
One Dart codebase, shipped to the App Store and Google Play by the people who wrote it
One Dart codebase, shipped to the App Store and Google Play by the people who wrote it
Apex Technology Enterprises builds cross-platform mobile software in Flutter. A Flutter app is a single Dart codebase that compiles to native iOS and Android binaries, so one team writes one set of screens, one set of tests and one release process instead of maintaining two. Vitacal is ours, it is built that way, and it is in both stores.
That is the whole reason to hire on Flutter rather than on native: the second platform stops being a second project. The trade is that anything the platform vendors have not exposed to Dart has to be bridged, which is worth knowing before the decision rather than after.
Vitacal is Apex Technology's Flutter application, listed on the home page as an iOS and Android product. It is one Dart codebase covering both platforms, and the parts below are what that codebase actually contains rather than a capability list.
Calorie and nutrition tracking for women. Photograph a meal and get calories and macros back, with water tracking, favourite meals and progress insights. Photos are analysed but never stored.
DriverScan ships native iOS and Android SDKs, TidyBill and ProFlight are web platforms, DialogSafe is a desktop build. Flutter is one tool here, not the only one.
Inside Vitacal: Riverpod for state, go_router for navigation, Firebase for authentication, Firestore, Cloud Functions, storage, messaging and analytics, on-device camera capture, subscription billing through RevenueCat, Sign in with Apple and Google Sign-In, Apple Health and Health Connect integration, local notifications, scheduled background work, and translations driven off a single source file. Widget and integration tests run against the same codebase both stores get.
Flutter suits a product where the two platforms should look and behave the same, where the team is small enough that maintaining two codebases would halve its output, and where the app is mostly its own interface rather than a thin shell around platform features. Vitacal is all three, which is why it was built this way.
Native is the better answer when the app lives inside a platform capability that moves fast, when you are shipping a library other developers embed rather than an app, or when an existing native codebase already works. DriverScan is distributed as separate iOS and Android SDKs for exactly that reason. A recommendation to use Flutter is only worth anything from someone who will also tell you when not to.
Scoping. One to two weeks, paid, ending in a written scope, the screen inventory, the platform channels the app will need, the third-party services and their monthly cost, and a build order. You keep the document either way.
Build. Two-week increments, each installable on your own device through TestFlight and Play internal testing. Nothing is called finished before you can run it.
Store submission. App Store Connect and Google Play Console entries, signing, privacy declarations, screenshots and review responses. Both accounts stay in your name.
After launch. Either a monthly maintenance arrangement covering Flutter and SDK upgrades and the annual platform requirement changes, or a handover with the repository, the release pipeline and a runbook. Flutter versions and the store requirements move whether or not anyone is watching, so this is a decision to make deliberately.
Apex Technology Enterprises Ltd is a UK-registered company, number 15019510, with its registered office in Great Portland Street, London W1W 5PF. Flutter work is delivered remotely across the UK, with meetings in London when a project warrants them.
Email [email protected] with what you want to build and which platforms it has to reach. If you are not yet sure Flutter is the right choice, say so and the first reply will address that rather than sell past it. For the wider picture, see what this software development company builds and the mobile app development page.