QuranHub
QuranHub is a Quran app for iOS and Android, with a mushaf reader (the Quran laid out as on the printed page) and recitation audio. It's a solo project.
The problem
Most Quran apps are either reference tools or copies of engagement apps, with streaks and leaderboards. That doesn’t suit someone who reads a little at a time or is coming back after years away.
In QuranHub a one-minute visit counts and a missed day is forgiven. Onboarding doesn’t ask about faith. Readers choose what others can see, and the app has no ads or third-party analytics.
What I built
The reader shows the mushaf as printed, glyph for glyph, in two print editions: Madinah and, since version 1.6, Warsh. There is a word-by-word view and there are translations in English and Indonesian. Recitation plays verse by verse and can be downloaded for offline use, and a Learn tab helps with memorizing.
Sign-in with Apple or Google is optional. With an account, a reader’s data syncs across devices and they can appear on a weekly reading board under an anonymous handle.
Decisions
Replacing PocketBase with a Go server
The first version ran on PocketBase. Before any real user data existed, I replaced it with a single Go server split into modules, with its data in SQLite. Only seven files in the app talked to PocketBase directly, so the switch was cheap. The server ships as one binary in a minimal container, and Litestream copies the database to backup storage as it changes. For sign-in, the server checks the Apple or Google token itself and then issues its own session.
I turned down heavier options such as a dedicated identity service and managed Postgres, because the project had to stay small and cheap to run. In exchange I maintain sign-in and deployment myself.
Sync rules came first
The app works offline, so the database on the phone is the source of truth and sync runs in the background. I wrote the merge rules down before any feature stored data. Records that are only ever added, such as reading visits and highlights, merge by id. Records that change keep the latest version by the server’s clock, since phone clocks drift and people set them by hand. Deletes sync as markers, so something removed on one device disappears on the others. Ordered lists use fractional ranks, which lets two devices reorder the same list without losing entries.
Those rules still missed one case. An older build could push a stripped copy of a record it had never edited and wipe fields on every other device. I changed the server to merge each record key by key and added a schema version to every push, so an older build can no longer overwrite data it doesn’t understand.
The word-by-word view took three tries
Drawing each word as its own widget drifted away from the printed layout. Squeezing translations into the gaps between printed lines kept the layout, but readers couldn’t read them. The version that shipped keeps the printed lines intact and gives each word its own cell, and it came out of feedback on the second version.
One audio file per surah
Cutting recitation into one file per verse by loudness clips words and splits the echo at the end of a verse. QuranHub plays one continuous file per surah (chapter) and jumps between verses with a timing table.
Testing and releases
There are 760 test files on the Flutter side and 264 Go test functions on the server. Some mushaf pages also have golden tests, which compare the rendered page with a saved image, so a font or layout change that moves a glyph fails the build.
CI also runs custom lint rules I wrote. One keeps the code’s layers apart, and another blocks pop-ups while recitation is playing. Font and audio licenses are checked on every run, and the tests run under three time zones. Every push to main ships a build to TestFlight, and tagging a version sends it to App Store review. There have been seven releases so far, from 1.1.0 in July 2026 to 1.6.0.
What’s left
The Android version is still in Google Play testing. Before it can go public, the listing has to pass a closed test with outside testers. A scholar also has to review the reading board, and the Warsh print, which arrived in 1.6, is still being finished along with a new tab bar.