Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>First thing I would do it just try it in the Android emulator. Does it work? Titanium will map UI elements to the target platforms functionality so it might just work, though it will look different. Each platform has their different ways of displaying information on the screen.</p> <p>Titanium Mobile is a write once, adapt everywhere model. So you write the main functionality for the app and then adapt the UI to the platform. You can generally reuse a large portion of your back-end management code for the device if you structured it properly. In my situation, I'm writing a reasonable large application and I can reuse all my networking code and database interaction code. The way you setup a project allows you to substitute platform specific files where needed in a platform specific folder. For example, if your form1.js doesn't work on Android, but works in iPhone, you place the form1.js file that works into the Android folder matching the folder structure and it will pull the file from there during compilation, but continue to use the database.js file for the data store from the common code.</p> <p>A good example of some cross-platform code is the <strong>RSS Reader</strong> sample code you can get through the IDE (lower left panel in the IDE). You may figure out the minor changes you need to make to get your app working on Android from that. I also like the <strong>Tweetanium</strong> app source code, because it is a larger project and has similar cross-platform effort for making the app look similar on both OSes. </p> <p>Also, do a search for Titanium Mobile Titans for the <strong>'App'</strong> source code. Actually here is the link: <a href="https://github.com/appcelerator-titans/App" rel="nofollow">https://github.com/appcelerator-titans/App</a>. This is an example of a cross-platform interface taking in the considerations for the UI.</p> <p>I believe all of these examples have tablet (iPad/Android) detection code as well, so you can see how the code branches for those screen sizes.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload