One platform, product-local URLs
Hostname-aware routing maps clean public subdomain URLs into shared internal route trees instead of maintaining five separate applications.
Multi-surface commerce platform02 / 04
Spotly
Five product surfaces. One operating network.
SPOTLY
01Customerspotlyafrica.com
02Businessbusiness.spotlyafrica.com
03Driverdriver.spotlyafrica.com
04Staffstaff.spotlyafrica.com
05Adminadmin.spotlyafrica.com
ONE SECURE PARENT-DOMAIN SESSION BRIDGE
ROLE / OWNERSHIP
Product architecture · full-stack engineering · auth design · operations UX
STATUS
Production platform
TIMELINE
2026
A marketplace stops being one interface as soon as customers, businesses, drivers, staff, and platform operators all need different information and authority.
Spotly has five public product origins but one underlying operating network. Identity, permissions, navigation, payments, delivery state, notifications, and kiosk behavior must survive domain boundaries without duplicating the product five times.
KEY DECISIONS
The work behind the screen.
Session continuity across sibling domains
A verified Firebase ID token becomes a secure parent-domain HttpOnly session. Sibling products bootstrap their local Firebase session with a custom token.
Keep high-impact operations behind server APIs
Driver approval, sensitive delivery actions, payout-related data, and kiosk credentials are not left to direct browser writes.
Design each role as its own product
Customer, Business, Driver, Staff, and Admin use one platform, but the information density and action language are role-specific.
Keeping clean product-local URLs while sharing one codebase required hostname-aware routing and a deliberate authentication bridge instead of relying on origin-scoped browser persistence.
WHAT THE BUILD PROVES
Evidence, not adjectives.
- Five role-specific products share one platform rather than five duplicated apps
- Sibling subdomains restore authenticated state through a server-issued session bridge
- High-impact driver, payout, delivery, and kiosk actions are server mediated
Next.jsReactFirebase AuthFirestoreStorageAdmin SDKApp CheckCloud MessagingPaynowResendVercel
VERIFIABLE EVIDENCE
Inspect the work.
- Five production product origins are documented in the repository.
- The cross-subdomain session bridge is part of the production architecture.
- Marketplace, delivery, kiosk, finance, staff, driver, and admin operations share one platform.
Have something complicated that needs to feel simple?