I pulled the latest changes from v0/rafalkojames-2398-626fe2e7 in umawiamapp-mobile-web.

Let me first understand the full current codebase structure before converting to URL-based routing.

Now I have full understanding of the codebase. The current architecture has everything in BusinessView as a single component with activeTab state. I need to convert this to proper Next.js App Router routes:

• /app/dashboard - Dashboard page
• /app/calendar - Calendar page
• /app/clients - Clients page
• /app/settings - Settings page

I'll create a shared layout at /app/(business)/layout.tsx with the BottomNav and shared state (appointments), and each tab becomes its own page. The root / page keeps the view toggle (business vs client).

Now I have full context. Here's my plan:

1. Create an AppointmentsProvider context to share appointment state across routes
2. Create a (business) route group with a shared layout (header + BottomNav)
3. Create individual pages: dashboard, calendar, clients, settings
4. Update BottomNav to use next/link + usePathname
5. Update root page to redirect / to /dashboard or show view toggle
6. Keep the client view at a separate /book route

Let me build this: