Mobile development - to be native or not!


Whenever you start a new cross-platform project, there is always the question about whether to use native languages and tools for each platform or just build an HTML/javascript solution that works fine on all platforms.

The decision to use HTML/JS is easy for most teams - you have a single code base, you are working against a tight budget, you have hardly enough time to develop for one platform, you have to develop a website anyway to handle the fringe mobile platforms or to provide ubiquitous access, the team may have expertise only on a few platforms & you can create quick prototypes to impress the investors or execs etc. The rich ecosystem around tools & open source libraries also helps with the choice.

Ionic has emerged as the leading platform for building applications for mobile platforms using HTML/JS technologies. It leverages angular JS & Cordova to offer the promise of build once and deploy everywhere.  But, there is always a catch, right?  The HTML/JS applications are indeed an excellent choice for certain types of applications, so there is no single correct answer to the question about the technology choices.

But, you might have to consider a native application, if you are building a solution:
  1. that takes advantage of the unique features of the platform.
  2. that showcases best-in-class interaction & animation
  3. provides the native look and feel
  4. and prefer to avoid cross-language debugging problems
  5. on platforms where the browser technologies may not be available. eg. watchOS
  6. that needs to be future-proof (exist beyond the time that ionic/react native may survive)
Please note that there are existing alternatives to most of the above except for #4 & #5. You can take advantage of unique features by writing cordova plugins that work on each platform.  But, now you need to have in-house skills in each of the supported platform, maintain it & debug it when there are new platform releases. 

There are hybrid solutions like Xamarin & React Native that lets you build a native UI by using a single code base in C# or JS respectively. React Native provides some excellent features, but is supported only on iOS & Android, with some upcoming efforts to support platforms like OS X. This does give you #3, but #1 & #2 still requires custom plugins which again introduces similar problems as cordova plugins.

You could also consider other options like NativeScript, Titanium, Java2ObjC, Flutter etc for cross platform development. Flutter is unique because it uses Skia to render components without leveraging any native components. Java2ObjC depends on writing model code in one language & then automatically converting it to another to help write custom UI and re-use model code. Golang, Lua, Haxe, OpenGL etc are also other less popular options for partially developing cross-platform functionalities.

The native toolset & libraries have independently matured for each platform that helps you kickstart you project quicker than ever before. The cocoapods libraries in iOS is just an example of how easy it is to integrate with several high quality open source components. There are tools that let you build a complete UI without code via storyboards. The Android IDE lets you auto-generate several common UI patterns.

Personally, I have been a proponent of HTML/JS in the early days of mobile development, but I have also been through the stages where you pull your hair to just create a screen that is "native" LAF with buttery smooth interactions. This was before the days of Ionic, but I believe it hasn't changed a lot if you need to build custom components even though it is definitely possible. The application at the end felt just good enough,  because most of the time was spent making the app look like "native". 

So, please review the above requirements & potential issues before you make the final decision. The good news is that you can make both options work in most applications due to the hybrid options & plugins available. It is the amount of time & hardship that maybe different.




Comments

Post a Comment

Popular posts from this blog

Google Appengine

It was good while it lasted, Google AppEngine gave developers an easy way to create web applications without worrying about scaling it or being a sysadmin. There were numerous startups that built their products on Google Appengine. Even after beta, there was a fairly large free quota that made it a reasonable choice. But, the current pricing seems a bit ridiculous for those who are looking for a free or cheap solution or for those enjoyed the initial quotas. Perhaps, we were spoiled and Google’s goal is to get rid of free-riders which is not exactly evil from Google’s perspective. So, it is 2012 and welcome to reality since Google can’t maintain those quotas forever and the current free quotas are intended to only test your application before you go live. If for some strange reason, your application becomes popular and gets more than 1,000 users, you would end up scrambling for an alternate solution since you will find yourself paying through the nose. The quota system is complica...
Read more

Blackberry Playbook

RIM introduced the "Playbook" tablet computer with much fanfare yesterday.It relies on Flash & HTML5 as the key development platforms. RIM was able to build the compatibility for existing apps on top of QNX which is good. It was smart to rely on the HTML5 platform given the poor UI capabilities in the existing Java framework, it wasn't clear if the tablet supported native game development despite the support for OpenGL in QNX platform. The specs are great compared to the existing iPad, RIM did need some +ve hype at this point after the Torch fiasco. It is just 10mm thick compared to 13.4mm for the iPad and I thought iPad was thin. It has a 7" screen, but the resolution is 1024x600 whereas it is 1024x768 for the 9.7" iPad. Playbook also comes with a dual core 1GHZ processor compared to the single core CPU in iPad. Playbook also comes with front and back cameras and HD display with HDMI output compared with none for iPad. It also tethers with the Blackberr...
Read more

What is up with RIM?

RIM is one of the leading technology companies in Canada and one of the largest employers in Waterloo. There are a few strategic mistakes that seem obvious in hindsight, but it is easier to list them now than to predict in advance. RIM is losing market share in North America, but surprisingly the execs were focusing on developing markets for growth. Obviously, profit margins from developing countries are minimal when compared to the lucrative NA market. RIM’s strength is in the enterprise market. The primary growth is happening in consumer market, but RIM has had trouble gaining traction there. RIM will continue to rule the enterprise for now, because changes come at a slow pace there. Still, the consumerization of IT is the biggest threat for RIM in this area. The current instability doesn't help them advance in enterprise either. RIM is losing the high end smart phone market which is ruled by Apple and Android devices, but instead is happy with the wins in mid-low end ...
Read more