Optimize POD Structure Initialization for Apps #204
Description
Description
Currently, the solid_login_auth_handler.dart in Solidui and initialStructureTest in rest_api.dart in Solidpod performs a comprehensive check of the folder and file structure every time a user logs in. For Geopod, this involves approximately 13 network requests (6 folders and 7 files/ACLs).
While necessary for the first run, performing these sequential (or even parallel) network requests on every login creates a "loading hang" of ~10 seconds, negatively impacting the UX for Geopod, Healthpod, and Notepod.
Why
So that as a user, I can access the app dashboard immediately after login without waiting for redundant file system verification.
Closing Criteria
Checklist for closing the issue:
- State Persistence: Introduce a persistent "First-Run" or "Initialization" flag (stored locally or as a single .initialized metadata file on the POD) to bypass checks for returning users.
- Parallel Execution: Ensure any mandatory startup checks in rest_api.dart utilize Future.wait() to resolve concurrently rather than sequentially.
Alternatives
Background Verification: Redirect the user immediately and run the structure check as a non-blocking background task.