lg optimus g pro - AOL.com
lg optimus g pro - AOL.com
lg optimus g pro - AOL.com
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
DISTRO<br />
03.08.13<br />
FORUM<br />
EDITORIAL<br />
The web-as-app ap<strong>pro</strong>ach doesn’t<br />
work particularly well when you’re<br />
trying to deliver a rich and smooth<br />
experience, especially on mobile.<br />
in the Western world. This poses significant<br />
<strong>pro</strong>blems for the fledgling OS since<br />
it relies on constant connectivity to<br />
deliver information. Sure, some services<br />
can cache data locally for offline use,<br />
but that’s a feature of HTML5 that has<br />
yet to be widely embraced by devs.<br />
Mozilla thankfully has Nokia offering<br />
some support for the disconnected with<br />
its maps, but most “apps” (and Mozilla’s<br />
insistence on calling them that is<br />
frustrating) will require an internet<br />
connection to function.<br />
As we mentioned, it is possible for<br />
HTML5 apps to be downloaded and<br />
installed locally. Nokia’s mapping solution<br />
is one of the confirmed examples.<br />
However, many of the apps offered are<br />
not “packaged” (Mozilla’s terminology)<br />
and installable. The vast majority<br />
of the tens of thousands referenced by<br />
Mozilla’s CEO Gary Kovacs during their<br />
big event at Mobile World Congress are<br />
“hosted.” In other words, they’re web<br />
apps — which Mozilla is using to pad<br />
its marketplace. (This is almost exactly<br />
what you’re treated to when exploring<br />
the Chrome Web Store.)<br />
The “packaged” versions of the apps<br />
are, essentially, just websites zipped up<br />
in an archive. This carries its own set of<br />
issues. As previously noted, HTML5 is<br />
widely perceived as suffering from performance<br />
issues when <strong>com</strong>pared to native<br />
apps. While some have claimed this<br />
is because of poorly constructed code,<br />
and should not be laid at the feet of the<br />
standard, it appears that many devs<br />
struggle to <strong>pro</strong>duce efficient <strong>pro</strong>ducts<br />
using it. And if said developers continue<br />
to struggle with HTML5, it may be tough<br />
to convince them to embrace it the way<br />
they have native code. The evolutionary<br />
take on HTML may make it simple to<br />
create cross-platform <strong>pro</strong>grams, but the<br />
differences in rendering engines and the<br />
layer of abstraction itself make it difficult<br />
to optimize performance for all of them.<br />
And while Mozilla has created hooks for<br />
apps to get deeper access to the hardware,<br />
it remains difficult to implement<br />
many of the more robust features users<br />
have <strong>com</strong>e to expect from applications<br />
using HTML5.<br />
Sparse coverage and slow speeds<br />
will pose significant usability issues for<br />
consumers in developing countries, but<br />
perhaps an even bigger stumbling block