People complained about the web too, we just don't make a lot of noise about it now because we've given up on many aspects of it. For a long time websites were

People complained about the web too, we just don't make a lot of noise about it now because we've given up on many aspects of it. For a long time websites were designed to fit a lowest-common-denominator screen size - 800x600 or 1024x768 - and anything larger just had padding or other void space added. Hell, most websites are still like this. See: NYTimes, IGN, etc. Fragmentation exists on the web and it causes many of the same issues as it does for native-mobile, it just isn't new, and it isn't very controversial given that we've thrown up our collective hands and quit trying to take advantage of everyone's browser windows and just resign ourselves to wasting pixels instead. Screen size fragmentation is still a big deal on Android because we haven't resigned ourselves to throwing black bars up on screen and we're still doing our damndest to make good use of each individual screen size. On the other hand, browser API fragmentation is a huge deal, and people do complain about it incessantly, for good reason, and it shares fundamentally many similarities with Android API fragmentation. Want to build your new thing with Canvas or WebGL? What's the penetration like, how many users even have browsers/machines that can handle it? New CSS tag? Sorry, not supported in many still-shipping browsers. Pretty much the whole "IE sucks" meme comes down to API and implementation fragmentation. Complex apps on the modern web involve miles upon miles of compatibility hacks to work out the implementation differences for the same API, as well as different API support levels entirely. This is a big deal, and a huge time sink, and people rightfully do complain about it. tl;dr: Fragmentation on the web is a problem and people do complain about it. The only thing that isn't complained about is screen size, mostly because we've taken a huge cop-out to avoid it.