Last modified: 2014-02-12 23:40:00 UTC
The platform choices don't reflect the state of the industry or the platforms we prioritize. The choices on the left are: All Macintosh PC Smartphone Tablet PC Other The OS list is long, but does not include *any* mobile OSes. Ideally, the hardware list would include specific devices, such as: Galaxy GS3 iPhone 4S Galaxy Note iPad 2 etc rather than generic things like "smartphone" and "tablet PC". Hardware specific bugs on mobile do exist (due to screen size among other things) Perhaps the most commonly used devices on Wikimedia sites could be included. At the least, though, the common mobile OS versions (including specific versions of iOS, Android, and Windows Phone 8) should be on the right. The mobile team may be able to help out with some basic user agent information so we know which are worth including here.
I just saw there's a mobile platform dropdown. I don't know why that's separate. The hardware issue at least needs to be addressed.
Is there any point to having hardware at all? Is anyone using it? If so I'd encourage killing it...
(Platform rather)
Well, desktop OS is only in the right column of Platform, so that's worth keeping. I would suggest we just put all the OSes there and get rid of (migrating the existing data) Mobile Platform. As far as hardware (left column of platform), it's not as commonly an issue. But there are definitely sometimes hardware-specific issues. My understanding is that is much more common on mobile, but I think it happens on desktop occasionally too.
=== Hardware dropdown === (In reply to comment #2) Is there any point to having hardware at all? I'd encourage killing it Waiting for next year's Bugzilla 5 to disable it: https://bugzilla.mozilla.org/show_bug.cgi?id=763409 === OS dropdown === (In reply to comment #4) > I would suggest we just put all the OSes there and get rid of (migrating the > existing data) Mobile Platform. Please convince the Mobile team to agree (combined with a nice proposal which items to merge or remove) and I will gladly do so - this is/was handled in bug 40936.
