How Long Does It Take To Build A Native Mobile App?

Found an interesting info graphic on How Long Does It Take To Build A Native Mobile App?

From the Post

In a survey of 100 native mobile developers, Kinvey determined that creating a fully functional and polished app takes a team about 18 weeks from start to finish. That includes both front-end design and user interface as well as back-end integration like push notifications, user management and authentication, caching and sharing through social channels.

I know what many app developers are thinking when they hear that: “18 weeks?! Who the hell are these turtle-slow developers?” On the other hand, enterprise developers are probably saying: “18 weeks?! We are only halfway through by that point.

Original Link here

Good One.


Enterprise Mobility Trends

Recently happened to read the post Current Trends in Enterprise Mobility from the InfoQ website. Its a post referring to the InfoGraphic created by XCubeLabs.
Enterprise Mobility

Key Points from the InfoGraphic 

HTML5 will become the preferred choice for Enterprise Apps. Nearly 3/4th of Fortune 500 companies are taking steps to deploy a HTML5 based solution.

Mobile Apps in Enterprises

  • 70% of mobile applications developed during 2007-2011 will become obsolete or candidate for a remake by 2012.
  • Native Mobile apps will continue to dominate transaction oriented and revenue generating mobile applications during 2012-15 time frame
  • By 2014, 40% of the Fortune 1000 organizations will employ a MEAP solution for Mobile apps development.

Preferred way to Acquire a mobile solution

  • 36.8% of the enterprises prefer to built them in-house,
  • 31.5% intend to outsource them,
  • 30.7% plan to buy one,
  • 20.1% are going to buy a MEAP with an SDK and configure the app in-house,
  • 20.1% also want to buy a MEAP and SDK but outsource the development,
  • 6.1% have other unspecified options.

A Good Reference!!!
On a side note, i really liked XCubeLabs website. 🙂

Original URL

Going Mobile : What should be my mobile strategy?

I am sure, there are 100s of posts already on this topic. This is a summary of my thoughts/understanding on Going Mobile.

Today, if you have an existing product, there is no way you can ignore about having a mobile application. Though its not mandate that you need a mobile solution today, but the growing needs will make it a necessity in the near future.

Great, we need to have a mobile application. Mobile is just another User Interface/Presentation End point. We had windows version earlier, then we moved to a web version, and now to a mobile version. Let us have a 50K Budget and get it done?

WOW, if only its the case, you will not see such a hype around enterprise mobility. The answer is definitely not that simple. There are quite a bit of things one need to consider before adding mobility to their product. The variance in the number of devices, operating systems and their capabilities has made it really complicated.

Wait, but i heard having a Cross Platform Solution will solve all this problem. Every large services company is talking about MEAP, Cross Platform application etc etc. to solve this problem. Well, the answer is May be.

But, before jumping to this lets try to understand what “Going Mobile” Means?
Going Mobile means that we have a strategy to address the business objectives. Typically any strategy is derived from the Mission and business objectives. What it means is that, we need to have clear list/statement of the problems we are trying to solve and the results to expect after solving the problem by when.

A Strategy (Plan to address) could be formulated, based on the business objectives. Based on the strategy it is then easy to define a set of guidelines for decision making.

  1. What do we want to achieve with our mobile solution?
  2. Who are our target users and what devices are they using?
  3. How can me make our mobile solution available to them?
  4. What is our competition doing in this?
  5. What kind of budget do we have?
  6. When do we want to go to market?

Based on the business problems we are trying to solve,  a technology implementation could be chosen. Following are the key considerations while making technology choice.

  1. User Experience
  2. Platform Coverage
  3. Performance
  4. Required Device Capabilities
  5. Offline

What should be my technology? Should i go with Native or Hybrid or HTML5?
You can choose a technology only based on your requirements. Your mobile strategy should be based on the problems you are trying to solve, and only that can help you decide that. Google Search can give you 1000s of pages on this. But the reality is there is no silver bullet. This decision cannot be made without context or based on personal preferences.

Okay, how do we decide whether to use MEAP or not?
Gartner has developed a Rule of Three to check whether there is a need for a MEAP solution

  1. There are 3 or more mobile applications
  2. There are 3 or more targeted operating systems or platforms
  3. They involve the integration of 3 or more back-end systems

If you have a requirement which fits the above then a MEAP Solution might be a good one to look at.

Cost of MEAP Platform and how generic you want a Solution will also play a key role in the decision making process. No Generic Solution can solve your business problem 100%. Which means there would be a customization. Assuming a MEAP Solution solves 80% of your business requirements, then you have to look at what does it take to solve the remaining 20% requirements. Then it becomes like any other COTS Vs Custom Solutions decision.

Like Desktop, Web, Mobile is also going to stay here. If we are going to enable mobility to our existing product, its very important to do solve the right business problem, so that it can help in monetization.

Useful books:
Architecting Mobile Solutions for the Enterprise
Microsoft Application Architecture Guide

Some useful pointers to look at:
Native or Web: How best to deliver Content to your Audiences?
Mobile Website Vs Mobile App: A Deep Dive
Mobile Website vs. Mobile App (Application): Which is Best for Your Organization?
Mobile Application Development: Native Vs HTML5
Mobile Web Vs Native Mobile App Vs Hybrid
Native, Hybrid or Web Apps?
Has mobile traffic really surpassed desktop internet traffic in India?
Gartner’s Rule of Three

Image Source:
Free images from

Happy Learning!!!

Getting Started with Mobile Application Development

Image: adamr /

Recently, there was a forecast from Forrester that the mobile application development services size will be around $17 billion by 2015. This means that mobile and tablet application development is becoming more and more mainstream.

With the introduction of Tabs in the enterprise segment, the mobile adoption of enterprise products has become a reality.  Enabling mobility with enterprise products is like anyother enterprise application development. It requires a very disciplined approach, following the best practices (TDD, Iterative Development, Continuous Integration, Continuous Delivery etc..) and its definitely a paradigm shift.

If you are Fresher or an experienced developer wanting to get started with Mobile application development, following is the high level skillset which one would require. This list is a combination of mobile development  + software development skills.


  • Mobile/Tablet
    •  iOS, Android, Windows Phone 7, Blackberry
      • Operating System & Framework Basics (File System, Framework Basics)
      • Language Basics (Objective C, Java, Silverlight/XAML)
      • IDE Basics (XCode, Eclipse, Visual Studio.NET)
      • UI Components
        • UI Positioning
        • Graphics
        • Alignments
      • Asynchronous Execution & Multi tasking
      • Logging/Error Handling
      • Data Binding
    • Mobile Web Application Development (HTML5, CSS, PhoneGap)
  • Programming
    • Object Orientation
    • Debugging
    • SOLID Principles
    • Patterns (MVC, MVVM)
    • Automated Unit Testing (OCUnit, JUnit, NUnit)
    • Source Control
      • Check-in/Check-out
      • Label
      • Branch
    • Continuous Integration (Jenkins, Hudson)
  • Web Basics
    • HTTP, HTTPS, Error Codes, Web Server (IIS, Apache etc…), Stylesheets, Post/GET/Put
  • XML
    • Loading, Parsing, Updating
  • Data Access
    • Web Services basic
    • Restful/Soap/OData Services
    • Local Data Access
  • Offline Storage
    • NoSQL Database (CouchDB)
    • SQL Lite/SQL Express
  • Caching
    • NoSQL DB
  • Localization
  • Builds
  • Releases
    • Versioning
    • Release Management Fundamentals
Happy Learning!!!

Web Traffic from the Tablet world – iPad Rules

Interesting Post on the market share numbers for iPad:

  • 83% of U.S. tablet sales.
  • 68.3% of worldwide media tablet shipments.
  • 73% of worldwide sales of media tablets to end users.
  • 61% of global tablet shipments.
  • 80% of tablet shipments in North America.

From the post, it is also clear that though consumers around the world are buying other tablets, but the market share as of now seems to be way behind iPad.

Original URL :

Happy Tapping!!!