lostintangent

That kind of "power user" experience would totally be possible using CodePush. Thanks for mentioning it, since we should have a sample to illustrate how it would look!

We added CodePush support for React Native because we think it's an extremely compelling platform and so do many of our customers. I actually respect Facebook's pragmatic approach to software development prioritization, and they work so closely with the community to allow other objectives/goals to be achieved (e.g. Windows support) That seems like a great way to run an OSS project to me.

I work on the CodePush team and we are simply interested in helping devs engage more closely with their end-users, by delivering value more quickly and hopefully less obtrusively. We by no means want to prescribe poor and/or annoying update practices.

As was mentioned, our existing API surface actually leans towards the use of "active updates" that present the option to install or ignore to the end-user. That said, I think there are numerous scenarios where silent installs could be valuable as well, and you could even imagine an app having a user option to disable that or not.

We want to provide the primitives and services necessary to create these experiences, without imposing any specific opinion to how devs should cater to their respective userbase. Compelling user experiences are absolutely priority one!

That's a great point gexla. I wasn't taking into account contractors in the article (naively so). I'll add an annotation to the article that mentions how contract work is slightly different.