When NTT DATA evaluates frameworks, it considers hardware support, device-level access, rendering engine support, and whether the framework is targeted at mobile sites, Web apps, hybrid apps or native apps. It also considers security, accessibility, UI widget designs, performance, the quality and comprehensiveness of documentation, and whether the framework integrates with a Java or .NET-based back end.
Each framework also has its own benefits. As an example, jQuery Mobile is great but it’s not optimized for mobile. It looks great on iOS but it’s not good for any other platform. Sencha Touch and Kendo UI are more complete packages, and then you have Appcelerator Titanium, which is good for prototyping. No single framework provides a complete solution but each has its benefits depending on your modernization needs.
Generally, over time, native OS’s such as Android or iOS are not the only platforms your applications will need to support. Choosing something like a Sencha Touch or Kendo UI that supports all the major platforms and has the right plug-ins may be a good option for a hybrid or cross platform modernization initiative. You also want something that offers rich UI functionality, rich native device functionality, and has the proper architecture framework built in. It should also allow you to control your code, provide persistence and meet your performance requirements. While many of the frameworks focus on the client-side, there are also back-end considerations, since mobile devices are constantly interacting with services.
Overall, in today’s age of disruptive technologies, it is important to understand if a Mobile framework makes sense and aligns to the business objectives of a modernization program. Not every mobile modernization project really requires using a framework per se but this is where it is important to engage experts in this area to provide the right advice upfront to ensure successful adoption of the right technologies.
Post Date: 31/01/2014