Today, developers increasingly need to be thinking about a mobile component and scenario, so they have to consider the actual fragmentation of this incredibly fast growing market if they want to be successful. I discussed the differentiation and fragmentation of the ecosystem in my previous post. In this post I am trying to synthetize what the approach to a mobile development looks like today.
All the responses to these questions likely come with compromises that will impact the customer reach, the revenue, the flexibility, the maintenance cost … There is no absolute right response… it depends…
Actually, when someone wants to make its services or applications available on different mobile platforms, they are offered several different approaches (bear with me here, I might be over-simplifying, but I do have a point I want to make…) that they will have to choose between based on responses to all these questions:
Note that these approaches are not exclusive.
This is where interoperability comes into the game. Whichever way you decide to go, you will need to think about the following things:
All of these considerations are interoperability ones. In a perfect world, you wouldn’t even have to wonder as all devices would support all sort of apps that connect to all sorts of back ends, and software would be developed with any sort of tool… (not sure I am depicting an ideal world here J).
So my next blog post will take a look at what Interoperability looks like for the mobile platforms these days.
Very Nice, queries & suggesstion to be asked before mobile app development, if you are an user experience of mobile?