Summary

If you should take one piece of information from this chapter, I would hope that it is this:

"Organize your Titanium code into manageable chunks along functional boundaries"

You will get into a horrible mess at some point in the future if your app's initial design is poor. Having to re-factor thousands of lines of code when you need to release a version of your previously iPhone only app for an Android tablet is no one's idea of fun. Remember that Titanium allows you to create apps for a wide range of devices on differing platforms that may affect your layouts and require platform-specific code. It doesn't matter if you use Alloy, MVC, Coffeescript, Kranium, or anything new that comes along, just be clear with your design and code separation. You can thank me for the advice later.

The chapter first introduced the Ti.include command for merging content from multiple files before going on to discuss the more modular require and commonJS framework.

Later in the chapter, the concept of MVC...