12
PEER TO PEER: THE QUARTERLY MAGAZINE OF ILTA | SPRING 2016
BEST PRACTICES
HTML5 or Native: Making the Choice
regularly. Choosing the native path requires that
you develop for the desktop, all desired mobile
devices and differing MDM systems with their
own security and deployment requirements.
This can easily exceed 20-plus versions based on
differing devices and MDM options. In contrast,
HTML5 is based on one program with four
variations (i.e., Internet Explorer, Edge, Safari and
Chrome).
What about a hybrid approach? According
to recent Gartner research, hybrid development
platforms will account for over 50 percent
of mobile apps by 2016. Hybrid development
provides the security and deployment advantages
of HTML5, while equally addressing the
performance, functionality and distribution (via
app stores) of going native.
» Maintenance and Support: A single code-base
provided by HTML5 development translates to
simpler maintenance and support. Testing is
also a big factor, as testing and quality assurance
resources add to budget costs when you want to
support multiple platforms. You will need a lot of
devices to test for each platform. Even if you are
building Web apps, the costs of optimizing for all
the browser/device/manufacturer combinations
should not be underestimated.
While there is no silver bullet for deciding your
firm's soware and application development strategy,
a variety of critical business requirements will guide
the decision-making process. The choice between
HTML5 and a native application depends on individual
user requirements, broader security concerns, the
importance of performance and app speed, and ––
above all else –– a firm's ability to develop, support and
maintain apps based on available resources. P2P
Hybrid
development
provides the
security and
deployment
advantages
of HTML5,
while equally
addressing the
performance,
functionality and
distribution (via
app stores) of
going native.
