A list of the most popular devices in the US and the EU, which is necessary to test the mobile application (translation of article)
We are in a situation where global markets are presented thousands of different smartphones under hundreds of brands. Some of them we are familiar, and some we see for the first time. But this does not mean that the A - or B-brands are represented and popular on all markets. According to the Pareto Sakoku, only 5-7 devices/brands are take up to 80% of the market in a particular region.
Preface from the translator:
Colleagues, due to a certain amount of hype in the comments, I want to clarify a few points:
1) This is a translation of the article;
2) I deliberately left everything as is in the original (not made any edits in a few inaccuracies, wrote of the conclusions didn't leave comments), because it would not be a translation.;
3) If you think something's missing or want to improve the material, you can write a comment at the bottom (on the case), or to contact the authors of the original source (link below).
This means that when developing and testing mobile applications, you must bear in mind two main points:
the
-
the
- Devices that are popular in the regions where it is planned to launch applications. These popular devices will be in the hands of the majority of your real users. And if the build is a beta testirovanie not been tested on any of these devices, chances to put bold cross on the promotion of the application right from the start. the
- Mobile device specification (screen resolution, independent of pixel density, etc.).
We conducted research and gathered a list of the most popular devices in the United States and the European Union markets.
Nice test!
the
Apple Smartphones
| Smartphone name | Screen width px | Screen height px | CSS width, dp | CSS height, dp | SPD, ppi |
| Apple iPhone 6s | 750 | 1334 | 375 | 667 | 326 |
| Apple iPhone 6 Plus | 1080 | 1920 | 414 | 736 | 401 |
| Apple iPhone 6 | 750 | 1334 | 375 | 667 | 326 |
| iPhone 6 Plus | 1080 | 1920 | 414 | 736 | 401 |
| Apple iPhone SE | 640 | 1136 | 320 | 568 | 326 |
| Apple iPhone 5/5S/5C | 640 | 1136 | 320 | 568 | 326 |
the
LG Smartphone
| Smartphone name | Screen width, in px | Screen height, in px | CSS width, dp | CSS height, dp | SPD, ppi |
| G4 | 1440 | 2560 | 360 | 640 | 538 |
| LG G3 | 1440 | 2560 | 360 | 640 | 538 |
| LG Nexus 6P | 1440 | 2560 | 411 | 731 | 518 |
| LG Nexus 6 | 1440 | 2560 | 411 | 731 | 518 |
| LG Nexus 5X | 1080 | 1920 | 411 | 731 | 423 |
| LG Nexus 5 | 1080 | 1920 | 360 | 640 | 445 |
| LG Nexus 4 | 768 | 1280 | 384 | 640 | 320 |
the
Samsung Smartphones
| Smartphone name | Screen width, in px | Screen height, in px | CSS width, dp | CSS height, dp | SPD, ppi |
| Samsung Galaxy S6 | 1440 | 2560 | 360 | 640 | 577 |
| Samsung Galaxy S6 Edge | 1440 | 2560 | 360 | 640 | 577 |
| Samsung Galaxy S5 | 1080 | 1920 | 360 | 640 | 441 |
| Samsung Galaxy S4 | 1080 | 1920 | 360 | 640 | 441 |
| Samsung Galaxy S4 mini | 540 | 960 | 360 | 640 | 256 |
| Samsung Galaxy S3 | 720 | 1280 | 360 | 640 | 306 |
| Samsung Galaxy S3 mini | 480 | 800 | 320 | 533 | 233 |
| Smartphone name | Screen width, in px | Screen height, in px | CSS width, dp | CSS height, dp | SPD, ppi |
| Xiaomi Mi 4 | 1080 | 1920 | 360 | 640 | 441 |
| Xiaomi Mi 3 | 1080 | 1920 | 360 | 640 | 441 |
| Sony Xperia Z3 | 1080 | 1920 | 360 | 598 | 424 |
| Sony Xperia Z | 1080 | 1920 | 360 | 640 | 443 |
| HTC One M9 | 1080 | 1920 | 360 | 640 | 538 |
| HTC One M8 | 1080 | 1920 | 360 | 640 | 538 |
the source of the article Article based on information from habrahabr.ru
Популярные сообщения из этого блога
Integration of PostgreSQL with MS SQL Server for those who want faster and deeper
Recently habré was already published integration PostgreSQL and MSSQL. But, items there is categorically not enough. Therefore, the objectives of this publication are the following: the the to broaden and deepen publicly available information about FDW for MSSQL-called tds_fdw to tell the difference in major versions and describe basic compatibility issues; the to talk about the possibilities of optimization of queries that use the foreign table; the to address the subject of caching external data in a materialized view; the to say a few words about the exotic ways to integrate PostgreSQL and MSSQL. the Installing and configuring TDS FDW The guys from PostgresPro already sufficiently said about this process, I will not repeat. Will leave a few links to the official PostgreSQL documentation and examples from tds_fdw: the the creating an extension (extension) in PG: off.dokumentacija ; the server: off.documentation , example of tds_fdw ; the creating
Parse URL in Zend Framework 2
Objective: the Have a method to disassemble the components of the string containing the URL. The string can contain both absolute and relative URLS and both these options should be correctly parsed. the And in the drain, let's say the "wrong" format absolute links without "http://". Further in the text links to the "wrong" format will be called partial absolute references . the Implement support for the "RF" domain. the Example: site.ru/page.php /page.php site.ru/page.php the scheme http the host site.ru site.ru the path page.php page.php page.php Implementation of paragraphs 1 and 2 of our problem In this we should help the class Zend\Uri\Http . He has we need methods parse($uri) , getHost() , getPath() , etc. But! When we parse the URL and type " site.ru/page.php " (without the " http:// ") getHost() will return an empty string and getPath()
Custom database queries in MODx Revolution
This topic will certainly be useful for those who have quite a lot of projects on MODx Revolution, as with the usual sites of business cards is enough and the standard working methods of a La $modx- > getObject() , $modx->getCollection() , etc., and these methods are inherently not just a job database, but also with the objects of MODx. When working with large projects methods a La $modx- > getCollection() for us is not the best solution for two reasons: 1. The overexpenditures. These methods are not just getting data from DB, but also create instance of the retrieved objects. In this case, getting information about 10000 documents, we get 10000 objects of modResource that it is not very cool. 2. The task is complicated by the count of records. In addition to the direct difficulties of counting even at the query level, even if you get 10 records of the same document (for example), MODx will return as a result only one object modResource. Although often that will su
Комментарии
Отправить комментарий