Flutter or native? Choosing the right way to build your app

In this article12 sections

1. Flutter vs native: what the words actually mean
2. Why this choice matters more in Nigeria
3. Flutter vs native: the honest comparison
4. What Flutter vs native really costs in Nigeria
5. When I recommend Flutter
6. When I recommend going native
7. What about React Native, Kotlin Multiplatform and web apps?
8. Mistakes I see business owners make
9. How I decide in one afternoon: my checklist
10. Key takeaways
11. Frequently asked questions
12. Your next step: talk it through before you spend

If you are planning a mobile app, the Flutter vs native question will land on your table early, usually as two quotes that look nothing alike. Last year Amaka, who runs three laundry shops across Lekki and Ikoyi, sat across from me with exactly that. One developer wanted ₦18 million to build “proper native apps” for Android and iPhone. Another wanted ₦6.5 million to build one app in Flutter that would run on both. She asked me the question I hear almost every month: “Dan, is the cheap one a trap, or is the expensive one a scam?”

Neither, as it turned out. But the right answer depended on things nobody had asked her. Who are her customers? What phones do they carry? Does the app need to talk to hardware like a printer or a card reader? Who will maintain it after launch, and what happens if that person travels abroad next year? That is the real decision. It is not a fight between two technologies. It is a business decision about money, time and risk.

In this guide I explain both options in plain English, show you what each one costs in naira as at 2026, tell you where each one shines and where it hurts, and give you the checklist I use with my own clients in Abuja, Lagos and across Nigeria. By the end you should be able to sit with any developer and ask the right questions, instead of nodding along and hoping for the best.

Flutter vs native: what the words actually mean

Most confusion starts with vocabulary. Developers throw around words like native, hybrid and cross-platform as if everybody learnt them in secondary school. Let me slow down and define them properly, because once you understand these three ideas the rest of this article will feel like common sense.

What “native” means

A native app is built with the official tools the phone maker provides. For Android, that means Google’s tools: the Kotlin programming language (older apps used Java) and a program called Android Studio. For the iPhone, that means Apple’s tools: the Swift language and a program called Xcode, which only runs on a Mac.

The important point for a business owner is this: native means two separate codebases (a codebase is the full collection of code files that make up the app). One for Android, one for iPhone. They do not share code. If you want to add a “pay on delivery” button, a developer builds it in Kotlin for Android, then someone builds it again in Swift for iPhone. It is tested twice and released twice. Two teams, or one team doing every job two times.

What Flutter is

Flutter is a free toolkit made and maintained by Google. Its first stable version came out at the end of 2018 and it has grown quickly since. With Flutter, a developer writes the app once in a language called Dart, and that same code runs on Android and iPhone. It can also produce web and desktop versions, though most of my clients use it for phones.

Flutter does something clever. Instead of borrowing the phone’s own buttons and menus, it draws every pixel itself using its own rendering engine (the engine is the part that paints the screen). That is why a Flutter app looks the same on a ₦90,000 itel phone and on an iPhone 15. The code is also compiled, which means it is turned into instructions the phone’s chip runs directly. That is a big reason modern Flutter apps feel fast.

Where “cross-platform” and “hybrid” fit

Cross-platform simply means one codebase that runs on many platforms. Flutter is cross-platform. So is React Native, which Meta (the owner of Facebook, Instagram and WhatsApp) created. You will read about it later in this guide.

“Hybrid” is an older word. Around 2012 to 2016, many cheap apps were really websites stuffed inside an app wrapper. They were slow, they froze, and they looked odd. Many business owners still believe “cross-platform apps are slow” because of that era. That reputation was earned ten years ago. Flutter and React Native are not the same thing as those old wrappers, and judging them by that history will cost you money.

Why this choice matters more in Nigeria

A developer in London or San Francisco can make this decision on technical taste. Here, the local realities change the maths. These are the three I always put in front of my clients before we talk about technology at all.

Most of your customers carry Android phones

Public trackers such as StatCounter have shown for years that Android runs on the large majority of phones in Nigeria, often well above 80 percent. Walk through Computer Village in Ikeja or Banex Plaza in Wuse 2 and you will see why: Tecno, Infinix, itel, Samsung, Redmi and Oppo dominate the shelves.

