Skip to content

Conversation

@samcday
Copy link
Owner

@samcday samcday commented Jan 26, 2025

No description provided.

Previously the shell was doing it in the a handler, which was
technically incorrect since it's possible that the loading of users is
slow enough to not be done by the time shell readiness signal fires.

The main motivation for doing it, though, is to prepare for the scenario
where the shell starts up without being initially locked, which is
necessary to support a "first-run" app.
this is set once all known users have loaded from AccountService
Makes it possible to implement a test with only a single user (Phoshi,
of course)
The "trivial case" is when there is one user and one session available
for selection. In this case, we make the keypad the default page as well
as switching to it.
This test will pass in CI but fail on local dev machines with more than
one session available, as I haven't properly mocked that out yet.
@samcday samcday force-pushed the optimize-trivial-flow branch from 49eb669 to 787c13c Compare January 26, 2025 19:29
@github-actions
Copy link

The CI build recorded and generated some videos

Demo video (shown on README and release notes)

accent-colours

keypad-shuffle

simple-flow

trivial-flow

@joelselvaraj
Copy link

I can confirm both flows works as expected. Once i delete the extra session files in pmos, phrog directly boots to the phosh lockscreen when only one user and one session is present.

@samcday
Copy link
Owner Author

samcday commented Jan 29, 2025

I can confirm both flows works as expected. Once i delete the extra session files in pmos, phrog directly boots to the phosh lockscreen when only one user and one session is present.

Thanks for testing 🎉

@samcday samcday merged commit 5342073 into main Jan 29, 2025
10 checks passed
@samcday samcday deleted the optimize-trivial-flow branch February 3, 2025 12:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants