Skip to content
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

Store FTUE use case in an account setting #6639

Open
germain-gg opened this issue Jul 26, 2022 · 1 comment
Open

Store FTUE use case in an account setting #6639

germain-gg opened this issue Jul 26, 2022 · 1 comment
Labels
A-Registration good first issue Good for newcomers T-Task Refactoring, enabling or disabling functionality, other engineering tasks Team: Delight Z-FTUE Issue is relevant to the first time use project or experience

Comments

@germain-gg
Copy link
Contributor

germain-gg commented Jul 26, 2022

Your use case

What would you like to do?

Migrate the FTUE use case value from the local device to an account setting with the key FTUE.useCaseSelection

Why would you like to do it?

Web is now tracking that data in the account setting. See the implementation matrix-org/matrix-react-sdk#8984

How would you like to achieve it?

Android is asking the use case question to user and storing that information on device. I would like to change the logic to that in the future all answers to this question are set in the account setting FTUE.useCaseSelection.

If the account that the user is logging into has already a value set, the FTUE use case selection screen should be skipped entirely.

Finally we should add a snippet of code that migrates the existing "on device use case selection" to the account setting.

Have you considered any alternatives?

No response

Additional context

No response

Are you willing to provide a PR?

No

@germain-gg germain-gg added Z-FTUE Issue is relevant to the first time use project or experience T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements A-Registration Team: Delight labels Jul 26, 2022
@daniellekirkwood
Copy link
Contributor

is this an enhancement or a task? I'm struggling to assign O- and S- labels

@germain-gg germain-gg added T-Task Refactoring, enabling or disabling functionality, other engineering tasks good first issue Good for newcomers and removed T-Enhancement New features, changes in functionality, performance boosts, user-facing improvements labels Sep 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Registration good first issue Good for newcomers T-Task Refactoring, enabling or disabling functionality, other engineering tasks Team: Delight Z-FTUE Issue is relevant to the first time use project or experience
Projects
None yet
Development

No branches or pull requests

2 participants