If you are planning to enable any of your existing application on mobile  (be it for your consumer or employees), make sure that you have the needed web services is place before you start, in most cases these are the same services (assuming you have service oriented architecture in place) which are accessed by your intranet or online applications currently.

When it comes to mobile you may not need all the data your existing service returns or you may wish to call multiple services before you respond to one mobile request (to limit the number of server calls). To accomplish this consider building mobile service layer, containing wrappers around existing services and also there may be services in this layer which are specifically built for mobile clients

Other architecture considerations for building a mobile app could be building synchronization component for apps which may need offline content, Notification services to push ad-hoc or scheduled reminders, Integration with Third party applications, DRM, Mobile Analytics and Security (MDM).

Typical Enterprise Mobility Architecture

• Author
• Recent Posts

Kamal Chandramohan

Practice Manager - Mobility at Aspire Systems

As a Practice Manager for Mobility at Aspire, Kamal contributes his knowledge and experience in the world of Mobility and Digital Transformation to our existing and prospective customers in building a digitally transformed mobile experience for their end users. Kamal advises our customers on building a Mobile strategy which would lead the way for better user experience, customer engagement and increase in productivity resulting in Customer and Employee satisfaction.

Latest posts by Kamal Chandramohan (see all)

• How can a mobile application lower your motor insurance premium and improve safety? - November 18, 2015
• Aspire’s Mobile CoE and it’s focus on Xamarin - October 15, 2015
• Dalvik to ART, Why a change of runtime in Android Lollipop? - January 30, 2015