J Lam kangaroo5383

## keybase.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                kangaroo5383
                / keybase.md
            
            
              Created
              November 21, 2019 04:41
            
              
                keybase.io
              
          
    Keybase proof

I hereby claim:

I am kangaroo5383 on github.
I am kangaroo5383 (https://keybase.io/kangaroo5383) on keybase.
I have a public key whose fingerprint is 1AFB 9DCB EABA 73CA 6EAF  57BE F567 0C85 5948 302C

To claim this, I am signing this object:

  
## gist:c5587e37a777fed105a5
I would be interested in the group's opinion on a design challenge we are having with an interactive onboarding experience.

Desired feature:
When a user is experiencing specific screens for the first time, the on boarding messaging would help guide them through it if they are inactive for n seconds (inferring that they may be confused). An example would be - we have a trip creation screen with multiple steps, the onboarding message would come up, then the user could dismiss it or if a user perform the suggested action, the onboarding message would go to the next suggestion or disappear until some other screen comes up. It should also be smart enough to not get in the way of user doing whatever they want in the app at the time.

Possible solutions:
A. onboarding as a custom view, whenever a controller decides it needs some hints, it would send the proper information and show and dismiss it.
- pros: dumb and simple onboarding view
- cons: I don't think it's right that view controllers have to manage onboarding
	I would be interested in the group's opinion on a design challenge we are having with an interactive onboarding experience.

	Desired feature:
	When a user is experiencing specific screens for the first time, the on boarding messaging would help guide them through it if they are inactive for n seconds (inferring that they may be confused). An example would be - we have a trip creation screen with multiple steps, the onboarding message would come up, then the user could dismiss it or if a user perform the suggested action, the onboarding message would go to the next suggestion or disappear until some other screen comes up. It should also be smart enough to not get in the way of user doing whatever they want in the app at the time.

	Possible solutions:
	A. onboarding as a custom view, whenever a controller decides it needs some hints, it would send the proper information and show and dismiss it.
	- pros: dumb and simple onboarding view
	- cons: I don't think it's right that view controllers have to manage onboarding