Your SlideShare is downloading. ×
0
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Mobile APIs
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Mobile APIs

509

Published on

Apistrat Amsterdam 2014 talk on mobile clients and their api needs.

Apistrat Amsterdam 2014 talk on mobile clients and their api needs.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
509
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
9
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Mobile APIs @MicheleTitolo
  • 2. Mobile
  • 3. Needs • Fast • Full-Featured • Flexible
  • 4. Fast
  • 5. 300ms
  • 6. Less API calls
  • 7. REST might not be the best
  • 8. Update multiple objects
  • 9. Failure
  • 10. Sync
  • 11. 3rd Party APIs...
  • 12. ...should be used by the server
  • 13. Full Featured
  • 14. “Can we ...”
  • 15. If you build it, it will get used
  • 16. Apps are fully functional
  • 17. “The website does X”
  • 18. Flexible
  • 19. Products change over time
  • 20. App functionality will change
  • 21. Reacting quickly saves time
  • 22. Optimize later
  • 23. Version APIs based on payload
  • 24. Non-breaking changes
  • 25. APIs for User Experience
  • 26. 1 Screen, 1 API call
  • 27. 1 Save, 1 API call
  • 28. Cascading is bad
  • 29. Different clients, different needs
  • 30. Thanks! @MicheleTitolo

×