But iPhone users matter more than their numbers suggest. If you sell premium shortlets in Lekki Phase 1, run a private clinic in Maitama, or target corporate buyers in Victoria Island, a large slice of your paying customers may carry iPhones. So most Nigerian businesses need both platforms, with Android as the priority. That is exactly the situation where building once and running on both starts to look very attractive.

Cheap phones, costly data and patchy networks

Many of your users will have phones with 2GB to 4GB of memory and storage already full of WhatsApp videos and voice notes. When their phone runs out of space, the first apps they delete are the big ones they rarely open. Data is not free either. A customer on an MTN or Airtel bundle thinks twice before downloading a 150MB app on a weekday.

Networks also drop. A rider in Surulere loses signal under a bridge. A sales rep in Kaduna moves between areas with weak coverage. A good app for Nigeria must work offline where possible, save what the user entered, and sync later (sync means sending the saved data to the server once the network returns). Both Flutter and native can do all of this well. It depends on how disciplined your developer is, not on the tool. I will come back to app size later, because it is one place where Flutter carries a small cost.

Budgets, dollars and the developer market

Every app store account is paid in dollars. Apple charges 99 US dollars every year for a developer account. Google Play charges a one-time fee of 25 dollars. With naira card limits on foreign payments, I have watched projects stall for weeks because nobody could pay Apple. Plan for this early, with a domiciliary card or a virtual dollar card in your company’s name.

The developer market matters too. Nigeria now has a large and growing pool of Flutter developers, many of them trained through bootcamps and online courses. Good native iOS developers are fewer and more expensive, and many of the strongest ones have moved abroad or work remotely for foreign companies paying in dollars. That affects how easily you can hire, and more importantly, how easily you can replace someone who leaves. When a developer japas in the middle of your project, the tool you chose decides how painful the next month will be.

Flutter vs native: the honest comparison

Here is the side-by-side view I share with clients. It is not a scorecard where the higher number wins. Each row matters differently depending on what your app does, so read it with your own business in mind.

Speed and smoothness

For about nine in ten business apps (forms, product lists, bookings, payments, maps, chat), users cannot tell whether the app is Flutter or native. Screens scroll smoothly, buttons respond instantly, and pages load as fast as your server allows. Google itself has said publicly that it rebuilt parts of Google Pay with Flutter, and banks such as Nubank in Brazil have spoken about using it at scale. It is not a toy.

Native still wins at the extreme end: heavy animations, camera effects, video editing, 3D, and games. If your app’s main selling point is how it looks while it moves, native gives your developers more control.

One more lesson from experience. When a client tells me their app is slow, the tool is almost never the reason. Tunde, who owns two schools in Ibadan, complained that his parents’ app was “too slow because it is Flutter.” We checked. The app was downloading every student photo at full size and pulling 2,000 records at once instead of 20 at a time. We fixed the images and the paging, and the same Flutter app became quick on a Tecno Spark. Bad engineering is slow in any language.

Look and feel

Because Flutter paints its own screens, your brand looks exactly the same everywhere. Same colours, same fonts, same buttons. For a consumer brand that is usually a good thing.

Native apps automatically follow each platform’s habits. iPhone users are used to swiping from the left edge to go back, certain date pickers and certain menus. Android users expect a back button and slightly different layouts. A careless Flutter developer can build something that feels “a bit off” to iPhone users. A good one uses Flutter’s iPhone-style widgets (widgets are ready-made building blocks such as buttons and menus) where they matter, and nobody notices.

Access to phone features

Flutter reaches the phone’s features through plugins (a plugin is a ready-made add-on that connects the app to something like the camera). Camera, GPS, push notifications, fingerprint and face unlock, contacts, file uploads, Bluetooth and payments are all well covered. Paystack and Flutterwave both have tools or popular community packages that work with Flutter.

The gap shows up in two places. First, when Apple or Google releases a brand new feature, native developers can use it immediately, while Flutter support may take weeks or months. Second, when your app must talk to specialised hardware, such as a Bluetooth thermal printer, an Android POS terminal with its own software kit, or a fingerprint scanner for staff attendance, your developer may need to write some native code anyway and connect it to Flutter. That is normal and doable, but it adds time.

App size and storage

A Flutter app carries its own engine, so it starts a few megabytes bigger than an equivalent native app. A simple Flutter app on Android might download at 10MB to 18MB, while the native version might be 5MB to 10MB. For most users this is irrelevant. For a mass-market app aimed at budget phones in rural areas, where every megabyte counts, it is worth discussing. In practice, images, fonts and videos inside the app make far more difference than the choice of tool, so ask your developer how they will keep the download small.

Testing on the phones your customers really use

Whatever tool you choose, insist that the app is tested on real budget phones, not only on the developer’s laptop simulator or a brand new iPhone. I keep a small drawer of cheap Android phones in my Abuja office for this reason: a Tecno with 3GB of memory, an older Samsung, an itel with a cracked screen and a battery that dies by afternoon. If the app is quick and stable on those, it will be fine for most of your customers in Kano, Owerri or Warri. Ask your developer which phones they test on and ask to see the app running on one of them before you sign off any milestone payment.

Updates and bug fixes after launch

Every app has bugs after launch. A customer in Port Harcourt cannot log in on one particular phone model, or a button hides behind the keyboard on a small screen. With one Flutter codebase, the developer fixes the problem once and releases to both stores. With native, the same fix may be made twice, by two people, on two timelines, and the Android and iPhone versions can drift apart until customers complain that “the app on my friend’s phone does this, mine does not.” Ask each developer how quickly they can push a fix, and who pays for it during the first three months.

What Flutter vs native really costs in Nigeria

Now the part everybody scrolls to first. These are the ranges I see in the Nigerian market for professional work, including design, the phone apps, the backend (the server and database the app talks to) and an admin dashboard. They are estimates as at 2026. Prices change with the exchange rate and the scope, so treat them as a guide for planning, not a quotation. I break down the full picture in my separate guide on how much it costs to build a mobile app in Nigeria.

Why native is not exactly double

People assume native costs twice as much because there are two apps. It is usually less than double, because some work is shared. The design, the backend, the admin dashboard, project management and a lot of the testing plan are the same either way. Only the phone part is duplicated. In my projects, native usually lands between 1.6 and 1.9 times the Flutter price. If a quote is exactly double, ask the developer why.

The running cost after launch

Launch day is not the end of spending. Budget roughly 15 to 25 percent of the build cost every year for maintenance. Apple and Google both release a major new version of their phone software every year, and they regularly tighten store rules. Google Play, for example, requires apps to target recent versions of Android, and apps that fall behind can be hidden from new users. With native, every one of these updates is done twice. With Flutter, it is mostly done once.

Add your other running costs: server hosting, SMS for one-time passwords, push notification services, payment gateway fees, the yearly Apple fee, and a small support budget for user complaints. None of these change much between Flutter and native, but people forget them when comparing quotes.

Hiring and replacing developers

As at 2026, and depending heavily on the city and the person, a junior Flutter developer in Nigeria may earn between ₦250,000 and ₦500,000 a month, a solid mid-level developer between ₦600,000 and ₦1.2 million, and senior developers more, especially those working remotely for foreign firms. Experienced native iOS developers sit at the top of that range and are harder to find.

Chinedu, who runs an events business in Enugu, learnt this the hard way. His iPhone app was built natively by one developer. When that developer took a job in the UK, the iPhone app sat for seven months without a single update while the Android version kept improving. Customers on iPhone left angry reviews. With a single Flutter codebase, the Android developer he still had could have kept both apps alive.

When I recommend Flutter

After many app projects for Nigerian businesses, I recommend Flutter in most cases. Not because it is fashionable, but because the typical business app here is a set of screens, forms, payments and notifications, built on a limited budget, for users on both platforms. That is exactly what Flutter does best. These are the situations where I say yes quickly.

You need Android and iPhone on one budget

If you cannot afford to ignore iPhone users but your budget will not stretch to two native apps, Flutter lets you launch on both with one team. For a restaurant ordering app, a hotel and shortlet booking app, a church giving app, or a pharmacy refill app, this is usually the smartest path.

You are still testing the idea

Many apps fail, not because they were built badly, but because customers did not want them. When you are testing an idea, speed and cost matter more than perfection. Launch a lean first version, measure what people actually use, and improve from there. My guide on building an MVP without wasting money explains how to cut your first version down to what matters, and my app idea to launch service is designed for exactly this stage.

Internal apps for staff and field teams

