Building a cross-platform app with Flutter: lessons from Al-Mubin

What building an offline-first Quran app taught us about Flutter, and how we would choose between Flutter and React Native.

We are building Al-Mubin, a free, non-commercial Quran app that works fully offline, with Flutter. It is still in development, and it is for both Android and iOS from one codebase. Building it has taught us where Flutter is a very good fit and where it still needs care. This article is for founders and product owners deciding how to build a mobile app, and it ends with when we would pick React Native instead.

Why Flutter for this app

A Quran reader has unusual needs. The text has to look exactly right on every phone, with every diacritic in place. It has to work with no connection. It has to scroll smoothly through long pages, in several reading layouts.

Flutter draws its own interface instead of using each phone’s built-in widgets, so text looks the same across devices and Android versions. That control suited an app where the text is the product. It also gave us one codebase. The rest of the stack is ordinary: Riverpod for state, a local SQLite database through Drift, just_audio for recitation and go_router for navigation.

What worked

  • Offline-first from day one. The text ships inside the app and the data lives in a local database, so reading never waits for a server. We keep database upgrades safe with an automated test that migrates an old database to the new version.
  • Several scripts and languages in one reader. The app has three Quran scripts (Uthmani Hafs, IndoPak and Uthmani), three reading views, and translations that include Urdu and Persian. Each script is defined in one place as a text source plus its font, so switching scripts is a setting, not a new screen.
  • Right-to-left layout. Flutter handles right-to-left text well, but every language needs its own check. Our Urdu translation uses a Nastaliq font, and we had to fix translations that started at the wrong edge of the screen.

What was hard

  • Text and font have to match. We first drew one text source in a font made for a different one. A few characters came out wrong: one verse showed a filled circle where a symbol belonged. The fix was to bundle the text that was prepared for that font. Reading apps are easy to get subtly wrong, and only a person looking at the screen catches it.
  • Small signs break if you style them separately. We tried enlarging the pause signs in two scripts. In those texts each sign is attached to its letter, so putting it in its own text span broke how the letters join. We left them alone in those scripts.
  • Reminders on modern Android. Prayer-time reminders need alarms that fire on time. On Android 14 and later, the permission for exact alarms is off by default on a fresh install, so the app has to ask for it. If the user refuses, reminders fall back to alarms that can be a few minutes late. The store also asks for a declaration when you use that permission. Flutter does not hide any of this, and it is the kind of platform detail every mobile project has to plan for.
  • Automated tests are not enough. The project has about 300 automated tests, and they pass. They cannot see a wrongly drawn character or confirm that an alarm fires on a real phone. We checked fonts, scripts and alarms on an actual device.

Flutter or React Native

Both build iOS and Android apps from one codebase, and either can ship a good product. We would choose between them like this:

  • Choose Flutter when the interface is custom, the app is heavy on text or graphics, you want the same look on every device, and you are starting without an existing JavaScript team.
  • Choose React Native when your team already works in JavaScript or React, you want to share code or developers with a React website, or you want the phone’s standard components and look.
  • Either way, some work is platform specific. Notifications, permissions, background tasks and store rules need attention on each platform.

What it means for your budget

One team and one codebase usually mean less duplicated work than building two separate apps, and one set of tests covers most of the logic. They do not remove the platform-specific work above, so ask any developer you hire to name it in the scope: the permissions, notifications and store requirements your app needs. We don’t quote a price here because it depends on what you are building.

Talking to us

If you are choosing a way to build your app, read about our mobile app development service, or tell us what you are planning. We will say honestly whether Flutter, React Native or something else fits.

Have an idea? Let’s build something great.

Tell us what you’re working on. We’ll get back to you with questions, ideas and next steps.

Chat with us