Over a million developers have joined DZone.

Building Mobile Applications for Enterprise: The HTML5 vs. Hybrid vs. Native Dilemma

DZone's Guide to

Building Mobile Applications for Enterprise: The HTML5 vs. Hybrid vs. Native Dilemma

· Web Dev Zone ·
Free Resource

Jumpstart your Angular applications with Indigo.Design, a unified platform for visual design, UX prototyping, code generation, and app development.

This post is mainly about building Enterprise Mobile applications. Today I was reading Charlie's post about building mobile applications, and was analyzing the hybrid application scenario from an Enterprise Standpoint.


The Bigger Picture

Most of the recent conversations I had about building enterprise mobile applications starts with questions like “Whether I should go Hybrid or Native”. It is true that a lot of organizations are interested to go the ‘hybrid’ way because of cost concerns – but in my opinion, any decision should be customer driven instead of cost driven. So, the answer for this question should be driven by “What will give the best user experience to the end user”, instead or/along with asking questions like “how we can reduce the cost”. This is true for all apps, not just for enterprise mobile apps.

Beyond this, from an Enterprise Standpoint, I think achieving end point independence is another way to reduce your cost and future proof your investments. So, while “HTML5 vs Hybrid vs Native” is just one decision parameter, there are few more parameters to consider when you talk about a mobile strategy. Including,

Concerns during envisioning phase

    1. Target user analysis
    2. Choose a simple framework to begin with, like Forrester’s POST approach
    3. Gap analysis and portfolio rationalization

Deciding a strategy for Mobile Application development & Delivery

    1. Mobile Web/Pure HTML/JS
    2. Hybrid apps (HTML5/JS apps in Native containers  - Like Phone Gap and/or native parts/plugs like in Titanium)
    3. Native apps

Concerns regarding a Common Service Layer

    1. Building/Implementing a scalable Common Service Layer
    2. Implementing a scalable broker system between the service layer and legacy systems
    3. Ensuring standards (like using REST)
    4. Identifying and integrating a Content Delivery Network (CDN) for media delivery

Testing Model

    1. Security and Performance
    2. Device based testing

Submission Governance

    1. Payment model
    2. Keep track of submitted applications
    3. Analytics
    4. Feedback tracking
    5. Continuous improvement

So, all these are parts of your mobile strategy.  Especially when you talk about Enterprise mobility,  achieving Mobile End Point independence is a key concern, and organizations understand the necessity of making their business logic and data available to multiple end points. REST is evolving more and more as a default choice for building a public service layer, around your existing data and intelligence.

Hybrid vs Native

Now, specifically about Hybrid vs Native. Here are the main Pros and Cons as I see it.

For Hybrid applications


  • No need for device specific development
  • Better ROI as same code base can be re-used (to an extent) across multiple platforms
  • You can still access some of the device features
  • Can be packaged for additional channels, (Chrome Packaged Apps, Awesonium)


  • UI specialization is difficult
  • Can’t be as responsive and feature rich as ‘pure’ native applications
  • May hit limitations when implementing specific, optimized features

For Native Applications


  • High degree of customization, can satisfy edge conditions
  • High degree of usability


  • Scattered/multiple platforms
  • Investment required for each platform
  • Non unified code base, not much re-usability
  • Teams with multiple skill sets required

And More

That said, again, think beyond the “Hybrid vs Native” point when you think about Enterprise Mobility.

From a Middleware Perspective

  1. Select a strategy where storage and compute resources of your Mobile apps can reside in Mobile devices, on-premises servers and Cloud computing infrastructure.
  2. Use a brokered service for connecting, communicating and brokering between Mobile apps, on-premise resources and Cloud/Middleware environment.
    • Custom implementation on top of brokers like Windows Azure Service Bus
    • Build on a Mobile ready WOA stack like Marlabs Matrix platform
    • Third party Mobile Middle ware platforms like Syclo etc
  3. Use Cloud based federated authentication services and security systems if you need support for multiple authentication providers – Like Azure Federated Authentication.
  4. Adopt cloud/service based push notification services for sending and receiving notifications from your Mobile devices.
  5. Choose a proper content delivery network that supports bit rate streaming to deliver video content. For example, Azure CDN or Limelight True Reach API.
  6. Enable APIs for provisioning, tracking and feedback reporting.

From a Middleware Perspective

Submission governance includes deciding a proper strategy for payment model, usage tracking, analytics and feedback reporting. The Submission Governance should ensure

  • Minimum criteria for submitting an application to the app store
  • Users are heard properly – Feedbacks and ratings should be used for identifying features
  • Releases and updates are following user expectations

So, happy coding!!

Take a look at an Indigo.Design sample application to learn more about how apps are created with design to code software.


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}