Auth
Login before dashboard access
The public Next.js pages do not start the Flutter app. Users move into the secure app only through login.
Security
Public website outside. Secure workspace inside.
The site architecture keeps public discovery separate from authenticated business operations. That makes the landing page faster and the dashboard clearer to protect.
Roles
Permission-based screens
Each role can be limited to the modules and actions needed for that person or branch.
Branches
Branch-aware visibility
Branch context helps prevent staff from accidentally working in the wrong operating scope.
Sessions
Cash and activity controls
Daily session workflows make collections, expected totals and closing actions easier to review.
Data
Business data stays in the app
Marketing pages only contain public content, assets and metadata; business records stay behind authentication.
SEO
Crawlers see public pages only
Robots and sitemap entries are focused on marketing routes while app areas are excluded.
Access model
Login is the boundary
This split also improves the user experience: visitors get a fast site, and signed-in users get the full Flutter application after authentication.
- 1. Visitor opens a public Next.js route.
- 2. Visitor clicks Login when ready to work.
- 3. Browser moves to the Flutter app login route.
- 4. Flutter authentication decides the correct dashboard after success.