Future of mobile development

It took me a while to converge to a decision regarding what cross platform mobile development platform I should commit myself to (at least in the foreseeable future). After considering the various frameworks, I came to the understanding that MoSync is the winner for me. The reasons are that MoSync best matches my view on where mobile development technology should be going:

  • It provides the ability to quickly develop web or native UI for a mobile application using HTML5 and get immediate feedback on the mobile device when changing the UI code on the development platform.
  • It provides a C++ abstraction layer for running native code on all the major mobile device operating systems.
  • It provides a bridge (called wormhole) to effectively pass bidirectional events between the HTML5/JavaScript world and the C++ world.

This struck a chord with me as this was the exact philosophy I had in mind when developing JNEXT, which enables smoothly combining demanding CPU and native resource tasks with demanding UI tasks while using the appropriate technology for each.

As a note regarding the longer-term future of mobile development, my guess is that what is going to happen is that native mobile APIs (using Objective C for iPhone, Java for Android, C# for Windows Phone etc.) will become as interesting to future mobile application developers as assembly language is for todays application developers. There will be just too many interesting apps to create and distribute to be bothered with wasting time learning the specifics of any particular “CPU”.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.