4 ms·

The value provided isn't necessarily silent updates, but making updates available without jumping through the app store. It's still up to the app developer whet

The value provided isn't necessarily silent updates, but making updates available without jumping through the app store. It's still up to the app developer whether they prompt the user before installing the update. In fact, the Cordova plugin provides a single function that shows a "apply or ignore" popup when an update is available, so the user can choose: https://github.com/Microsoft/cordova-plugin-code-push#codepushsync https://github.com/Microsoft/cordova-plugin-code-push#codepu... That's not to say app developers can't silently update, but using CodePush doesn't lock your app into that workflow. (full disclosure: I'm doing other things now, but I worked on this project for a few months)

drdaeman 11y ago
Oh. Then it's fair - if developers actually conform to the suggestion, of course. Sorry, I guess I've got a wrong idea what it does.
- lostintangent 11y ago
  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!