omi icon indicating copy to clipboard operation
omi copied to clipboard

Onboarding screen about how important it is to enable notifications

Open kodjima33 opened this issue 1 year ago • 1 comments

Is your feature request related to a problem? Please describe. I assume that 70%+ of people don't enable the notifications but they are crucial part of the product.

Describe the solution you'd like Explainer screen that doesn't let people use the app without enabling notifications, explaining how important it is

kodjima33 avatar Jul 01 '24 07:07 kodjima33

I quickly created an onboarding screen in Figma to match the current designs. Does this work, or do we need different illustrations?

notif.png

mdmohsin7 avatar Jul 08 '24 18:07 mdmohsin7

Update

  • [x] This task should include speech profile in onboarding, connection and ws shared by same

  • [x] Should find a better way to ask for permissions

    • [x] Bluetooth doesn't appear when you opened (very bad experience)
    • [x] Ideally connect your device is less skippable
    • [x] Notifications permission is better asked.
  • [x] Probably check bluetooth permissions, and ask the user to turn the device on or explain the lights indicators.

Aha moment should take 30 seconds for them to start seeing transcript in the screen.

Relates to https://github.com/BasedHardware/Omi/issues/606

When they open the app, they should instantly see new memory creation.

  • A sample memory.

This sample memory should explain that once the conversation finishes, they will get a memory, etc.

josancamon19 avatar Aug 24 '24 20:08 josancamon19

Onboarding Flow: Notification permission -> Bluetooth Permission -> Connect Device (Also explain light indicators through UI) -> Setup Speech Profile (skippable?) -> If speech profile skipped, speak few words (show transcript) -> Show memory (aha moment) and then home

mdmohsin7 avatar Aug 27 '24 17:08 mdmohsin7

  • [x] We should also include here a set name page here, during onboarding, to confirm the user name, so should use firebaseAuth first name, and ask them "How should we call you" it should call @router.patch('/v1/users/name', tags=['users'])
  • [x] People should be able to go to settings and change the name (specially existing users) cause some of them might have AnonymousUser value from apple hidden name.

josancamon19 avatar Aug 28 '24 04:08 josancamon19

  • [ ] We should also include here a set name page here, during onboarding, to confirm the user name, so should use firebaseAuth first name, and ask them "How should we call you" it should call @router.patch('/v1/users/name', tags=['users'])
  • [ ] People should be able to go to settings and change the name (specially existing users) cause some of them might have AnonymousUser value from apple hidden name.

An endpoint to get the user details as well? To show their details like the name, email address etc in the personal details section in the app

mdmohsin7 avatar Aug 28 '24 18:08 mdmohsin7

@mdmohsin7 name should be changed directly with firebase auth, check auth.dart, but once changed we need to call the backend, to modify the text contained in facts, to match the new user name

"Kaitlin likes chocolate" modified to "Kaitlin2 likes chocolate"

josancamon19 avatar Aug 29 '24 06:08 josancamon19