feat(mobile): register flow + onboarding redesign - #60
Merged
Conversation
Add a RegisterScreen with email + password. Rework the final onboarding slide into a three-tier hierarchy: primary Create account, secondary Log in, tertiary Skip for now. Mirror that hierarchy on the home sheet guest state and in Settings > Account so guests can register from anywhere. Login/Register screens accept an onSuccess callback so onboarding completes after either auth path succeeds. Restores the pre-paint-mode onboarding copy (anonymous-session bullet, "use without account" wording) now that painting is available on iOS.
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
1 participant
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.
Summary
LoginScreenandRegisterScreennow accept anonSuccesscallback so onboarding completes after either auth path succeeds.registerTitle / registerSubmit / registerError* / onboardingCreateAccount / onboardingSkip(en + de). DE uses "Registrieren" on buttons because "Konto erstellen" overflows.Why
Painting mode shipped on mobile (#55), so the "force login in onboarding" band-aid from #56 is no longer needed. At the same time the app was missing a register UI entirely — new users had to go to the web. This adds the missing piece, puts register as the primary action without forcing it, and makes the entry points consistent across onboarding, home, and settings.
Test plan
flutter analyzecleanjust test-mobile— 172 tests pass, including new onboarding tests for all three paths (skip, login success, register success)