Hobber
Jan 2026 — Present · Vendor platform for entertainment, recreation, dining & tourism vendors · UAE
Architecting a vendor platform from an empty repo: feature slices over one sprawling dashboard.
Problem
A vendor platform needs auth, accounts, dashboards, scheduling, payouts, integrations, and team access — and none of it existed. Built as one surface, it turns into a monolith before the first release.
Move
Architected the dashboard from scratch in React and TypeScript as the sole frontend engineer, on a modular, feature-based structure, so each domain owns its own slice and adding one is adding a folder rather than a refactor.
Result
Seven core platform modules and five vendor workflows in production on one shared component layer — with the structure still legible enough that a new domain is a new folder, not a refactor.
Constraint
Upfront architecture vs. time to first screen
- React
- TypeScript
- Feature-sliced architecture
- Vitest
- Playwright
- REST APIs
Results
- Platform modules shippedeach in its own slice
- 7
Count
Authentication, vendor accounts, dashboards, scheduling, payouts, integrations and team access — shipped as independent feature slices over one shared component layer.
- Vendor workflows built on the shared layer
- 5
- Test layerVitest for unit and integration, Playwright for E2E
- 0→1
- Page-load baselineno before/after to report yet
- not yet measured
Composition and boundary reads across the codebase I architected — a structural measure, not a performance one. The platform is 7 months in, so there is no before/after perf number to report yet.
