News for hackers. Stuff that matters.
Re:React Native for OS X by mattlutze on Wednesday March 30, 2016 @06:21AM (#11388231)
The update message I've not generally seen before, but nearly every app I've used asks for at least the first two individually. The modals to allow notifications, location access, and other granular permissions on iOS is a good-practice pattern.
Re:React Native for OS X by dean_mcpherson on Wednesday March 30, 2016 @05:51PM (#11393326)
Agreed, we probably need to work on offsetting those prompts til after onboarding, and preparing the user. An implementation issue though, not a react native one.

The two permissions modals are required by iOS to access those features, and RN definitely has the ability to defer when those are shown.

The update prompt is actually from http://microsoft.github.io/code-push/ which allows us to push minor updates directly to the app without going via the app store. Say goodbye to 2 week time cycles. A newer release of Code Push actually doesn't prompt the user at all, and can download an update during use and load it when the app goes inactive.

Re:React Native for OS X by Cthulhu_ on Wednesday March 30, 2016 @07:00AM (#11388362)
Good onboarding will however prepare the user for the appearance of those dialogs, or ideally only present them when the user performs an action that requires access to e.g. location services or push messages.
Re:React Native for OS X by mattlutze on Thursday March 31, 2016 @04:44AM (#11395814)
Agreed entirely, if it's just blasting them out on first-use then they could definitely tighten that up.