The document advocates for developing mobile-first applications using native development to access device hardware and provide a high-quality user experience. It discusses how mobile usage now dominates over desktop, and that native apps have advantages over mobile web apps in terms of performance, access to device features, and security. The document also presents options for developing across iOS and Android platforms, and introduces the Appcelerator Titanium framework for building native mobile apps using JavaScript.

1. Mobile first, mobile right
TIM POULSEN
Software Engineer, Tooling Team
@skypanther

2. Goal: Convince you to develop
Mobile First
Multiplatform
Native
With computing in the right place

3. MOBILE FIRST
Online activity:
60% mobile : 40% desktop
Mobile app usage up 53% since 2013
(desktop use up by 1%)
85% time spent in apps, not the browser
Go Mobile!

4. THE OBVIOUS REASONS
Access anywhere, any time
Hardware integration:
Camera, Bluetooth, NFC, etc.
Rich experiences:
Media, audio, HealthKit, HomeKit,
beacons, location detection, etc.
Life integration:
Calendar, contacts, social networks
Apple Pay, Google Wallet, Square ...
Go Mobile!

5. iOS first, or only?
Worldwide market share of ~15%
42% of US market
Generates 85% more revenue for
developers than Android
Targets premier consumers
Dominates tablet and corporate
markets
Closed ecosystem, tight controls,
restricted hardware, limited licensing

6. Android first, or only?
Worldwide market share of ~80%
52% of US market
Targets all consumers with range of
devices
Multi-user profiles, education/school
features
Open ecosystem, limited controls,
flexible hardware, broader licensing
Device variations, additional testing,
more Android versions

7. Both, at the same time
Broadest reach
Highest revenue opportunities
Highest cost
Efficient development & testing
required
Tailored interfaces
More design, testing, cost

8. WEB APPS & MOBILE-OPTIMIZED SITES
Great for occasional / one-time access
Not easy to replicate native UI/UX
Performance is typically poor
Network connectivity typically required
Few options for meaningful local data
storage
Limited access to device hardware
Limited security
Go Native
As much as possible, it’s a good idea to use the standard UI elements that UIKit provides.
- iOS Human Interface Guidelines

9. NATIVE APPS
Native UX/UI components
Access to device’s hardware
Access to OS-specific components
Greater security
Better performance
Go Native

10. Processing in the right place
Data Data Data

11. Demo

12. Demo
http://goo.gl/29lShl  “raw” API output from NYS LB
http://goo.gl/ptyViU  “filtered” API from NodeACS

13. Native apps using JavaScript
iOS, Android, Blackberry, and Windows
Mobile
Alloy MVC framework
Appcelerator Cloud Services
NodeACS
Appcelerator Titanium

14. Titanium Open Source

15. 600K developers in 185 countries
250M devices running Titanium apps
500+ add-on modules in our Marketplace
http://gitt.io – search & install
800+ modules and 300+ UI widgets
tiConf – community operated developers
conferences
www.tidev.io – community-created news
site
TiShadow – community-created rapid
development tool
Titans – volunteer community advocates
Our Ecosystem

16. Appcelerator Enterprise Offerings
Real time analytics
Crash monitoring
Automated testing tools
Backend data connectors
API builder
Support and services

17. Apps built with Appcelerator Titanium