These are the slides of the EventList talk I gave at IBM Research Labs during the dojo.workshop. The talk was covering possible architectures for cross device mobile solutions.
11. The idea
• upcoming, eventbrite, ...
• finding all web dev events on one page?
• YES: HTML, CSS, JS
• NO: Objective C, Java, other proprietary stuff
• AND: we are lazy ... fastest way from idea to
result? mobile devices and normal websites???
Nikolai Onken - @uxebu, @nonken
18. Use the cloud - again
Nikolai Onken - @uxebu, @nonken
19. for your JS/CSS/Images (CDN)
Be careful though - mobile apps need custom builds for deploy
Nikolai Onken - @uxebu, @nonken
20. What could be a good architecture?
• Something similar to the MVC pattern
• Tiny base (especially for mobile)
• Extra functionality through plugins
• Styling via CSS
• Platform specific design via templates (DTL)
=
Multiple Platforms
Nikolai Onken - @uxebu, @nonken
31. Build platform/device specific
• CSS Transitions (Webkit)
• Device API support (geolocation, etc.)
• Custom builds (Deliver in chunks, small initial
hit)
Nikolai Onken - @uxebu, @nonken
36. Automate
Set up deployment processes for all platforms you
want to support (sh is your friend)
Nikolai Onken - @uxebu, @nonken
37. How do I test?
• Debugging tools on mobile devices suck (most)
• http://www.opera.com/dragonfly
• Uhh, the screen is so tiny (firebug lite?)
• phone specific deploy process takes ages (e.g.
iPhone)
Nikolai Onken - @uxebu, @nonken
38. Some tips
• Always test your app before you build the JS
• Always test the built JS in a normal browser
• e.g. iPhone: test in Webkit
• e.g. iPhone, test on the iPhone browser before you
compile your native app
• e.g. S60: test in Opera
• Always do this
• Really!
Nikolai Onken - @uxebu, @nonken
39. Simulators are not devices,
unfortunately
Do you have a phone for me?
....Start collecting phones,
optimize for the lowest common denominator
Nikolai Onken - @uxebu, @nonken
40. And once you have found the solution
Share your knowledge
Nikolai Onken - @uxebu, @nonken