2 Answers

• Desktop and mobile apps are quite different in how the user interface pieces work. In addition, user interface pieces aren't 100% compatible between the different mobile platforms, either. There are many pieces of code that work great on iPhone but crash Android.

  That said, here's a good strategy:

  Separate your code into UI (display logic), Business Logic, and Data Logic. Business Logic and Data Logic should be reusable for all platforms. Just include these files inside both your desktop and mobile projects.

  For the UI code, you'll either want separate files for each platform (iPhone, Android, iPad) or write separate blocks of code like this:

  if (Ti.Platform.osname == "android")
     { android_code_block }
  else if (Ti.Platform.osname == "iphone")
     { iphone_code_block }
  else
     { ipad_code_block }
  

  How much of your code is reusable? It depends on your project. A project that has a lot of heavy back-end processes, lots of database access and logic, etc. will have more portable code. A project that's mostly front-end stuff, like a game with a lot of moving parts will probably require more platform-specific code.

  Note: Until the documentation is more complete here, figuring out what works on Android and what doesn't is pretty much trial-and-error. It's time-consuming and frustrating. But it beats learning the Android SDK and starting from scratch – probably by an order of magnitude.

• We are working to address the Android deficiencies. If you do find crashes, please let us know.