For most of the internet's history, software built "for Muslims" has meant the same thing: a mediocre product with religious functionality bolted on, monetized aggressively, sold to an audience that didn't have alternatives. The Quran app you installed and quickly uninstalled. The "halal browser" that was a Chromium fork with a green logo. The prayer-time widget that demanded location permissions, push notifications, and an email address before it would tell you when Maghrib was.
We built Noorani because that bar was set too low for too long.
Noorani is a desktop browser built for Muslims, by Muslims, with the Islamic utilities most of us have learned to live without — woven into the browser itself rather than scattered across five tabs and three apps. Prayer times computed locally on your machine, with no location data sent anywhere. Qibla direction in the toolbar. Hijri date in the UI where Gregorian dates usually sit. Quran one keystroke away. Trackers blocked by default — not because the West is the enemy, but because the modern web's data economy was built without us in mind, and we'd rather not opt into it on principle.
It is also a Chromium-based browser that opens websites and renders pages, which we mention because some readers will be wondering if "Muslim browser" means something exotic. It does not. It means the browser you already use, with the parts that should have been there from the start.
Why a browser
Five times a day, around 1.8 billion people stop what they're doing and pray. Most of them are sitting at a computer when at least two of those breaks happen. Every one of them is using software built by people in San Francisco, Mountain View, or Redmond who weren't thinking about Asr when they shipped.
This isn't a grievance. It's an observation. The web was built by people thinking about the problems in front of them, and a Muslim user's day was simply not on that list. The result is that the largest single religious community in the world has spent thirty years adapting to software built for someone else.
That made sense for a long time. It doesn't anymore. Engineering talent is global. Distribution is global. The reason no one had built a credible browser for Muslims wasn't technical — it was that no one had done it well. We're trying to do it well.
Why a blog
A browser is one job. Explaining why is another.
This blog exists because shipping software is not enough on its own. There are technical decisions behind Noorani that deserve to be written about — why prayer times are computed locally, why we picked Chromium over Firefox, what it actually takes to build a right-to-left native UI in a desktop application. There are observations about the modern web that don't get made anywhere else, because the people best positioned to make them aren't writing in English, or aren't writing publicly, or aren't writing at all.
We're going to write about five things. The privacy and tracking economy, and what to do about it. The engineering and design choices behind Noorani, in public, as we make them. How the global Muslim community actually lives online — which is more interesting than either Muslim media or Western media tends to admit. The slower question of what "intentional technology" means for a tradition that prays five times a day. And, occasionally, practical product writing for people actually using the browser.
What we won't write: religious instruction, fatwas, or anything that belongs to scholars rather than engineers. There are a thousand better places on the internet for that, and adding one more would be both unhelpful and out of place.
The bar
There's a test we use internally for everything that goes out under the Noorani name. A piece of writing should be something a thoughtful engineer at Stripe would read and respect, and something a Muslim grandmother in Lahore would feel quietly proud of. If it only lands for one of them, we rewrite it.
That's a high bar, and we'll miss it sometimes. When we do, tell us. The browser is open source on GitHub, and the blog is, for now, a one-way conversation we'd like to make two-way over time.
We're at v1.0.0-alpha as of today. The browser works. It does the things on the box. It also has the rough edges that anything labeled "alpha" tends to have, and we'd rather ship those honestly than wait another year polishing in private.
If this is the browser you've been quietly waiting for, download it, read the source, and come back when we publish next week.