[krschultz]

1) Do this analysis for your own user base, universal stats may not be relevant.

2) It's more helpful to look at aggregations on cuts that will impact your product and codebase. e.g. % of devices above API level 19, % of users with each screen size grouping, what % of our users are on tablets, etc. These answer questions when you should drop support for an API, when you should start using new features, how many different UI mocks you need. Those are the relevant questions.

3) Do test your UX across a couple different phones categories. Samsung & vanilla Android have different button placements and icons.

4) There are plenty of libraries and tools available to handle this problem. I won't say it's not something to think about, but it's usually pretty low on my list.