Chapter 3. How to Design Titanium Apps

In the last chapter we created an app based on a single file. We also introduced the concept of splitting the executing path of the code to handle platform differences using the Ti.Platform.name property. This worked for the small app but would be no way to design something larger. The single file approach would get very messy and the code would get more and more complex when new platforms were added. It was a good start but what we need to do now is to lay down the proper principles of Titanium design that will enable us to create complex apps that support many devices without the code getting tied up in knots.

Towards the end of the chapter we will be touching on the very latest in Titanium design trends. This may be a step too far for a first time Titanium user. If you find it's a bit heavy, skip it; it's not a problem, you can revisit that part of the chapter at a later date.

Expect to read about the following in this chapter:

• How to pass data cleanly...