Haitham Assoli

the project

All projects

Fazawwijuhu

A supervised platform for lawful marriage introductions.

A platform that introduces people seeking marriage under explicit, published conditions with administrative supervision throughout, deliberately structured to keep the process within religious bounds rather than reproducing a dating app.

Fazawwijuhu

the facts

Role
Solo
Year
2026
Status
Live
Category
Web

Built with

  • Next.js 16
  • React 19
  • TypeScript
  • Convex
  • Better Auth
  • Tailwind v4
  • shadcn
  • Base UI

Where to find it

overview

What it is, and why it exists.

The default shape of this product is a dating app, and the default shape is exactly what the users this is for want to avoid. The design problem was structural rather than visual: what does the flow look like when open browsing and private messaging are the things you are trying to prevent?

The answer was a form-driven, admin-supervised pipeline. Applicants answer a structured questionnaire that differs by gender, agree to explicit published conditions, and every introduction passes through administrative review rather than happening directly between two users.

Built on Convex with Better Auth, where the server holds the rules and the client is only a view of them.

problems

Challenges

The rules are the product, so they cannot live in the UI

the problem

If eligibility and visibility rules are enforced by which screens the client renders, anyone who inspects the network can step around them. For this product that is not a bug class, it is a breach of the entire premise.

what I did

Convex functions are the source of truth and the enforcement point. The client cannot request what it is not entitled to see, regardless of what it renders.

The questions must change without a deploy

the problem

The form questions and the published conditions are religious and editorial content, not engineering decisions. Having them hard-coded means the person who owns that content has to go through me to change a sentence.

what I did

Questions and Arabic copy live in dedicated, owner-editable config modules, separate from application code and marked as such in the repo layout.

Publishing someone's details is irreversible

the problem

An accidental disclosure here is not a UI bug. It affects a real person's reputation and family, and it cannot be undone by deleting a record afterwards.

what I did

Nothing is visible by default. Publication requires explicit, recorded consent from the applicant plus administrative approval, so disclosure needs two deliberate acts rather than one missing check.

after

Results

  • Server-enforced visibility rules. The client cannot request what it may not see.
  • Questions and religious copy editable by the product owner without a deploy.
  • Publication gated behind recorded consent plus admin approval.

next

Next project

Al-Tibyan Educational Center

Quran memorisation circles, run properly on a phone.