Titanium best practices
- Stable – applications must be stable when published and available to the market.
- Rapid – applications must be rapid to develop, maintain, and update.
- Performant – applications must perform optimally, approaching 1:1 native speed on targeted devices.
- Readable – applications must have a readable codebase for quick understanding, modification, and improvement.
Does best-practice really mean only-practice?
In the general sense, no. However, the contents of this guide are distilled from the experience and practices of Appcelerator's Professional Services engineers with input from the Engineering department, Developer Relations team, Training department, and of course our many supportive customers.
In this section, we'll lay our cards on the table and describe what we've come to believe is the best way to build a Titanium applications. (There's good stuff in the other chapters. So at least circle back to them when you're done here.)
This is a big enough topic that we'll give it its very own section. Learn how to write and use CommonJS modules here.
In this topic, we'll share techniques for implementing large-scale Titanium apps as well as techniques for separating presentation and content (and business logic).
In this section, we'll share some wisdom about how to handle images, including caching remote images, loading and unloading to minimize memory usage, and optimizing images with tools like pngcrush.
In this section, we'll cover techniques for maximizing performance, handling app updates, and accounting for platform differences.
In this section, we'll examine the Appcelerator preferences for coding style, including naming conventions, code formatting, and commenting. We'll also cover our recommendations for organizing the assets that comprise your project.