Sales reps capturing orders in Onitsha market, inspectors logging site visits in Port Harcourt, teachers recording attendance in Jos, riders confirming deliveries across Abuja. These apps need to be reliable, work offline, and run on whatever phone the staff member owns. They do not need award-winning animations. Flutter is a very good fit, and one codebase keeps your maintenance cost low for years.

Apps that are mostly screens, lists, payments and maps

Musa runs a haulage company in Kano with trucks moving goods to Lagos, Onitsha and Port Harcourt. He needed a customer app to book and track loads, a driver app to share location and upload photos of signed waybills, and a web dashboard for his office. We built both phone apps in Flutter, sharing most of the code between them, in about eleven weeks. The driver app stores photos when the network is weak and uploads them later. Nothing in that project needed native code beyond a small piece for background location. If you are planning something similar, see how I approach delivery and logistics app development.

When I recommend going native

Flutter is not always the answer, and any developer who tells you it is should make you slightly nervous. There are clear cases where I advise clients to pay more and build natively, at least for one platform.

The app lives on specialised hardware

If your app must control a Bluetooth receipt printer all day, read NFC cards, talk to a fingerprint scanner, run on an Android POS terminal with the manufacturer’s own software kit, or connect to smart devices, native code gives you the most direct control. For example, a restaurant POS running on a dedicated Android terminal with a built-in printer is often best built natively for Android only, because it will never run on an iPhone anyway. Flutter can handle many of these cases with custom bridge code, but when the hardware is the heart of the product, I start with native.

Performance is the product

Video editing, live camera filters, augmented reality (placing virtual objects in the real world through the camera), fast-moving trading charts and serious games all push the phone hard. Native gives developers direct access to every bit of power the phone has. If your app lives or dies by how smooth it feels under pressure, pay for native.

You need the newest Apple or Android features first

Home screen widgets, Apple Watch companions, CarPlay and Android Auto, advanced background tasks and new privacy features all arrive native first. If your competitive edge depends on being first with these, native is the safer path. If you just need them eventually, Flutter usually catches up.

You already have strong native teams

If your company already employs good Kotlin and Swift developers, switching to Flutter means retraining people and rebuilding what works. Banks and large fintechs often sit here. That said, the choice is less clear than it used to be, and some large financial companies around the world run Flutter in production. The honest rule is: use the skills you already have, unless there is a strong reason to change.

What about React Native, Kotlin Multiplatform and web apps?

Flutter and native are not the only choices. Three other options come up in almost every conversation, and each has a place.

React Native

React Native is Meta’s cross-platform tool. Developers write in JavaScript or TypeScript, the same languages used for many websites, and the app uses the phone’s real buttons and menus. If your company already has a web team working in React, React Native lets them share skills and even some code. The ecosystem is huge.

In Nigeria I see more Flutter developers than React Native developers in the mobile space, but both are healthy. Between the two, my advice is simple: pick the one your chosen team knows best and has shipped real apps with. A great React Native team beats an average Flutter team every time, and the other way round too.

Kotlin Multiplatform

Kotlin Multiplatform is a newer approach backed by JetBrains, the company behind the Kotlin language. It lets developers share the business logic (the rules, calculations and data handling) between Android and iPhone, while keeping native screens, or sharing screens too with a companion tool called Compose Multiplatform. It is a good middle path for teams with strong Android skills who want native feel without writing everything twice. It is younger than Flutter, so the pool of experienced developers here is smaller.

Progressive web apps

Sometimes the best app is not an app from the store at all. A progressive web app (PWA) is a website that installs on the home screen, works partly offline and can send some notifications. No store approval, no Apple fee, one codebase, and updates reach users instantly. For many small businesses, especially those whose customers only order occasionally, this is the cheapest sensible start. There are limits, mostly on iPhone, and I explain them in my guide on progressive web apps as a cheaper alternative to a mobile app.

Mistakes I see business owners make

Most failed app projects I am asked to rescue did not fail because of Flutter or native. They failed because of decisions around the tool. These are the ones I see again and again, from Lagos to Uyo.

Letting the developer’s comfort decide

A developer who only knows native will tell you Flutter is unreliable. A developer who only knows Flutter will tell you native is a waste of money. Both might be honest, but they are describing their own skills, not your business. Ask every developer: “What would make you recommend the other option?” If they cannot name a single case, keep asking questions or keep looking.

Building two native apps before proving demand

