For example on my smartphone (a Wiko Cink Slim), I uninstalled the Twitter and Facebook apps because mobile.twitter.com and m.facebook.com are much quicker and responsive than the Android applications. They also do not request as many permissions, and are more featureful (e.g., Facebook chat works on m.facebook.com while it isn't included in Facebook's app, and rather requires an additional very intrusive shitty app).
On Android.
[1] https://developer.android.com/about/dashboards/index.html
What? People don't upgrade to an older phone. That number has nowhere to go but highter.
The upgrade cycle being a mess just make this take more time.
No, but new phones come out all the time that are STILL using older Android versions. I think it will take around 2-3 years for all new Android phones to come with the latest Android.
Content distribution and companion apps made sense when you needed to go mobile 5 years ago, when redoing your entire site to support mobile was too expensive and even then it wouldn't be a good experience due to how poor mobile browsers performed back then. Now it makes absolutely no sense, it's another thing you need to support and worry about which costs money, it's much harder to make people download an app than press a link, and in the current "link-content-sharing" (e.g. outbrain) eco systems most sites operate in it makes very little sense since allot of the traffic is generated by those click-baity "25 reasons why Node is now considered harmful" links you have at the bottom of each TechCrunch article. And on top of that even a low-end phone will usually have a 1080p(or close enough) screen, 2GB of RAM (unless it's an Iphone ;)) and a quad/hex core CPU which is more than capable of running pretty much any browser served content today mobile or not.
But, the reason people are using browsers more than apps is simply because search is becoming the main use case of a smartphone.
I never look for an app on my phone beyond my home screen anymore, I just search or voice search my phone and expect it to either direct me to an app on my phone, or a search results page in Google.
I dont care where the solution to my need lives, I just want the quickest, easiest access to that solution.
I don’t think that explains the difference at all. I think it’s about convenience. People don’t want to use apps for the diverse things they do on the web all the time. Apps may be convenient if you use them frequently (and then only marginally, especially with improving speeds and more people paying attention to making websites usable on phones), but if you use something not so often?
it's 2015 man, we took the word back. nerdy is cool.
I don't even know anymore what apps I have on my phone.
I simply search and let Google search my phone and the internet at the same time and I click on the most convenient result.
it is definitely a difference, but to act like this is the reason for these numbers is so misguided.
"I use mobile web because apps have too much control" - no normal person ever
the only competitive advantage for apps is push notifications, and the sooner browsers and phones can build that into a standard the better (including opening the right page when clicking on a specific service notification)
Don't know about that. What about UX? It's pretty well accepted now that the native controls in apps provide a much less frustrating UX than all but the most meticulously designed web apps, which is a very low percentage right at the top. That's just talking about controls, that's not even to mention the clunkiness of the browser itself (address bar popping up over content, popups offering to remember passwords, all that kind of stuff that detracts from your tailored experience) and to an extent the navigation model (typing in a url rather than tapping an icon for instantaneous checking of a service). Simple stuff like this really matters to the majority of people.
For technically-minded people, we're not as distracted or put off by this 'minor' stuff because we understand the trade offs, reasons for it, depth of it and even how to work around it. Most people don't, they just (probably rightly based on evidence) trust apps to deliver a better and more tailored UX and that's it, that's what they like and want more of.
Don't get me wrong, I love the web, for probably much the same reasons you do. One advantage it definitely has is the ability to avoid downloading apps in the first place. But its competitive disadvantages vs native apps go way beyond push notifications. There's are a lot of things so deeply baked in to the web and browsers that apps do so much better that it will take (software) generations to 'fix', if at all.
Unfortunately for the web, as seen in the last five years or so, these are disadvantages that really, really matter to the majority of people who actually use services. Much more so than the higher level, arguably 'more important' things like security, privacy, storage space, etc that us techies tend to prioritise.
we're not that far from a good user experience. even the bar problem is only ios specific, android browsers have a better support for full screen apps
Looking at the ridiculous number of permissions different apps would require to run on my (Android) phone, using mobile site of the most of the services seems safer choice. Android 6.0 may change this with switchable permissions, tho.
I agree that the current browsers represent an exceptionally good model to run remote applications securely, far better than the app store / play store 'sandbox' and 'vetting processes' model, since has been used since forever and tested again loads of different attack vectors.
but I don't know if this is the reason for non nerds not to use native apps
And on iOS, even speakers and high bandwidth content are loaded only on a per user request basis.
It corresponds to kCLAuthorizationStatusAuthorizedWhenInUse authorization status in the SDK.
If an app tries to use any of the background location API without the user having previously authorized kCLAuthorizationStatusAuthorizedAlways (and I believe the user is prompted again in a few days after the initial authorization by iOS8+) the app API calls are denied access with an error code representing unauthorized.
It has been my experience that adding the "Location updates" background mode capability indicating to Apple that your app requires background location sets off closer review during the app store acceptance process.
I have had apps rejected that a reviewer felt did not have a good enough text "reason" for requiring location tracking displayed to the user in the message box.
There are many reasons for a Yelp-type app legitimately to know about your location while not in use. It could make better recommendations, limit searches to "local" sites, etc.
None of this of course stops iOS itself from "spying" on you. The CLVisit seems to be always recording but experts with more knowledge on that topic than me might know how to turn it off.
The Play Store and installing APK's shows you a full list of permissions that the app will have access to before installing. If you're not happy with it, just don't install the app.
That's a shitty way to do things. You should be able to revoke access to things the app is asking and still use the (then crippled) app. There are tons of apps who ask way more access rights than they need (obviously not related to their core functions).
It's going to be extraordinarily confusing for users who end up exposing their personal data, thinking that an old-API app will be constrained when running on their new 6.0 OS.
By stock ROM, you mean you have a nexus device and the original or OTA upgraded firmware on it?
PS: This is the device http://www.gsmarena.com/vodafone_smart_ultra_6-7313.php
A website has write access to my screen, my speakers and my internet connection. Plus limited read access. To keyboard, mouse, device orientation etc. Other rights can be granted (location, cookies etc). It can do all this only as long as it's "open".
An app usually has read/write access to large parts of my device. The whole sd-card, raw internet access, the camera, the microphone, ask me for money etc. And it can keep doing so even when it's "closed".
We will see the two converge. Websites will have more rights they can ask for. Apps will be better to tame.
But trust will keep being the differentiator and they will keep co-existing. There is friendship and there is marriage. Both have their use case.