Native Cross platform development means using tools to maintain ONE CODEBASE and produce NATIVE applications for Windows™, Mac OS/X™, iOS™ iPhones/iPads and Android™ devices, entailing that you maintain only ONE software, you correct bugs and add features in ONE PLACE only, avoiding confusion and adding new bugs depending on which platform the team is working on.
This way, when a feature is added to the Windows™ version, it’s automatically propagated to the Mac OS/X™ version, as well as the Android™ and the iPhone™/iPad™ versions.
How cool is that?
Also, being native, you don’t get a subset of interpreted software like Java or .NET with poor performances*.
We use Embarcadero Rad Studio compilers (Delphi/C++Builder) to achieve such a thing. Examples can be found below.
*Even better for Android as the app is compiled down to the processor, skipping Java crawling performances
This application processes data collected from geomagnetic devices disseminated across the world.
The cross platform design adds the ability to take the data with you to the field, without putting expensive and heavy laptops at risk, exposing them to dust, scratches, rain, natural hazards.
The end-user is immediately operational since the application's look and behavior are similar to the full desktop application she is used to.
Click the thumbnail to show the application in 4 different platforms.
SJMovieDB is a good example of cross platform development.
This is a DVD movie database. The user can conveniently use the desktop application to enter the data and then take that valuable information with her in a portable tablet like the iPad or an Android GalaxyTab.
The same information is available, not a subset.
Also, the screen real-estate can be automatically managed between portrait and landscape modes, hiding navigation/section controls in a side-drawer that slides in and out in portrait rather than covering the interface, leaving the screen display most of the information.