Live data from Hacker News

Onboarding teardowns

useronboard.com

31–40 of 61 posts

Re: Onboarding teardowns

#32

Hi all! I'm the person behind this site -- if any of you have any questions or withering critiques, send 'em here! I will be watching it all day.

Fabulous work! Love your attention to detail. Kudos for not polluting my history with each slide. Here: have an Internet!

Re: Onboarding teardowns

#34

Hi all! I'm the person behind this site -- if any of you have any questions or withering critiques, send 'em here! I will be watching it all day.

I think this http://i.imgur.com/bgAJfwI.png is not something us iOS developers have any control over. It is a message that automatically will pop up upon starting the app, as opposed to the location message when we are asking for the location. (This one is saying the app might use it in the background).

Re: Onboarding teardowns

#35

Hi all! I'm the person behind this site -- if any of you have any questions or withering critiques, send 'em here! I will be watching it all day.

I think this http://i.imgur.com/bgAJfwI.png is not something us iOS developers have any control over. It is a message that automatically will pop up upon starting the app, as opposed to the location message when we are asking for the location. (This one is saying the app might use it in the background).

I think the best practice there is to "prime" the user before they see the iOS permission prompts. Something like "your phone will now ask for permission to access your location. We need this to do x,y,z.."

Re: Onboarding teardowns

#36

Earlier quoted context omitted.

I think this http://i.imgur.com/bgAJfwI.png is not something us iOS developers have any control over. It is a message that automatically will pop up upon starting the app, as opposed to the location message when we are asking for the location. (This one is saying the app might use it in the background).

I think the best practice there is to "prime" the user before they see the iOS permission prompts. Something like "your phone will now ask for permission to access your location. We need this to do x,y,z.."

Sure, but my point is that for this very specific one (app may use location in the background) we are unable to do the priming as this one will be displayed by the app automatically (as opposed to most/all other such popups).

Re: Onboarding teardowns

#37
Love this site. It's amazing how many steps users have to go through to start using even simple apps. (It actually made me feel better about my app-- not that the on boarding is perfect, just nice to realize that I'm not alone.)

Sam-- any thoughts on how many screens someone should have to go through, or tips for reducing that number?

Or, if perhaps sometimes it's better to do something in multiple screens that many of us developer types would group onto one screen (Slack comes to mind here)?

Thanks for your contributions to making software easier to use.

Re: Onboarding teardowns

#38

Hi all! I'm the person behind this site -- if any of you have any questions or withering critiques, send 'em here! I will be watching it all day.

I think this http://i.imgur.com/bgAJfwI.png is not something us iOS developers have any control over. It is a message that automatically will pop up upon starting the app, as opposed to the location message when we are asking for the location. (This one is saying the app might use it in the background).

I don't think this is the case. On iOS 8.0+ there's a method on `CLLocationManager` called `requestAlwaysPermission` that causes this popup to appear. I'm not positive about older iOS versions, but I thought they asked for permission when you started using `CLLocationManager`.

https://developer.apple.com/library/ios/documentation/CoreLo...

Re: Onboarding teardowns

#39

Earlier quoted context omitted.

I think this http://i.imgur.com/bgAJfwI.png is not something us iOS developers have any control over. It is a message that automatically will pop up upon starting the app, as opposed to the location message when we are asking for the location. (This one is saying the app might use it in the background).

I think the best practice there is to "prime" the user before they see the iOS permission prompts. Something like "your phone will now ask for permission to access your location. We need this to do x,y,z.."

That's just an extra step sadly. But yeah
Post reply on HN