View Single Post
daperl's Avatar
Posts: 2,427 | Thanked: 2,986 times | Joined on Dec 2007
#44
Originally Posted by twoboxen View Post
You guess incorrectly. Though you can kinda leverage JNI to use native code in an Android app (my Android apps use it, since I wrote the core engine in c... to make it work well with the iPhone, Qt, etc), most people don't, because it's a pain. Nearly all of the Android apps are 100% Java. So basically, you have to re-implement almost everything, and that isn't even considering the OS API differences--merely your logic.
If you continue with this attitude, and you're a decent software developer, you'll leave easy money on the table. Some of the good software houses are supporting 5 mobile OS's; the minimum is 2. Go the extra mile and continue to abstract your solutions. Take what's yours. If you can't handle the reality that there's more than one OS out there, you might want to move aside before you get flattened. Java, iPhone OS, Symbian, and anything GNU/Linux based, all have solid underpinnings (and some shared [OpenGL ES]), and it seems they all will be here for a while.

Porting is fun. If you don't feel that way, you might be in the wrong arena. Regardless of what you think about the U.S. Military, one of the Marine Corps' mantras applies here:

"Improvise, Adapt and Overcome"
__________________
N9: Go white or go home
 

The Following 3 Users Say Thank You to daperl For This Useful Post: