Score A-Star
- Next.js 16
- Turborepo
- Firestore
- Cloudflare R2
the story
A family publishing business in Egypt ran on WhatsApp orders, a Facebook catalogue, loose PDFs and spreadsheets. I rebuilt it as four Next.js apps sharing one account and one design system.
Solo, over about a year: frontend, backend, data model, design system and deployment.
- 01
Store
Catalogue by subject and year, guest checkout, shipping priced by city and parcel weight.
- 02
A-Practice
Generated quizzes, lesson notes, two live games and a parent–child link with approval.
- 03
Library
Readers see only the books granted to them, on one bound device per account.
- 04
Console
One installable admin that runs all three, built on Server Actions rather than API routes.
- 01
A leak names its reader
Every page is marked with the reader's account id the first time it opens, strong enough to survive screenshots, recompression and cropping.
- 02
One device per account
A non-extractable ECDSA key in IndexedDB answers the server on every render, so a copied cookie on its own gets nowhere.
- 03
A courier with no API
A nightly job reads the courier's public tracking endpoint and closes out deliveries that nobody marked as done.












