Slide deck from my Dreamforce 2013 mobile theatre session demonstrating a couple of complementary applications - a ticketing app to download tickets to a device and present a QR code and a driver app to scan and verify the code and consume the ticket in Salesforce.

1. Ticket to ride
Keir Bowden, BrightGen, CTO
@bob_buzzard

2. About me
 CTO of BrightGen
 5 years Force.com
 Force.com MVP
 Enterprise Java background

3. When mobile web apps aren’t enough
You need access to device features but don’t want to learn a
new programming language per platform
Here’s how to leverage your existing web skills using the
Salesforce Mobile SDK ...

4. Tickets app flow
1. Download Tickets
1. Download Tickets
2. Store Offline
2. Store Offline
3. Present Code
3. Present Code

5. Driver app flow
1. Sign in to service
1. Sign in to service
4. Consume ticket
4. Consume ticket
2. Touch to scan
2. Touch to scan
3. Scan code and validate
3. Scan code and validate

6. Mobile options

7. Tickets app
Hybrid
Hybrid
Application
Application
iOS
iOS
V 1.3
V 1.3
REST
REST
Toolkit
Toolkit
Smart
Smart
Store
Store

8. Driver app
Hybrid
Hybrid
Application
Application
iOS
iOS
V 1.3
V 1.3
REST
REST
Toolkit
Toolkit
Scanner
Scanner
Plugin
Plugin

9. Demo
 Retrieving tickets and presenting a ticket code
 Scanning and verifying the ticket
 A look at the code:
•
Store.js - Smartstore integration
•
Tickets.js – interface between store and UI
•
Scan.js – Scanner integration

10. Lesson 1: Storyboard the application
 Especially single page applications!
 Map pages to functionality

11. Lesson 2: Professional JavaScript
 Avoid anonymous functions
 Use your own namespace
 Don’t tie behaviour to content

12. Lesson 3: Use the discussion boards
 You aren’t the first
 Leverage the community
 Access the SDK developers

13. Lesson 4: Terminology
 Cordova ≈ Linux
 Phonegap ≈ RedHat
 Used interchangeably

14. Keir Bowden
CTO, BrightGen
@bob_buzzard