3 ms·
From the top of my head: less animations, no autocorrect on the keyboard, quicker killing of applications, memory pressure events integrated in the built-in app
by janjongboom 12y ago
From the top of my head: less animations, no autocorrect on the keyboard, quicker killing of applications, memory pressure events integrated in the built-in applications so they clear out stuff when needed.
More information can be found on the Tarako[1] info page at MDN. I saw the finished device (I have a dev version here with an old build) last week in Oslo and was surprised that it worked that well. Panning the homescreen had no jank and opening and closing apps was fairly fast.
[1] https://wiki.mozilla.org/FirefoxOS/Tarako https://wiki.mozilla.org/FirefoxOS/Tarako
- bgirard 12y agoThat's right. On the graphics side if you drop the resolution of the screen you can drop a lot of memory and CPU power. Trading off features like pre-rendering (display port) on the newer builds will save you more memory and CPU cycles at the cost of waiting a bit of content to come in while scrolling. Really it means that any time you fall off the well optimized paths you're going to notice it more. It mean being more careful with how the app are designed and which feature they use. Of course content that really pushes the throughput like canvas games will be slower. But in those cases the browser's rendering pipeline (layout, style, visibility, display list) isn't running so you minimize the overhead there.