Skip to main content

‘HTML5 vs. Hybrid vs. Native Dilemma’ When You Build Enterprise Mobile Applications - The Bigger Picture

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!!

Popular posts from this blog

MVVM - Binding Multiple Radio Buttons To a single Enum Property in WPF

I had a property in my View Model, of an Enum type, and wanted to bind multiple radio buttons to this.

Firstly, I wrote a simple Enum to Bool converter, like this.

public class EnumToBoolConverter : IValueConverter { #region IValueConverter Members public object Convert(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture) { if (parameter.Equals(value)) return true; else return false; } public object ConvertBack(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture) { return parameter; } #endregion }

And my enumeration is like

public enum CompanyTypes { Type1Comp, Type2Comp, Type3Comp } Now, in my XAML, I provided the enumeration as the ConverterParameter, of the Converter we wrote earlier, like

Creating a quick Todo listing app on Windows using IIS7, Node.js and Mongodb

As I mentioned in my last post, more and more organizations are leaning towards Web Oriented Architecture (WOA) which are highly scalable. If you were exploring cool, scalable options to build highly performing web applications, you know what Node.js is for.After following the recent post from Scott Hanselman, I was up and running quickly with Node.js. In this post, I’ll explain step by step how I’ve setup Node.js and Mongodb to create a simple Todo listing application.Setting up Node.jsThis is what I’ve done.1 – Goto, scroll down and download node.exe for Windows, and place it in your c:\node folder2 – Goto IIS Node project in Git at, download the correct ‘retail’ link of IIS Node zip file (I downloaded the already built retail package, otherwise you can download and build from the source).3 – Extract the zip file some where, and run the install.bat or install_iisexpress.bat depending on your IIS Version. If you don’t have IIS in…

Top 7 Coding Standards & Guideline Documents For C#/.NET Developers

Some time back, I collated a list of 7 Must Read, Free EBooks for .NET Developers, and a lot of people found it useful. So, I thought about putting together a list of Coding Standard guidelines/checklists for .NET /C# developers as well.As you may already know, it is easy to come up with a document - the key is in implementing these standards in your organization, through methods like internal trainings, Peer Reviews, Check in policies, Automated code review tools etc. You can have a look at FxCop and/or StyleCop for automating the review process to some extent, and can customize the rules based on your requirements.Anyway, here is a list of some good Coding Standard Documents. They are useful not just from a review perspective - going through these documents can definitely help you and me to iron out few hidden glitches we might have in the programming portion of our brain. So, here we go, the listing is not in any specific order.1 – IDesign C# Coding StandardsIDesign C# coding stand…