At least in the US, a lot of designers have an iPhone (and so do their friends). I think it's also likely that the iPhone was the first mobile device they have ever used the internet on. It's easy to fall into the trap of thinking that since me and all my friends only use the iPhone everyone else does to.
I don't agree. The iPhone was at least my 4th or 5th device that had some kind of "mobile web" function. Most folks had smartphones, blackberries, etc before they got an iphone if they had any interest in the net. The problem was, the reality of tying to actually _use_ these devices to access web sites was such a horrible UX that you didn't do it unless there was absolutely no other option. In comparison, lots of us…
The iPhone obsession
61–70 of 82 posts
Re: The iPhone obsession
#62"First, so what? No, let me rephrase that: So fucking what? Since when does web development mean leaving 50% of your mobile users out in the cold? Since when is “I only support browsers with a large market share” a valid argument? (Answer: since we have an iPhone up our ass.)" A device has more than 3x its market-share in traffic-share and we are supposed to ignore that? That doesn't seem realistic. This gap between…
* Those usage numbers (50% of mobile browser traffic)
could be a US-only statistic
* People on other browsers might not browse the web as much because
not enough effort is made to making web content usable on those
browsers.
Viewing your argument alongside the second point poses a possible chicken-and-the-egg problem. No one is using other mobile browsers because the experience sucks, but the experience sucks because not enough development is done to make it bearable (or pleasant). Not enough development time is being spent to make the experience bearable or pleasant because no one is using those other mobile browsers.Re: The iPhone obsession
#63It's not about the iPhone, it's about Webkit. He seems to forget the fact that hardware sales doesn't translate into actual internet usage. The internet outside of iPhone, Android, and Palm is so terrible that barely anyone even bothers to use it. What do those three platforms have in common? Webkit!
Nokia's browser is also based on WebKit.
Re: The iPhone obsession
#64Earlier quoted context omitted.
None. Having worked on mobile web applications that serve a wide range of devices, I can honestly say that this is not the case. I would challange ppk to cite examples of this behaviour.
Actually, you can change your user agent with Opera Mobile if I'm not mistaken.
Re: The iPhone obsession
#65First time I heard Quirksmode curse like a sailor. Regardless, the reason I can't develop for a Nokia, Blackberry, or HTC is because I don't have a Nokia, Blackberry, or HTC. I have an iPhone. It's pretty easy to develop webapps for it because if it looks good in desktop Safari, it will probably look good in iPhone Safari. I don't even know the browsers that other phones have. I know Opera Mini is on many phones and…
Re: The iPhone obsession
#66Earlier quoted context omitted.
Well, given that Nokia S60v3 browser _is_ webkit, I don't think that the results with your suggested stylesheet would be satisfactory. Would you accept it on your iphone?
If the phone is worth targetting, then target it. I'm just saying that arguing Nokia's total phone market share seems like a sort of sketchy way to extrapolate priorities for smartphone-enabled websites. Does the Nokia S60v3 have large market share worth targeting? The reason Android and iPhone markets have such gravity is that they're large and relatively homogenous consumers of rich web content from the mobile spac…
Re: The iPhone obsession
#67Earlier quoted context omitted.
If the phone is worth targetting, then target it. I'm just saying that arguing Nokia's total phone market share seems like a sort of sketchy way to extrapolate priorities for smartphone-enabled websites. Does the Nokia S60v3 have large market share worth targeting? The reason Android and iPhone markets have such gravity is that they're large and relatively homogenous consumers of rich web content from the mobile spac…
Sorry, you're the one who's confused -- the article is quite explicit that the marketshare numbers given are for smartphones, not the entire phone market.
There are smartphones and then there are post-2006-smartphones, which actually do real web browsing. I strongly suspect that Nokias numbers here include many phones less capable than the one that was raised in objection previously. Is there independent evidence to the contrary?
Re: The iPhone obsession
#68"First, so what? No, let me rephrase that: So fucking what? Since when does web development mean leaving 50% of your mobile users out in the cold? Since when is “I only support browsers with a large market share” a valid argument? (Answer: since we have an iPhone up our ass.)" A device has more than 3x its market-share in traffic-share and we are supposed to ignore that? That doesn't seem realistic. This gap between…
Re: The iPhone obsession
#69It's not about the iPhone, it's about Webkit. He seems to forget the fact that hardware sales doesn't translate into actual internet usage. The internet outside of iPhone, Android, and Palm is so terrible that barely anyone even bothers to use it. What do those three platforms have in common? Webkit!
Emerging economies such as India have huge mobile Internet populations. In fact in India mobile Internet outnumbers PC based internet 3 to 1 with a mobile Internet use north of 37million users, very few of which are using iPhones.
http://research.nokia.com/files/MobileInternetUsageInIndia.p...
http://mobiforge.com/analysts/blog/mobile-internet-users-ind...
http://knowledge.wharton.upenn.edu/india/article.cfm?article...
Re: The iPhone obsession
#70Earlier quoted context omitted.
I think this article is aimed directly at you then. And clearly you disagree, sounds like because you don't feel like it. A lot of us don't really want Apple (or Google, or x, or y, or z) to be a monopoly though. And perhaps the people who do follow the advice to consider the other browsers and will help keep things on an even keel.
I disagree not because I don't feel like it but rather because I'm not certain it is the best use of my resources to develop, test, and debug my app in every browser out there. I just don't have the time/money/resources to do it. And I highly doubt most startups do either. So you target the top 5-10 and stick to it till someone complains.
But in the end, the loser is you, the web developer, because you're pushing potential visitors away from your site.