To that end, in recent months, I've found myself deleting about half of the mobile apps I'd downloaded over the years, and shifting to using the firm's browser interface whenever possible.
If it's so "garbage" then maybe don't install that app or visit that site?
But people want the content, but not what pays for it (and also don't want to directly pay for it -- not in any sustainable numbers).
It really sucks for the honest developers, but as a result, I'm more comfortable using my browser to interact with dynamic content (like HN, Reddit, etc) while reserving local app installs to an extremely limited set of functions which need to operate on my local data where having both contact and networking permissions are a huge red flag.
This is all due to the interface though. Mozilla is a much more neutral party then Google. I'd rather untrusted third parties negotiate with Mozilla's API than Google's. What I'd like even more is good native software which treats users with dignity and respect, but those are few and far between on Android.
Sorry, but what "race to the bottom"? There are 1.5 millions apps in the iOS App Store. Inevitably a lot of them will be bad. But there are thousands of great apps at any price range.
It is not up to you to decide what is legitimate.
The iOS App Store isn't perfect in this regard, but it's miles ahead of Google Play, which doesn't seem to have any standards at all.
But yes, Google still gets everything .
Use webapps, a browser to sandbox better websites.
Phone is marvelous now.
Apart from performance-intensive apps/services like Netflix or Twitch, even things like Linkedin I find more engaging on a tablet/phone.
The app feels more responsive, the design does not have the same constraints as when designing for a browser.
But I really don't see the need of seeing it as a dichotomy, as a "there will be only one" thing.
The convenience/ubiquity/versatility of a browser is hard to match.
Just like the browser didn't kill desktop applications, native apps won't kill the browser.
I have an app that pays for parking in my city. It's pretty decent and I'm happy with it. If I go to another city once in a while, I'm likely not going to download a different app to pay for parking there. Or if I visit a furniture store for something once, I really don't want their app. And so on.
Maybe there needs to be a more curated App Store that carries only the best applications?
Battery sipping native C apps? Mobile browser-based SPAs are worse battery sipping offenders than native apps.
At least the native C apps don't run 2-3 extra levels of indirection AND the most inefficient GUI stack to top.
WebAssembly might indeed solve this...
This mirrors my experience. I derive all the value I'm looking for from my personal and work mobile devices (yes I like to keep them separate) with less than five apps beyond the vendor+carrier distribution on each.
This is particularly true for my work device, which is a BlackBerry Z30. There aren't many apps available for this environment so the browser is the primary point of mobile interaction.
Your point regarding browsers becoming a modern Emacs is a concern and a good expression of the issue. I'm not sure what to do about this - I can only pick and choose a browser where options are available and look to configure it to my advantage. Any suggestions?
Amusingly enough, you just described how apps worked on my first mobile device - a Windows CE PDA. There weren't a lot of free programs available, but the ones I could find were very well-designed.
Perhaps check out the new permission model, which requests permissions at runtime, instead of upfront.
And about ads, more and more iOS apps are starting it too, i thought ( don't have iOS, read it from multiple sources)
Perhaps I'm just spoiled by the excellent quality software I get for free on my Gentoo/Debian workstation. I just refuse to accept that because my phone fits in my pocket, the standards should be so much lower. I miss my n900 dammit. :/
This is getting worse and worse though as browsers expose more and more of their host operating system's functionality. The benefits of using a website instead of a native app are quickly disappearing, while the drawbacks have only been somewhat mitigated. We're getting to the point where browsers are worthy of the decades old criticism Emacs has received. They have eventually become an OS with many fine features - simply lacking a good web browser. For the privacy conscious user, modern web technologies will undermine you every step of the way, or simply break if you choose to stand your ground.
I personally would rather have a dozen well crafted battery sipping native C apps than a million awful contraptions built in a script interpreter on to of a VM by the lowest bidder on ODesk. Sure it's harder to do it right, but that's the cost of quality. Maybe I'm stuck in the 80's, but to me, it seems like a lot of wisdom has been shrugged off in the pursuit of expedience.