The Brief
Value Islam came to us with a simple ask and a wide-open scope: build a home for their work — one platform, spanning web and mobile, covering everything from learning content to community to giving. There was no legacy system to migrate, no existing design language, no prior version to iterate on. Just a blank canvas and an NGO that needed to exist online, properly, for the first time.
This was also my first real project. Not a tutorial, not a clone — an actual client, an actual deadline, an actual product that real people would use.
The Setup
It was a two-person build. I handled **design and frontend engineering** — both the React website and the Flutter mobile app — and was involved from ideation, so there was a product layer to the work too: figuring out what the platform should even be before figuring out how to build it. My partner - @Yameen handled the backend, built in Python.
Stack:
- Web — React
- Mobile — Flutter
- Backend — Python (built by @Yameen)
Learning on the Job
Here's the honest part: I didn't know Figma properly going in. I didn't know Flutter either. Both were picked up while building this — not before.
That shaped everything about how the project ran. Design decisions and implementation constraints were discovered at the same time, not sequenced neatly like a textbook process. Some screens got redesigned because I learned a Flutter layout trick a week too late. Some Figma components got simplified because building them pixel-perfect in code wasn't worth the time yet.
Looking back, this was less "here's my process" and more "here's what happens when you build in public with your own inexperience." That's exactly why it mattered — every project since has been easier because this one wasn't.
What Value Islam Covers
The platform wasn't scoped narrow. It brought together the pieces an Islamic NGO typically needs scattered across five different tools:
- Learning and content
- Community-facing features
- Giving and support
Bringing all of that into one coherent web + app experience — with one visual language across both — was the actual design problem, more than any single feature.
What I'd Point To
There's no traffic chart or download count to show off here — this predates the point in my career where I was instrumenting things properly. What this project actually represents is different: it's the proof that I can walk into total ambiguity — new tools, no team beyond one other person, a client waiting — and come out the other side with a shipped product across two platforms.
Everything I've built since — Raacord, the Asasika leadbot, Pafex — inherited habits I first had to force myself to learn here.