Conversation
Fade-in + slide-up animation for the title and info text using FirstOrderFilter, with sequential icon fade-in on the status bar. Right-half click retriggers the animation for testing. Includes fake version text fallback for development. Made-with: Cursor
Made-with: Cursor
Made-with: Cursor
Made-with: Cursor
Made-with: Cursor
Made-with: Cursor
Made-with: Cursor
Contributor
UI Previewmici: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Just to show animation, has testing bits like half the homescreen is an animation trigger, etc.
Also, I think we consult with adeeb on how to handle the build info text; caching it, pre-loading it based on release, having a general filler text, idk rn
As far as behavior, when the animation should trigger:
After boot (needs some delay to trigger after the comma screen disappears) < ez for sure
Whenever screen is woken? I can see this becoming slightly annoying for developers since its a tiny bit of visual noise, but the sequence happens fast enough (and doesnt otherwise prevent usage).
Instead of 2, have some sort of timeout, like 15min or something that it waits until waking the screen will retrigger the animation (otherwise waking the screen would just instant on if this timeout hasnt been reached)
When ignition, there has to be some additional handling of >wait for animation to play >then slide over to onroad
So if this is all too complicated to test/think about before next release, then it's ok to only have this play on boot for now, and we can slowly bring it to more appropriate places.
Essentially, the end goal is to feel like when a person "turns on" their device by starting their car, then it plays the animation but otherwise it should feel more like your smartphone in standby mode.
Given the unique usage/context of the comma 4, we can definitely get this balance right with some simple rules like suggested above.