61. Everything else?
• HTML for layout
• JavaScript for accessing device APIs
• CSS for look & feel
• Offline storage for standalone clients
• Ajax, JSONP for syncing to the cloud
– Runs on file:// protocol which is exempt from same-origin
policy
• Just use Sencha Touch!
64. Tools
• Browsers – Safari the best (unfortunately)
• Web Inspector
• RemoteJS (Android debugging)
• Souders’ bookmarklets
– stevesouders.com/mobileperf
• Jdrop
– jdrop.org
65. Object-oriented
• Use namespaces to define your library
• Define components – code for reusability
• Extend first, write plugins second (not at all
if possible)
66. Events rock!
• Use events to communicate between
components
• Use event delegation
67. Override appropriately
• Do not edit the library files
• DO NOT EDIT THE LIBRARY FILES!
• Use an overrides file if you need to override
the framework
• Do the same with CSS (but you should be
using cls, ui properties)
68. Define a directory structure
• Break your code into small files
• Use build tools to compile for performance
• Use sencha-touch-debug.js during dev (but
never prod!)
• Keep the framework up-to-date – upgrade as
often as you can
69. Worry about performance
• Understand client-side performance rules &
use them
• Latency bad
• JIT compilers – compilation time relates to
size of file the method exists in
• Keep DOM light
• Destroy components that aren’t visible
• concatenate, minify, compress!
70. Theming/Layouts
• Use SCSS
• Remove unnecessary CSS by only
including required SCSS mixins
• Understand XTemplate
• Understand doComponentLayout