Whatever the mission, CNSI's mobile application development practices help government agencies bring mobility to their business by harnessing the power of information - anytime - on a variety of mobile platforms.

In keeping with your business process requirements, our application architecture model can include three options:

• Native Applications: These are standalone apps, residing natively on smart phones, and extensively leverage native APIs (geo location, accelerometer) of the mobile platform. These provide a rich user experience allowing offline capabilities and improved performance. However, these applications can manage a limited volume of data on the phone, have a relatively complex deployment procedure, and pose a possible security risk with locally stored data. So care must be taken to deactivate the device in case of loss or theft, to ensure data integrity, privacy, and security.
• Mobile Web Applications: These are internet based application designed to be accessed by web browsers from smart phones. These applications provide access to dynamic data, with easy integration to other web content and are low maintenance. However, these have no offline connectivity, have a high dependency on network availability / speed (which can be a issue in remote areas) and therefore are limited in the use of system data v/s integrating and leveraging the native APIs of the platform.
• Hybrid Applications: These are internet based application designed for a richer user-experience by leveraging some of the native APIs and therefore provide a middle ground for the other two models. Hybrid apps provide a possibility of building intelligent web applications, which can also leverage native features (i.e. contacts, geo-location, camera etc) to improve the user-experience and enhance business productivity. These do have a more complex architecture with limited offline features (leveraging HTML5), and have a dependency on network availability / speed. However, these applications allow for asynchronous data transfer making them very conducive for conducting business in an offline setting when required.

CNSI Mobile API architecture comes with a service and client tier allowing:

Minimal Coding for a given use case on the device All business logic to be enforced via the service processing layer in the back-end Data validation at the client level reinforced by the service processing layer Use of HTML 5 Canvas for the application layout and design All communications between the device and the server over https protocol to prevent wire snooping or data stealing Device specific user interface rendering components on the server side minimizing application updates Implementation of asynchronous queuing message model for data updates and inserts