As for myself, I decided from the start not to develop "apps" for iOS or Android and instead keep building "web apps" instead. My apps are all business tools so I really don't need any special access or permissions to make them usable.
I will say LocalStorage sucks and I wasted too much time trying to make it not suck. In the end I gave up so Apple's and others decisions to stomp on it won't really affect me or my apps' users.
But Local-First assets and data management are something that developers will have to demand and there seems to be little thrust for that right now. Still, the shine is most certainly wearing off the hype developers were attracted by for these platforms so we might start seeing some movement that direction soon now.
I've been working on a local-first, offline-first, web app for desktop PCs that uses CouchDB installed on the user's PC instead of a CouchDB in the Cloud. Used this way with a web app CouchDB is somewhat akin to a sandboxed runtime engine for web apps on the client side. And the increase in performance of the app is quite noticeable. I think it's fair to say it runs at near native speed.
Configured with service workers to run offline first the web app only checks the server to see if any updates have been issued and if not it never sends any data over the internet.
It's very easy to provide the user an option to sync their local CouchDB with one in the Cloud, and they can turn that option on and off. When it's on they can access their data with any device and "Live Sync" the data between the Cloud CouchDB and their Desktop CouchDB.
Now, it's beyond my skills to develop it but it seems to me that a sandboxed runtime engine for web apps on mobile devices would be a good thing for us all. Of course, I don't think Apple and Google think so, but they do most definitely depend on indie developers to entice people to use their devices.