Thursday, November 25, 2010
Interrupt handling (m-cube: Level 1)
Wednesday, November 24, 2010
Graphics & UI (m-cube: Level 1)
Tuesday, November 23, 2010
Certification (m-cube: Level 1)
Monday, November 22, 2010
Saturday, November 20, 2010
Distribution (m-cube : Level 1)
An effective distribution strategy plays a vital role in the success of any mobile solution. As the applications’ distribution directly affects the billing procedure, it is imperative that this strategy is worked out in the design phase itself.
Distribution largely depends on the type of application.
Typically, consumer mobility applications may be distributed via App stores, carrier deck or app aggregators like (get jar & cell mania). These app stores have now reduced the entry barriers and helps us reach out to the market in no time, like OVI store - you can register as a publisher just in 1$, get your applications signed for free and launch to the audience in more then 190 countries in almost in no time.
For enterprise mobility, corresponding Mobile Device Management systems should be planned and configured according to the expected load.
In case of a client/server application, like a mobile banking or a stock market app that needs frequent interaction with the server..you may feel the need of distributing it from your own Deck i.e. Over the Air from your own Website.
This makes sense when it is complicated to share the revenues of these apps with carriers, aggregators and/or store fronts while providing a quality service to the customers. In setting up an OTA distribution infrastructure for these cases, we need to make sure of the following two things:
a- Auto-detection of device platform and model, so that the right build is delivered to the requesting mobile device – this is achieved by searching the WURFL database using user-agent string fetched from the mobile request.
b- Auto-upgrade infrastructure is required on both the client & server side, so that on every login, the server can compare the client build version with one available on OTA server and give notification of optional/mandatory upgrade to the client app.
Another way to reach the market quickly is to embed the application on the device before the same is launched. You can do this by making an alliance with a renowned handset manufacturer like Nokia, Samsung, Motorola, etc for this.
Stay tuned, I will be posting the details of other attributes and best practices very soon.
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.