- Ubiquity. Will the chosen mobility platform work on as many customers as possible whilst giving the maximum chance of profit and/or adoption.
- Reduced Development Costs. Will the chosen mobility platform increase or decrease development time(s). Will the platform also enable or empower a uniform design experience across one or more platform(s) that compliment proposed ubiquity needs.
- Workforce Ready. Will the chosen mobility platform stand up to various conditions workforce is likely to put them through in their daily work style(s). Will they be compliant for industrial work not just office work, will they have work around to employee’s wearing gloves (safety) and so on.
Mobility is fast becoming a topic, which does not seem to yield a concrete answer. The more you sit down and analyses mobility within an organization, the more you begin to notice there is a lot more choice on offer than before. That is to say, not getting an answer is not due to lack of choice. The plethora of choice available is what is causing the paralysation of selecting one or more platforms to adopt. A company today who as adopted .NET cannot accurately answer the question around which mobile device they should target. They cannot answer this, simply due to the uncertainty of what Microsoft’s current product line(s) look like today, let alone unsure if what they propose will fit tomorrow. A company first must contend with the idea that the .NET developers within their pod will have to be outsourced and/or up skilled in order to begin mobile development. Choosing a platform of any kind in the mobility offerings is often times based around a few conditions such as these: