1.
Yaron Karasik
Mobile SDKs:
Considerations and
Best Practices
Yaron Karasik

2.
Yaron Karasik New York
Greenwell
Hi, I’m Yaron
Karasik

3.
What is a mobile
SDK?

4.
Why build a native
Mobile SDK?

5.
Offer a mobile
specific service
Make existing service
or API easily usable

6.
App developers are a
well defined target
market and business
model

7.
What do we need to
consider when
building a SDK?

8.
How much time do
you have to hook
the developer?

9.
What’s the easiest way
for a developer to solve
an SDK related issue?

10.
Your SDK is a guest
in its host app
Creative Commons Image: Liz Mc
https://www.flickr.com/photos/11638547@N00/3827808607

11.
Minimum use
of resources
Easy to integrate
and use
Maximum
compatibility
Provide your
own UI?

12.
Users know
what the app is
doing

13.
Users know
what the app is
doing

14.
Yaron Karasik
Don’t kill the
battery

15.
Yaron Karasik
Be thrifty with
cellular data

16.
Not real time?
Batch requests

17.
Real time? Use mobile
optimized transport and
API

18.
Polling
Long Polling
SSE
Websockets

19.
Keep your payloads
as small as possible

20.
Memory - Allocations & Leaks

21.
Performance

22.
Instruments

23.
Automated Build
Process and Testing
Don’t crash the host
app

24.
Never ask the user
for permissions..

25.
..but definitely use them if
permission has been given
Class $CLLocationManager =
NSClassFromString(@"CLLocationManager");
if ([CLLocationManager authorizationStatus] != kCLAuthorizationStatusDenied) {!
..!
}!

26.
Location
Services
Twitter
Facebook
Address
Book
Photos
Camera
Notifications
Microphone
Calendars
Bluetooth

27.
Again, users
know what the
app is doing..

28.
Notifications
Push requires
server side support
and developer trust

29.
Notifications
Local is very useful
if already enabled
by developer

30.
App Size

31.
Local Storage & Security
• Don’t use local storage it you don’t have to
• If you do, take good care of app data
• Encrypt sensitive information
• Purge it when you’re done
• Use SSL for all networking

32.
Should I use open
source code in an SDK?

33.
OS Version Compatibility

34.
Architecture Compatibility

35.
When will the
developer upgrade
the SDK?

36.
Much later than
you’d like
So design your APIs
for the long run

37.
Make it easy to
integrate and use

38.
Instant onboarding
Free tier (or trial)

39.
Interactive docs are cool

40.
Indicate successful integration

41.
Use CocoaPods..
platform :ios, '7.0'!
!
pod 'AFNetworking', '~> 2.1'!
pod 'Reachability'!
pod 'LivePerson', '~> 1.5.448'!
pod 'SocketRocket', '= 0.3.1-beta2'

42.
..or a minimum integration flow
1. Add required frameworks
2. Add SDK

43.
Simple SDK Launch
[[SDKManager shared] initWithAppId:@“XYZ-ABC”];

44.
Developer Logs
EcoTest[2051:66030] [LPMobile//info]
Loaded. #ios #info!
!
EcoTest[2051:66030] [LPMobile//
warning] The server has reported an
error with your app. This may be
caused by a bad configuration - Please
contact mobile@liveperson.com for
assistance. #ios #warning

45.
Smart callbacks
and event reporting
Notifications
BlocksDelegates

46.
Configuration -
Server or Client side?

47.
Help the developer
keep the SDK updated
Cocoapods + Github

48.
Should your SDK
include UI?

49.
Provide UI friendly
API, allow developer
to use their own UI
Plan A

50.
Provide a view
controller for the
developer to present
Plan B

51.
Implement your own
UI, automatically
integrate with host
Plan C

52.
Maintain App
Context

53.
Custom Branding

54.
Device and orientation
support

55.
OS Version Compatibility

56.
What about assets?
• Use flat design when you can
• PNG crush required assets
• Consider downloading and caching
• Download bundle on first launch

57.
Memory
Networking
Documentation
UI
Devices
OS Versions
Battery
Permissions
Security
Storage
App Size
Performance
Summary

58.
Thank You!
We are hiring

59.
YouTube.com/LivePersonDev3
Twi5er.com/LivePersonDev3
Facebook.com/LivePersonDev3
Slideshare.net/LivePersonDev3