Saturday, September 4, 2010

Impetus Mobile Maturity Model (m-CUBE)

The market for mobile applications hasn't reached mainstream adoption just yet, but is poised to hit the $9 billion mark by 2011; device makers, service providers, and software vendors all have some pie in this growth.

The projected growth is noteworthy, but there has been talk in the industry around issues that have kept mobile apps from gaining widespread adoption in the business world. It’s extremely vital to understand that why a killer idea doesn’t turn into a successful mobile solution, what’s missing.

Is it related to lack of understanding of the business objectives i.e. ignorance of short term and long term goals, or it’s because the usability not been considered while designing, or the sizes of business causing huge data traffic which is difficult to manage. We all are aware that technologies & device specific hurdles are very critical to understand in mobility. And when it comes to bringing mobility in enterprises, their IT departments are hesitant to implement any mobile applications without proven security that protects the home network and the user's device. Be it any issue, it becomes a major factor affecting mobile solution adoption & growth.

Looking at these challenges of mobility, Impetus has drawn best practices of mobility i.e. Mobile Maturity Model. We derived this model while handling & contributing to different releases of hundreds of award winning mobile products & services.

Impetus Mobile Maturity Model (m-CUBE) is a suite of best practices that we have identified. This addresses all horizontal and infrastructure design issues of mobility. 19 attributes of m-CUBE are very critical & should be considered in the various phases of mobile product development .i.e. analysis, design, development, and deployment & post deployment. Attributes under these phases are acknowledged in a manner such that they give direction for the development at a later stage. Our best practice ensures that all the parameters and their implications for a given set of mobile requirements are handled adequately and at the right time. While adopting mobile maturity model we design mobile application in a way it becomes easy to add new functionalities as per changing business needs.

Keep following me on this blog, I am going to take up these various dimensions of this maturity model one by one.

1 comment:

  1. Nice blog. And i have noted some information from your blog that was really a good informations. Thanks.
    Joomla Development