a new 'base app' which gon get deployed on prem

README.md

@@ -10,7 +10,7 @@ Currently in alpha. Greenfield. Subject to change.
 
 1. Admin generates a unique link and assigns it to a user (or a slot).
 2. User opens that link in their browser — served by `apps/front`.
-3. User waits while a Docker-Android device is allocated to their session.
+3. User is shown a loading screen for good UX purposes
 4. User is prompted to install the PWA.
 5. User opens the PWA — they are routed into a live stream of their assigned Android instance.
 6. Admin manages the entire fleet from `apps/main` (the dashboard), which communicates with `apps/orchestrator` running on each VPS to control Docker-Android containers.
@@ -54,11 +54,12 @@ Currently in alpha. Greenfield. Subject to change.
 - [ ] Admin dashboard: Links page — generate links, view detail, configure linked device, revoke, delete
 - [ ] `apps/front`: validate incoming link token on request
 - [ ] `apps/front`: return appropriate error page for invalid/expired/revoked links
+- [ ] Front: keep on checking for link status change, if it gets revoked, we cutoff the connection
 
 ### PWA & User Session Flow (`apps/front`)
 
 - [ ] `apps/front`: serve static PWA shell (HTML + manifest + service worker)
-- [ ] `apps/front`: wait/loading page — poll for device allocation status
+- [ ] `apps/front`: wait/loading page — just for show with a 3-5s duration
 - [ ] `apps/front`: PWA install prompt flow (beforeinstallprompt handling)
 - [ ] `apps/front`: session binding — tie the PWA launch to the user's allocated device
 - [ ] `apps/front`: route/proxy authenticated PWA requests to the Android instance stream