1. Daniel Burke - Mobile Development Manager, Lead Native SE
Research Analytics
Software
Built web apps for
Google, Red Bull,
Burberry
Several apps in the App
Store, featured by
Wired.com

2. Why You Should Have
A Native Strategy
Experience is key to Customer Lifetime Value

3. 180M iOS & Android Devices
Setting The Stage - U.S. Mobile Usage
COM SCORE

4. 60%
of the world
still isn’t
online
United Nations Broadband Commission

5. Mobile traffic
surpassed
desktop traffic
in 2014 at
55%2007 2008 20102009 2011 2012 20142013 2015
Setting The Stage - Usage
COM SCORE

6. 86%of the
time spent on mobile is
spent in native apps,
not the browser
CNN MONEY

7. Most of that is in about 5 apps they
use all. the. time.
88% actually

8. Ok, so what's
the problem?

9. Having a native
strategy is not
easy.

10. Why? - Difficulty
$ MULTI-PLATFORM
HIGHER SALARIES
FEES
FINDING VALUE
DISTRIBUTION
APPROVALS
TIME DELAY

11. Other Considerations - Single IDE, Single Language
Tools Needed for Web Version Tools needed for Native

12. Other Considerations - Frameworks & Hybrid
3rd Party
Dependence Learning Curve Late Feature Adoption
New

13. Other Considerations - What Am I Building
Read OnlyUtility (Features) Communication (Features) Game (Features)

14. Users want native apps for
services they use often

15. Native
Performance

16. Native Performance - Hardware Accelerated
Smoother
Animations
Custom
Transitions
Better Caching
Resources

17. “Our biggest mistake”
Mark Zuckerberg
on using HTML5 for their mobile app
(CEO of Facebook, you know, just in case)

18. ● App was sluggish and
people hated it
● Article load times are
still super slow
● FB Instant Articles for
publishing
● HTML5 App was
sluggish and people
hated it
● Article load times are
still super slow
● FB Instant Articles for
publishing

19. Native - Quality Is Important (trust me, or trust them)
Google Docs Pinterest Instagram Zillow

20. Native - Internet Favor
Google rewards websites
for having native content
Google app indexing
makes native app content
search-relevant

21. Native
Quality

22. Native - Quality Feel
Performance helps
the app “feel” good
Cater to the OS,
special nuances

23. Native - Quality Features
Motion,
Gestures
Bluetooth,
File sharing,
Communication
Camera/Video
Auto-play video
inline
Background
Processing/Updates

24. Native - Quality Features (mo)
Voice recognition &
“Assistants”
Better social
integration - sharing
and customization
Better security -
fingerprint and
biometrics
Mobile Payments

25. Quality
Enhances
Experience

26. Native - High Quality Brings Re-engagement
Geo-fencing
Use this to add
contextual value
Push Notifications
Capture communication
channel
Magic Moments
- Actionable Notification
- Swipe for a batch action

27. The “Web” Is Disappearing

28. Future - The Web is disappearing
Connected
Wearables and
Smart Devices
Many services and tasks
are being completed by
BOTs, invisible apps
Messenger Services are the
new “platform”

29. Explore With
Motion
Imaging exploring your new
neighborhood, coffee shops,
downtown - before you move.

30. Move-in Date
Phone Call Time
Floor Plans
Wearables
Being able to send
contextually relevant
responses from your watch
based on basic lead data.
“Hi Bill! Thanks
for your interest
in Belmont
Estates. When
are you looking
to move in?”

31. Cars
CarPlay integration can
take your user along a
guided customized route to
apartments that fit their
needs.
Call

32. The VALUE a business
will derive from the entire
relationship with a customer.
“Customer Lifetime Value”

33. Swift 2.0 and
XCode 7

34. Storyboards: Multi-device Support
No Extra Code

35. Storyboards: Rapid Prototyping
High-level
Project View

36. Swift: A More Approachable Language
● Less code to write, less
redundancy
● Safer to let the compiler decide
● Mutability is explicit and compiler will
warn you
● Compiler warnings help you optimize
your code when you have unchanged
objects.

37. Swift: A More Approachable Language
● Simple syntax
● Type Inference
allows
abbreviation

38. Swift: A More Approachable Language
● String literals are
more like other
languages
● Concatenation &
String templating
without format
specifiers

39. ● Performance Tuning and Memory
Consumption
● Deprecation Warnings
● Unit Testing & CICD w/ BOTs
● Device Simulation
● Swift Playgrounds (Live code)
● Swift 2.0 will be Open Sourced later
this year

40. Wrap It Up
Daniel…srsly.

41. Native Development is
about Quality Experience,
that “Magic Moment”
Plan for the
“disappearance” of the
web as you know it
Swift 2.0 makes iOS
very approachable
WHAT?

42. Users want native quality
and performance
The world is mobile Native features add value
WHY?

43. Focus on how to deliver
high quality, value-
adding apps
Build a culture around
documentation, CICD,
and testing
Recognize and celebrate
entrepreneurialism
HOW?

44. Questions?