This document discusses lessons learned from apps that performed better than Titanium apps in terms of cross-platform concerns, memory management, slow initialization times, multiple contexts, and code structure. It provides solutions for each problem area, such as not aiming for 100% code reuse across platforms, planning for platform differences, closing windows and nulling references to help Titanium cleanup memory, deferring script loading, avoiding multiple contexts, and building a suite of custom components for code structure. The document concludes with a demo and code walkthrough.

1. Lessons Learned from apps that kicked Titanium’s ass Kevin Whinnery @kevinwhinnery

2. Agenda Some Cool Titanium Applications Problems we saw (and how we fixed them) Titanium application structure: CommonJS modules and Custom Components Demo and code walkthrough Q&A

3. Some Cool Titanium Applications NBC iPad Application Late Night with Jimmy Fallon GetGlue Wunderlist Many many more

4. Awesome! …but they also kicked our ass…

5. Big Apps, Big Problems Cross-platform concerns Memory Management Slow initialization times Multiple Contexts Code Structure

6. Cross-Platform Concerns “Write Once, Run Everywhere” fallacy Cross-Platform API Parity Cross-Platform functional differences

7. Solutions Cross-Platform Concerns

8. “WORE” Fallacy Don’t aim for 100% code re-use, because it’s not going to happen (not even on the web) For many apps, you can get by with branching logic For complex experiences, re-use components, not your entire set of UI code Custom components offer the best cross-platform re-use If your app is made up of small chunks, each chunk will be easier to maintain cross-platform

9. Cross-Platform Parity/Compatibility Probably the most annoying thing about our platform - We’re writing specs to drive testing/implementation for 2.0 - First spec implementation will be with layouts in 1.8 Cross-platform testing essential Should plan on platform differences, however – check NavigationController demo for one example

10. Memory Management No explicit memory management API Lots of views (images especially) === lots of memory Unsure when Titanium cleans up

11. Solutions Memory Management

12. How to make Titanium clean up Close windows Set object references to null Don’t keep “fat” views in the view hierarchy (images)

13. Slow initial load times App loads up too slowly Windows open too slowly (windows with URLs)

14. Solutions Slow load times

15. Dealing with slow load times JavaScript evaluation is the slowest part of your application Defer script loading until absolutely necessary Don’t load the same script over and over again in a context

16. Multiple Contexts Kitchen Sink model Data sharing is hard When was code run?

17. Solutions Multiple contexts

18. Dealing with multiple contexts Don’t Custom events Properties API for data transfer

19. Code Structure app.js – not very much structure folder structure? MVC? MVVM?

20. Solutions Code Structure

21. Code structure Many ways to skin that cat Appcelerator will have a more formal solution soon Your best bet is to build a suite of components Demo/Code Walkthrough

22. Q&A Questions and Answers

23. Contact Kevin Whinnery @kevinwhinnery kevin.whinnery@gmail.com

24. Thank you!