15. Constraints === Focus
• Know your demographic
• Choose your target platforms
• ...?
• Profit!
16. DOM concerns
• What does your target browser support?
• Offline capable? storage / cache manifest
17. Backend Arch
• RESTful JSON
• favor parse to eval btw
• Use local storage or device api for file i/o
to cache data as much as possible
• Update apps through the various stores
19. Native Apps
Apple iPhone OS .............................. Obj C
RIM Blackberry ................................. Java
Google Android ................................ Java
Symbian / Maemo (Nokia) ............. *
Palm webOS ..................................... Web
Windows Mobile ............................. .NET
47. Ghetto, actually
• DOM Storage is key/value only. Slightly
nicer than cookies but way lamer name.
• SQLite seems like a bad idea: schemas,
migrations, impedance mismatch, oh my.
50. Lawnchair quickly
• JSON document store (not key/value)
• Designed for mobile; very light
• Clean and simple async oo api
• Adaptor pattern for store customization
52. Lawnchair Futures
• 1.0 is REAL SOON I FUCKING PROMISE
• Adaptors abstracted into a RequireJS build
• Some actual benchmarks
• PhoneGap File I/O adaptor
53. Closing rant
• App stores are sanitized and walled
gardens. The content is dictated.
• 30% for the ability to sell is corporate
greed at its worst.
• Requiring provisioning to build code on a
device you own is unethical.
• This should not be tolerated by
developers: speak out!