11. Apps (the surfaces)
Purpose — The client surfaces: a Next.js web storefront/admin and a React Native app suite (Customer, Technician, Dealer), sharing a themeable design system driven by the Tenant Config Contract.
Personas served
All.
Surfaces
| Surface | Tech | For | Highlights |
|---|---|---|---|
| Web storefront | Next.js + Tailwind + Tailwind UI | Customer | SSR/ISR, SEO, i18n, configurator, calculators |
| Team dashboards | Next.js + shadcn/ui | Admin/Manager | role-scoped BI (Admin) |
| Medusa Admin | React | Admin | commerce ops |
| Customer app | React Native | Customer | shop + My Products + service/AMC + loyalty |
| Technician app | React Native | Technician | offline-first field ops |
| Dealer app | React Native | Dealer | ordering, ledger, targets, leads |
| (opt) Electrician loyalty app | React Native | Installer/electrician | scan-QR → points |
Key capabilities
- Shared design system — web built on TailwindCSS + shadcn/ui + Tailwind UI, themed at runtime from tenant config (logo/colors/fonts/locale) via CSS variables; apps share the same design tokens. See Frontend & Design System.
- Customer app — browse/buy, register warranty, raise complaint, track technician ETA, renew AMC, buy spares, loyalty.
- Technician app (offline-first) — job list, navigation, customer/product/warranty context, checklists, photo/video, signature, parts used, time/expense, on-site close-out, sync when back online. See FSM.
- Dealer app — order booking, ledger/credit, targets, stock, leads. See DMS.
- Multilingual —
i18next(i18n). - Push notifications — via Notifications.
Offline strategy (technician app)
- Local store (e.g. WatermelonDB/SQLite) for assigned jobs + reference data.
- Queue mutations; conflict-safe sync with idempotent server handlers on reconnect.
- Media captured offline uploaded on reconnect with resumable upload.
Data owned
None — clients of the modules' APIs via the BFF. Local caches only.
Events
Consume server push/notifications; emit user actions through module APIs.
Tenant-config knobs
Branding tokens, enabled surfaces/features per tenant, supported locales, push keys.
Dependencies
Every module via BFF; Tenant Config, Notifications, Testing.
Open questions
- One RN app with role-gated modes vs three separate apps (recommend: separate Customer vs Technician; Dealer could merge with Customer behind role).
- Web admin: extend Medusa Admin vs standalone dashboards (plan: dashboards standalone, commerce ops in Medusa Admin).