"Both of these could be solved with caching, though."
Sounds like it is up to you if the app you deploy to the app store will have this ability or not or on which side of the spectrum you want to be.
When you look at the Facebook app (or other popular apps) they've found ways to 'update' parts of the application (or behave differently eg for a/b testing of new functionality) without the user having to download a new version.
Do you use any web apps? Those are updated and re-downloaded regularly, depending on how the app is built.
If you use an Android or iOS-based device, the software on it often becomes out-of-date and requires an upgrade in order to restore and improve functionality.
The app writers should have such control. The 'poor shmucks' have as much power as always in this ecosystem, because they can choose what apps they want to trust and use.
Web browsers have the ability to use your location information, microphone, camera, and local storage. Plus the web browser is almost always running.
You may not realize it, but you already trust your web browser to protect you and safely dole out permissions. Why would a next-gen application environment be any different?
You don't permit browser access to all that when you visit a internet page. You do on Android if you want to install an app.
...the majority of the app is served over HTTP, allowing for continuous deployment where everyone always runs the newest version. URLs are a base layer of DART, so everything is internet aware. The downside to this is that the demo app doesn't work when you're offline, and starting the app takes a second or two because it needs to download data.
So this is effectively a permanent 'wget |sh' kind of system? Sign me up!