Aaliya Traders

The brief

Ship a storefront the client can run alone — add a product, price it, photograph it, publish it — while every one of those products earns its own indexable URL.

What was in the way

• No in-house technical staff, so any solution requiring a deployment to change a price was a non-starter.
• A catalogue that changes weekly, which rules out a hand-built static site.
• Product pages needed to rank individually — a single-page catalogue would have surfaced one URL for the entire inventory.
• Mobile-first buyers on variable connections, where a heavy JavaScript bundle costs real orders.

What we did

1. 01

   Firestore as the product system of record

   Products, pricing, stock state and imagery live in Firestore with Firebase Storage behind them, so the owner publishes changes from an admin surface and the storefront reflects them immediately — no build, no deploy.

2. 02

   A route per product, and a sitemap that keeps up

   Every SKU resolves to its own URL under /product/:id, and the generated sitemap now carries 84 entries covering the catalogue, the browse page and the standard company routes.

3. 03

   Angular with route-level code splitting

   The application ships as lazily loaded chunks so the landing route stays light, with Firebase SDK loading isolated from first paint.

4. 04

   Complete social and PWA metadata

   OpenGraph and Twitter cards with a 1200×630 banner, themed browser chrome, and installable-app icons — so a WhatsApp-shared product link renders as a card rather than a bare URL.