shadcn/ui baseline installed
Hanap Laba app shell for customers, branches, and admins.
The web app now uses shadcn-style primitives, Tailwind tokens, and a reusable app shell so product screens can be built on a consistent foundation.
Foundation status
Core UI primitives are now in place for future feature work.
Design systemshadcn/ui
Routingcustomer / branch / admin
Data layerReact Query ready
Customer routes
Nearby discovery, bookings, orders, invoices, and post-MVP chat placeholders.
Branch discovery and booking UX
Branch routes
Dashboard, orders, bookings, customers, services, invoices, and settings placeholders.
Operations and capacity management
Admin routes
Tenants, subscriptions, and platform controls placeholders.
SaaS oversight and support tools
What changed
The shell now reflects the stack requirement instead of a generic inline-styled page.
Shared UI primitives live in
components/ui, Tailwind tokens are configured, and the layout/header are now built from reusable components.Next step
Build the first real customer and branch screens on top of this base.
This is intentionally a UI foundation only. Business logic, data fetching, and auth flows stay unchanged until the next implementation phase.