3 ms·
"With Marshmallow Android is moving towards a runtime-permission-prompt model similar to Chrome" This is horrible from a usability perspective. Note that large
by chetanahuja 11y ago
"With Marshmallow Android is moving towards a runtime-permission-prompt model similar to Chrome"
This is horrible from a usability perspective. Note that large bulk laptop purchasers (schools, large enterprises with mostly web application requirements etc.) have been the biggest markets for chromebook. One of the biggest reasons for that popularity is the lower cost of management of chromebooks compared to windows or mac laptops. In that the base OS not only just works, it also just updates. A huge saving in admin time and headache. The other factor is that all user data is automatically in the cloud, which means backups/restores/replacements/upgrades are trivial operations now.
One way chromebooks can retain this ease of use/administration is by basically shipping a laptop with chrome running on Android OS but no other apps installable by the user (outside of chrome sandbox). This will get Google out of the two OS kernels management business but could still retain the essential goodness of the chromebook concept.
- lnanek2 11y ago> Android OS but no other apps installable by the user There are quite a few device management solutions out there for Android that can white list, black list, deny all installs of apps. It's very common to setup in business and already completely supported. It's even far more powerful than that with capabilities to do things like deny certain apps/networks unless you have certain password complexity requirements, etc..