APIStrat 2016 | How to be a courteous guest: providing SDKs to developers (Devin Sevilla)

B9b8a2b543b485604fc7cccf380d11bc?s=47 API Strategy & Practice Conference
November 03, 2016
Technology
2
85

APIStrat 2016 | How to be a courteous guest: providing SDKs to developers (Devin Sevilla)

Mobile developers are suspicious of including SDKs in their applications. Mobile devices are resource constrained and each application must be a good citizen. It''s easy for SDKs to cause crashes or simply use too many resources, leading to one-star reviews. SDK providers must earn trust and do what they can to protect it. This talk introduces methods to earn the trust of developers and how to manage the fallout from the inevitable bug in your SDK.

B9b8a2b543b485604fc7cccf380d11bc?s=128

API Strategy & Practice Conference

November 03, 2016
Tweet

More Decks by API Strategy & Practice Conference

See All by API Strategy & Practice Conference
B9b8a2b543b485604fc7cccf380d11bc?s=48 apistrat
12
250
B9b8a2b543b485604fc7cccf380d11bc?s=48 apistrat
5
190
B9b8a2b543b485604fc7cccf380d11bc?s=48 apistrat
2
150
B9b8a2b543b485604fc7cccf380d11bc?s=48 apistrat
1
150
B9b8a2b543b485604fc7cccf380d11bc?s=48 apistrat
1
110
B9b8a2b543b485604fc7cccf380d11bc?s=48 apistrat
0
61
B9b8a2b543b485604fc7cccf380d11bc?s=48 apistrat
2
250
B9b8a2b543b485604fc7cccf380d11bc?s=48 apistrat
0
99
B9b8a2b543b485604fc7cccf380d11bc?s=48 apistrat
0
100

Other Decks in Technology

See All in Technology
9e7a653ed313b3da4b263a772bfc5026?s=48 clustervr
0
190
42ba906dc35ef460ffcb1b7c3307ef45?s=48 spring_raining
0
1.1k
C5e26822fb2aa64410b50eac63ef7d84?s=48 fill9120
0
210
C636093440dd4a8be6416e83cb980979?s=48 iselegant
13
2.7k
0479057e04d0dbef40692b5f171f60e4?s=48 takanakahiko
0
510
2ca9e6e68b43a796a8add2bcb9bbad2e?s=48 mizutani
0
290
2011382f0f10050fbb5f08e80e2bd125?s=48 akuwano
0
130
74cec195bfb6cb5165256d88cb7fcf0f?s=48 miu_crescent
2
260
Ae03eb47606f4e0125268d39f8aebfad?s=48 ymmt2005
2
1.2k
953fe5f1a04d8944ead78db3991cfa6a?s=48 anoriqq
0
220
E91a24de5f8858932171b35bd47c8485?s=48 rueian
0
240
2ec42cd8400b1e8e5ba125936c1d27e9?s=48 smiyaza
0
200

Featured

See All Featured
8081b26e05bb4354f7d65ffc34cbbd67?s=48 chriscoyier
775
240k
1b75d89772b7eea1f6c89fbf362607d9?s=48 moore
125
21k
4262b9cfacfb6b2c77f23e1d0310cd3e?s=48 myddelton
106
11k
F57e2136eb9895eb95ff5dc8a1c02677?s=48 zakiwarfel
87
3.2k
56c4053438af8e8b90d6f53cbb7573be?s=48 jakevdp
770
190k
245cee81a9c424266e5e401d844ea881?s=48 lara
13
2.4k
B6a8f005f39d23ffc930508ac9da68b9?s=48 vanstee
115
4.7k
5f83ef806155b403c3393160ce51f955?s=48 jlugia
216
16k
7653c7c449918ff6542880a8c284f5e7?s=48 jponch
101
4.8k
20bfe76b3d6105641f879fe45cfc9272?s=48 bkeepers
319
53k
7edec06b5435e0dac07a353b2cc26253?s=48 geeforr
331
29k
9128d500301ae51524e887bb680f471d?s=48 caitiem20
305
17k

Transcript

  1. How to be a courteous guest Providing mobile SDKs Devin

    Sevilla APIStrat Boston 2016

  2. Previously — Engineering Manager, API Currently — Partner API Technical

    Program Manager Credentials

  3. • iOS & Android SDKs • Partners ◦ Shazam ◦

    SoundHound ◦ SoundTracking ◦ Billboard Music Awards ◦ Various music festivals Rdio Developer Program

  4. Will you get invited?

  5. • Provide complete documentation • Share your roadmap • Share

    known issues, limitations Build trust with no surprises

  6. • Closed source feels like less control • They won’t

    look at the source, but it’s nice to know it’s there • Alternative — open source SDK that depends on a minimal closed source library Consider an Open Source SDK

  7. Easy to get started (make it easy to invite you)

    • Dependency management is easier than ever ◦ Maven Central Repository (Android) ◦ CocoaPods (iOS) • Provide a tutorial with how to install and configure

  8. You’re invited! Now what?

  9. • OS and framework versions (deployment target) • External dependencies

    • Permissions • Don’t expect to use the latest features • Expect to drop support for old versions until the last moment Permissions and Versions (Dress code)

  10. Be efficient (Don't eat the whole deli tray) • Battery

    — Don’t keep GPS, radios on • Network — Don’t use too much data • Package size — Keep downloads small

  11. Share resources (Be nice to the other guests) • Let

    them know you're going to take control or release shared resources • Let them say yes or no (the app might already have control)

  12. You spilled a glass of wine

  13. Have a release and support process • Do your partners

    know how to report issues? Do they know what to include in a report? • How quickly can you build, test, and deploy a bug fix? • Make it easy to talk to a human • Provide frequent updates, even if it isn’t fixed yet

  14. Logs • Log enough detail to help you diagnose •

    Don’t leak user information • Log what you’re doing, not the data you’re using

  15. Debug Builds • Your release process should include debug builds

    • Log additional steps and the data you’re using • Use an API proxy for detailed HTTP request logging

  16. Recap

  17. ❏ Document your roadmap, known issues ❏ Consider an open

    source SDK ❏ Host your SDK in a public package repository ❏ Create a tutorial to ease getting started ❏ Implement callbacks for shared resources ❏ Also build a debug version of your SDK Actions

  18. Devin Sevilla • devin.sevilla@adroll.com • devinsevilla.com • @devin_s