Flutter development
Flutter, when one team has to cover both stores.
Flutter buys you one codebase for iPhone and Android, which is a real saving when the interface is mostly standard and the budget is one team rather than two. It costs you some of the platform feel, and we will tell you when that trade is wrong.
Overview
Flutter, the way we do it
Flutter is a good answer to a specific question: you need both platforms, the app is mostly forms, lists and flows rather than deep platform integration, and you would rather maintain one codebase than two. For a great many business apps that description fits exactly.
It is the wrong answer when the app is the product and every interaction has to feel native, or when you depend heavily on platform features that arrive in Flutter late. We would rather say that at the start than deliver something that quietly disappoints on iOS.
What's included
What you actually get
- One codebase for iPhone and Android, maintained by one team
- Best suited to forms, lists and flows rather than deep platform integration
- Right-to-left Arabic supported across both platforms at once
- Published to both stores under your name
- A straight answer on when native would serve you better
How we work
Five steps, no surprises
- 01
We talk
A call or a WhatsApp thread. You tell us what is not working; we tell you honestly whether we are the right people.
- 02
We scope it
A written plan with what you get, what it costs and how long it takes. Fixed, so there are no surprises later.
- 03
We build it
You see it as it goes, not at the end. Changes are cheap while it is still being built.
- 04
We put it live
On infrastructure we set up and secure, tested before the launch date.
- 05
We keep it running
Updates, monitoring and someone who answers. Most clients stay on a monthly agreement.
Questions
About flutter
Flutter or native?
Flutter when one team must cover both platforms and the interface is standard; native when the app is the product and the feel of it matters. We will say which yours is rather than recommending whichever is cheaper for us.
Will users be able to tell?
On a well-built Flutter app, mostly not. On the details, scroll behaviour, gestures, system integrations, an iOS user sometimes can. Whether that matters depends on what the app is for.
Has BitBee shipped a Flutter app?
Not among the work on this site; our published apps are native Swift and Kotlin. We list Flutter because we build in it, and we would rather say that plainly.
Also
Related work
- Quality AssuranceFind it before your customers do.
- UX DesignWork out what it should do before anyone builds it.
- UI DesignScreens people can use without being trained.
- Design SystemsOne set of rules, so the tenth screen looks like the first.
- Mobile ApplicationsApps people keep on the first screen.
- iOSiPhone apps built the way Apple expects.
- AndroidAndroid apps that work on the phones people actually own.
- AIAI that does one job, properly.
- Machine LearningModels that earn their place in the business.
- Data ScienceAnswers from the data you already have.
- LLMsLanguage models, kept on a short leash.
- Generative AIGeneration with a human still holding the pen.
- PythonPython, for the work that has to be read as well as run.
- Back-EndWhere an order becomes an order.
- DatabaseThe part of your system that is hardest to fix later.
- Node.jsNode.js, for the systems that have to answer quickly.
- GoGo, where it has to be fast and stay simple.
- .NET.NET, for the systems a business runs on.
- JavaJava, for systems measured in decades.
- Front-EndThe half of your product people actually see.
- Web DevelopmentCompany sites, customer portals, and web systems that hold up.
- ReactReact, built so the next team can still work on it.
- AngularAngular, for systems that have to last.
Tell us what you have in mind.
An engineer reads your message and replies to you directly.
Talk to us