![]() ![]() It’s your job to build a deep understanding of what users are experiencing That’s why testing with real devices is crucial because your $1,000 iPhone performs almost as well as a reasonably new Macbook Pro. We’re talking total lock up on a slower device-almost unresponsive for several seconds. Forget 620 it’s more like 2–3MB decompressed. Today, 620Kb of JavaScript is the global median, which sounds like a lot, but remember, this is GZipped. ![]() Testing on a real device can become pretty limiting too, thankfully both Web Page Test and Calibre have got you covered.Īs you’ll notice, the parse time varies greatly between devices. Lower-powered devices will feel sluggish, whereas newer devices can run several pages simultaneously without breaking a sweat. The more script, the more your app depends on local single-core performance. If you develop and test with a Motorola G4 starting today, and it performs ‘kinda well’, it’ll be excellent for everyone who uses newer, more powerful devices.ĭevice specifications are huge factors for a smooth, delightful user experience, mainly if you’re relying on JS for interactivity and rendering. The cheap phones are still shipping with 512mb-1GB of RAM. There’s quite a lot of RAM (2GB)-memory just hasn’t gotten cheap.The Moto G4 is a great candidate for a device that will be the median in late 2017 or early 2018.The actual median is a slower, older, cheaper phone.Most people receive phones via their carrier, and the devices vary greatly over demographics and geography.Īfter conducting this research, Alex arrived at the Motorola G4 - which is statistically quite above average. It’s best to choose a device on that chipset. These Quad-core CPUs are everywhere and also come with hardly any cache. There are billions of Android devices in the wild that are using the Qualcomm 28nm A53 Chipset.Sometimes they’re fast and occasionally slow (A57 vs A53 Chipsets). The Nexus 5X wasn’t an option due to thermal instability.The device would need to be slightly ahead of the 2016 average, making it a strong candidate to purchase as a test device.This device needed to be globally available, reasonably affordable, have minimal bloatware, and thus, a low barrier to entry.The criteria for such a device are as follows: There’s some subtlety in testing on the suitable devices, but thankfully Alex Russell was kind enough to share his 2016 research, in which he did some detective work to find a single mobile device that best-represented devices in the wild could be purchased today and would make for a trustworthy test phone in the years ahead. Test using realistic average network conditions for a given market.Test in all major browsers for a given market.Test using real hardware (and automate your testing).How on earth are we meant to test all these and understand their quirks intimately? Such a wide range of devices in the market leaves plenty of web developers with a sickly feeling in their stomachs. What I find striking about these statistics is the tremendous number of devices and the fact that I’d never heard of a handful of these vendors-who sell more than 200M devices in just three months. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |