IT Transmission to Mobility

Reach of Mobile devices is enormous in comparison with desktops. That's the reason every organization is willing to make their applications get onto Mobile as early as possible and make the applications usability more and more than limiting the users to sit in front of desk and make the work. Mobility is evolving technology with too many number of options in terms of technologies, frameworks & devices. Which is one of the reasons the organizations are spectacle about the transmission. When Organizations want to get their Applications onto mobile, what is that they should be looking at?

Here are some of the important points that has to be determined

  1. Target User Groups:

    Organizations should decide on the user group who are going to use the mobile applications that they are planning to build.
    Is the Mobile application, local to organization, or external or mix of both?

  2. Target Devices & Platform:

    There are many mobile platforms exist in the market ( . Well known platforms are Android, IOS, BlackBerry, Ubuntu, Windows 8 etc.
    Most of the time, unless it is Corporate specific policy, Organization tend to target more than one Target Device. Choose top three such devices which is mostly being used in the target user groups. If the range of target user groups is vast, and if the Organizations feel like, the application is more open to worldwide users, it's better to target all devices.
    Target device's choice is the most important, because it lets you choose the appropriate framework accordingly.
    For example, if you are targeting for any top three devices, one may choose multiplatform native application building framework and IDE such as Appcelerator. If the target is much vast, targeting most of the devices, one may choose HTML5 based frameworks, such as PhoneGap and/or JQuery Mobile etc.

  3. Type of Mobile Application:
    When it comes to determining the type of Mobile applications, there are majorly three types of applications:
    1. Native Mobile Applications: Applications that are platform specific and that can run internal to the phone. It doesn't require any internet connectivity once installed on device. Such applications can make use of full features of the device. Such applications are developed completely on native language that of the device. For example, for IPhone's native application has to be built using the Objective C, on IOS. Examples of such applications are calculator, or conversion based apps.
    2. Mobile Web Applications: Applications that can run on any device, as long as the device as one browser. Such applications are mostly like a web site loaded on a web browser on desktop. However, the adaptability framework makes it fit into the devices like Mobile and still displays well formatted UI. Such applications are very quick to build, don't need any specific knowledge of the device native language. However the downside is that, they can't use the device specific functionalities like, camera, location, sms etc.
    3. Hybrid Applications: This carry flavor of both the above. These applications are easy to build and does not require to learn any native language for each device, same time, these applications can also communicate with the device specific features like Camera, and Location tracking using the APIs provided underlying frameworks. The advantage of it is straight forward that one need not learn three different languages to build the same application on three different devices.
      Organization can choose to build Hybrid Applications for major enterprise level features, or functionalities that has business logic and where collaboration is required.
  4. Choice of application & features:
    • In Reality, not all desktop/web applications can be implemented completely as a Mobile
      1. Mobile Application can't replace Web completely at any point of time.
      2. Both Web & Mobile Apps should co-exist.
    • Simple yet very important features of different applications can be identified as mobile app candidates.
    • Some of the candidates could be:
      1. Most widely used functionalities
      2. High visibility & High level Management executive usable features
      3. Workflows
      4. Reports
      5. Simple tasks related features that involves very few data entries.
  5. Common Framework:
    Organizations may have a doubt, if they have to build new application duplicating all the existing web application. Nope, if it's properly designed at the stage of Architecture.

    Here is the link to the POC that we build for an Organization show casing this capability. 85% of the code is reused between Web & Mobile Application. Which means, only 15% of Cost on top of the new Web application gives the Organization a Mobile app with most of the features part of Web. GEEKS-V Architectural team has unique efficient framework for the development of Mobile applications, alongside the web applications, where in 85% of the code is reused between Web & Mobile Applications.