Lead Source
Lead Status
Mini Navigation

Blog

What platform should I choose and why?

| Category: Help me out    
   

The previous blog post says all about the “Why” part of embracing mobile technology into your business.

The second part of the blog answers “What” and “Why” that is hiding inside the “What” part!

Alright, it looks like you have decided to embrace mobile technology into the veins of your business but hold on, now the choice of choosing from “yes” or “no” has transformed into multiple choices of choosing what is right for your business.

Let us see the roadmap to mobile solution that we have in the industry.

When we embrace mobile technology, we sound generic. There are deeper details inside the mobile application industry as such.

Broadly classified, we can put forth things that being looked from a bird’s eye view.

We have taken sufficient measures to minimize the technical jargons as not to confuse the new entrants into the mobile industry!

Mobile applications are assorted in the following headings.

  • Native application
  • Web apps
  • Hybrid apps

Let’s directly dive-in to see what the mobile industry is offering us.

Native Applications:

People who coined the notion for mobile application industry are smart enough to follow a naming convention that doesn’t confuse the user and also at the same time makes it easier for anybody to guess underlying concept.

Now, you have guessed it right!

Yes, the native application is all about the device native features. When we say “native features” it is not the geographic location we mean, but it is the local resources that can be used to run the application.

A mobile device or Smartphone is build very similarly like a laptop or a Desktop computer. The Smartphone holds a CPU, a RAM, an input device and also an output device as well. (Technically the input and the output is- The screen)

A native feature includes the phone’s entire feature list like camera, memory, gallery, contacts, making a call or creating and sending a SMS, Accelerometer, compass and also the GPS and whatever that is a part of the system or phone’s hardware architecture that even includes the processor, the RAM, etc!

And when we say a “native application”, the application takes the complete and full privilege to use the system resources or features that are said. The native application is designed and developed in such a way that it uses the system resources optimally as an administrator to deliver a robust performance at the system do what is best for the internal system!

These applications are developed and deployed in platform or OS specific distribution platform that are called App Store for iOS applications, Play Store for Android applications and Marketplace for Windows Phone applications and so on and so forth.

Web applications or mobile web:

   The “web apps” as the name suggests it is primarily based on the web related resources that has the browser at the top of the requirement.

The web apps look like a Native app but runs on a native browser in the device with an exception of not having an address bar or navigation bar that usually fills the top most area of a mobile browser. 

These web apps cannot be “installed” in a mobile device but can be “bookmarked” to the home-screen.

Talking about the features that it holds, we can integrate native gestures like swiping to left and right to view pages, storing the content in the browser cache for offline viewing, sensing the landscape and portrait orientation and adjusting the screen as per.

One of the best examples is,

                                          m.facebook.com

Although, they have a Facebook application in the app store, for better reachability they have the mobile web or the web app that more or less mimics the native app.

There are active talks in the industry that other functionalities like camera integration is soon to be merged  inside the package of HTML 5 which will pave for minimizing the further demarcation between mobile web and native web and even hybrid application.

Hybrid applications:

Hybrid applications is easy to define, just add the above two definitions, simple ain’t it?!

Let’s skim through what it does now, the hybrid application as the name suggests is a culmination of both Native application and Mobile web put together. Although the application runs on a native browser, the hybrid app has a privilege to access native features and functionality just like a native app.

If a “how” question arises in your mind, it’s time to look for answers below!

The cross platform technology makes it work like a native application by using a “wrapper class” that wraps the mobile web in the name of native application thus making the system process its request as a native app rather than a mobile web.

The cross platform technology encompasses all the features that a native application can, but one the reason still it hasn’t replace the native app is that, the look and feel of the application is highly dependent on the network speed as everything about the performance of a hybrid application is about “page-loading” time just that of a browser.

However, once the application is designed and developed, we can deploy it to the application store or distribution platforms and can “install” them rather than creating a “shortcut” in the case of mobile web.

With this, the series that says “Why” and “What” come to a grand conclusion.

But stop not now, the next series would be little more interesting as we will be catching some intricate details about “How” the mobile technology is being built and what are the challenges involved and also for better transparency, what are the best practices to build them.

Catch you soon in the next page . . . :)  

comments powered by Disqus
Subscribe

Follow Us