Close

Native UI - continued

Published by romachal, April 15, 2010 Filed in

 

As promised, here is my second blog post about native UIs.

After some work and wandering in the Android and Apple documentation, I am glad to announce new prototypes for Android and iPhone, next to the Windows Mobile one. 

In order to do that, some code has been added to the specific MoSync runtimes, mainly IOCtls (see Developping MoSync -> Writing extensions to MoSync) and a cross-platform MoSync library deals with calling the appropriate code for each platform.

A prototype for designing UIs declaratively through XML is also available.

Events are handled in the 'Java-style' by adding action listeners to the widgets; an event dispatcher is responsible for… dispatching (!) the events to the appropriate widgets.

One of the benefits is that learning all the device-specific tricks (yes, i mean Android's 'activities' and Objective-C for iPhone...) will no longer be needed for the one who wishes to design a native UI, provided he is a cool guy that uses MoSync ;)

 

Trackback URL for this post:

http://www.mosync.com/trackback/4634

GUI Fragmentation Issues on Smartphones

How does MoSync solution address user interface fragmentation issues? I have mentioned some smartphones related GUI specific fragmentation issues on my blog: http://mobtive.com/?p=4.  Your comments are highly appreciated.

The native UI approach

The native UI approach is what you would call a Device-Centric-Adaptive approach I guess, as it adapts the widgets to the native API... I personally think that application-centric approaches do not solve the fragmentation problem, and the same goes for device-centric approaches, so a compromise seems to be a good alternative.