-
Notifications
You must be signed in to change notification settings - Fork 984
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Onboarding - New opt-in usage data screen #21655
base: develop
Are you sure you want to change the base?
Conversation
Jenkins BuildsClick to see older builds (28)
|
f8ccd62
to
3c49d9a
Compare
3c49d9a
to
d62975f
Compare
parent (or (first @state/modals) @state/root-id)] | ||
(navigation/push | ||
(name @state/root-id) | ||
(name parent) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Onboarding navigation is very confusing because:
- We use the same screens across different flows (e.g., create an account, sign in, profiles → create an account).
- Since we use the base screen as a modal for transparency, and then push screens using
navigate-to-within-stack
, we have to track where we are coming from. Additionally, because we also usenavigate-to-within-stack
in events, we end up polluting the app-db with flow-related data to keep track of this.
Solution: In onboarding, we push stacks inside the base modal. Wallet likely does something similar, with different logic for where to pop up (though I'm not sure — I need to check).
- We continue using
navigate-to
also for these flows, as we do in other areas. Navigation will push into the modal if it exists; otherwise, it will push into the base stack. - Do not change
navigate-to
; instead, create a new event,navigate-within-base-modal
.
In both cases, we will eliminate confusion and reduce noisy code, as seen in 336f1cb. (still WIP)
What do you think? Which solution sounds better, or do you have any suggestions?
@@ -43,4 +43,4 @@ | |||
:stickers/packs-pending #{} | |||
:settings/change-password {} | |||
:keycard {} | |||
:theme :light}) | |||
:theme :dark}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
App opens in on-boarding/profiles, where default theme is :dark
d62975f
to
7f754a1
Compare
@@ -277,7 +276,6 @@ | |||
|
|||
(defn view | |||
[] | |||
(rn/use-mount #(rf/dispatch [:centralized-metrics/check-modal metrics-modal/view])) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For existing users who have not confirmed their choice, we will likely show the usage data screen after login. (Needs to discuss, cc @ilmotta)
(defn- share-usage-data-fn | ||
[enabled? next-screen] | ||
(rf/dispatch [:centralized-metrics/toggle-centralized-metrics enabled? true]) | ||
(rf/dispatch [:navigate-to next-screen])) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Used navigate-to
instead of navigate-to-within-stack
- https://github.com/status-im/status-mobile/pull/21655/files#r1856286497
0% of end-end tests have passed
Failed tests (7)Click to expandClass TestCommunityOneDeviceMerged:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
Class TestWalletMultipleDevice:
Class TestWalletOneDevice:
Expected to fail tests (1)Click to expandClass TestCommunityMultipleDeviceMerged:
|
fixes #21563
Testing Note
status: ready for review (please postpone testing the PR until approved)