This is the most expensive mistake, and I have watched it drain good businesses.

Ibrahim, a property developer in Abuja, spent ₦24 million on separate native Android and iPhone apps for tenants to pay rent and report repairs. Eight months after launch, fewer than 300 tenants used them, and most still paid by bank transfer and reported problems on WhatsApp. A ₦5 million Flutter app, or even a simple web portal, would have taught him the same lesson for a fifth of the price. The lesson: prove people want it first, then invest in polish.

Forgetting that the app is only the front door

The phone app is what customers see, but the real work happens behind it: the backend, the database, the admin dashboard where your staff approve orders, the payment reconciliation, the reports. Some quotes look cheap because they only cover the phone screens. Before you compare Flutter and native prices, make sure both quotes include the same backend and dashboard. Otherwise you are comparing a house with a gate.

Not owning your accounts and your code

Whichever tool you pick, insist on three things. The Apple and Google developer accounts must be registered in your company’s name, with your email. The code must live in a repository (an online storage place for code, such as GitHub) that you own, with the developer added as a collaborator. And you must receive the login details for every service the app uses. I have met owners who could not update their own app because the only developer with access stopped answering calls.

Ignoring app store rules

Apple reviews every iPhone app before it goes live and rejects many first submissions. Common reasons include missing privacy details, broken links, demo accounts that do not work, and payments for digital goods done outside Apple’s system. Read Apple’s App Store Review Guidelines with your developer before you build, not after you submit. Google Play is gentler at first but strict about privacy and permissions. None of this changes between Flutter and native, but it catches out first-time founders all the time.

How I decide in one afternoon: my checklist

When a client comes to me with an app idea, I do not start with the tool. I start with questions. Here is the list I work through, usually in a single two-hour session over tea at my desk in Abuja or on a video call.

1. Who are the users, and what phones do they carry? Mostly Android, mostly iPhone, or a real mix?
2. What is the one job the app must do well? Book, buy, track, pay, learn, report?
3. Does the app depend on special hardware or heavy graphics? Printers, card readers, AR, video?
4. What is the total budget for year one, including maintenance, servers and store fees?
5. How soon must it launch? Is there a season, event or investor deadline?
6. Who will maintain it for the next three years? In-house staff, an agency, a freelancer?
7. Is there an existing team or codebase? Web developers who know React, Android developers who know Kotlin?
8. Must it work offline? For how long, and what data must survive a network drop?
9. Does it need a website or dashboard too? Could a web app come first?
10. What happens if the main developer leaves? How quickly can someone else take over?

Once those answers are on paper, the choice usually becomes obvious. This small table captures how the answers point.

Back to Amaka and her laundry shops. Her customers were split roughly 65 percent Android and 35 percent iPhone. The app needed bookings, pickup scheduling, payment through Paystack, order tracking and push notifications. No special hardware. We went with Flutter, launched both apps in ten weeks, and she spent part of the savings on a proper launch campaign in Lekki. That is the kind of trade-off I want every client to make with open eyes. If you want to read the official technical side, the Flutter website has good plain overviews and showcases.

Key takeaways

• Flutter vs native is a business decision, not a technology contest. Start from your users, budget and hardware needs.
• Native means two separate apps (Kotlin for Android, Swift for iPhone), usually costing 1.6 to 1.9 times a Flutter build.
• Flutter suits most Nigerian business apps: bookings, stores, schools, churches, delivery and staff apps on mixed phones.
• Go native when the app depends on specialised hardware, heavy graphics, or the newest platform features on day one.
• Slow apps are usually badly built apps. Images, paging and backend design matter more than the tool.
• Plan for dollars: Apple’s yearly fee and Google’s one-time fee need a card that works abroad.
• Own your code and store accounts in your company’s name, whichever option you choose.
• Prove demand before polish. A lean first version beats two expensive apps nobody uses.

Frequently asked questions

Your next step: talk it through before you spend

If you have an app idea, or quotes on your desk that do not agree with each other, send them to me before you pay anyone. I will look at your users, budget and timeline, and tell you honestly whether Flutter, native, React Native or a simple web app makes the most sense, even if the answer is “not yet.” You can see the kind of apps and systems I build on my projects page, learn more about my mobile app development service in Nigeria, and book a free consultation when you are ready. If you prefer, message me on WhatsApp from the site and we can start the conversation there.