The other is that web browsing discrepancy is a huge anomaly for some reason and should not be considered a proxy for other "smart" features. I'd love to hear suggestions.
I can think of many, many reasons for that discrepancy. See, browsing the web isn't that much fun on such small displays. People prefer to get the information they want in an easy way. There are multitudes of ways to get information from the web without using any browser at all.
Once you don't use a browser to access the web, it becomes rather tricky to near impossible to get valid statistics about what device/OS accesses that information. In the case of smartphones, apps are the little things that add methods of accessing the web without a browser. If you have an ecosystem that makes it cheap and easy to develop and distribute apps, you will naturally have more apps available to access the specific things you are interested in. It is rather awkward to use a smartphones web browser to surf to a weather forecast site to get a forceast for where you are. Using an app makes that much easier and comfortable. But it also potentially hides the method of access, since there is no browser signature.
And that's just one of the many things i can think of. And apps play an important role when you compare iOS to Android, see below.
This is why "access by browser by OS" isn't a suitable measure when it comes to mobile, extensible (by apps) devices.
To be clear: by developers I meant publishers, not developer salaries. As for your final sentence, most iPhone customers are not otherwise Apple customers, so they aren't "used to" anything even if your "excess" claim were true.
So, publishers are now developers. I guess that red is blue as well. And about paying premiums to be involved in the iOS ecosystem. Well. To develop an app there you need a Mac. You also need the actual dev-environment, that not only runs on the Mac, but also requires the latest OS-X. It's not enough to have just some old OS-X Macintosh somewhere. If you want to be in the game, you have to pay for the latest OS.
Then, once you got around to write an app, you have to play the Apple-lottery: Will they allow your app in the appstore or not? And even if you managed that, a not-so-small chunk of what the users pay for the app goes to Apple. So, to make up for all that you have to increase the price, which makes it more expensive for the user.
In case you ever have the idea to develop some hardware to connect to an iOS device, you have to wade through a lots of red tape and paperwork, and then pay many thousands of dollars to Apple just so you get into the MFI program. These are upfront costs before you even thought about your actual device. And guess who has to pay that in the end? Not to mention that this is blocking a lot of small businesses from developing hardware for iOS devices, since they simply can't afford that.
Oh, and even if you manage to get into the MFI program, it's far from certain that you can really provide apps through the Apple appstore to use that hardware. See the Redpark serial cable for example.
Compare that to the Android ecosystem. You simply download a virtual machine image, for free (well, except the cost for the internet traffic). You start the virtual machine and are ready to go. Everything is there, ready to use. You write your code and publish the app, that's all. If you sell it, only very little of that money goes to anyone else.
Plus, you write apps in Java, as far as the language is concerned, which means that a huge developer base has almost instant access to the ecosystem.
And _that_ is the biggest reason why Android is so popular. More choice, more relaxed environment to get your stuff marketed. Users have way more freedom and choice, which is what they like. Vendor lock-in never worked that well in the end.
Greetings,
Chris