Mobile APIs
Mar. 28, 2014•0 likes•1,403 views
Download to read offline
Report
Technology
Apistrat Amsterdam 2014 talk on mobile clients and their api needs.
Michele TitoloFollow
Recommended
Mobile Services AWSMaria Villalba Rodrigo
Joe Emison - 10X Product DevelopmentServerlessConf
Public Workspaces: Massively Multiplayer API ExperiencePostman
A Connector, A Container and an API Walk into a Bar… Microservices EditionSteven Willmott
Take Control of your APIs in a Microservice Architecture3scale
Adapting iOS 8 in iOS 7 Apps Aviel Lazar
More Related Content
What's hot
Postman Visualizer - More Than Meets the EyePostman
Response Visualizations in PostmanPostman
SugarCon 2013 - Tips and Best Practices: Ten things you didnt know you could ...SugarCRM
Realm 研究ShengWen Chiou
On the shoulders of giants Learning About API Design by Looking Backwards CA API Management
Naki techDavid Clarke
Viewers also liked
Mobile APIs: Optimizing APIs for Many DevicesApigee | Google Cloud
Lo mejor y peor de React Native @ValenciaJSMarcel Kalveram
SONY BBS - React NativeMehmet Ali Bağcı
Microservice Websites (microXchg 2017)Gustaf Nilsson Kotte
A tour of React NativeTadeu Zagallo
Nuxeo & React Native Nuxeo
More from Michele Titolo
Writing Design Docs for Wide AudiencesMichele Titolo
Beam Me Up: Voyaging into Big DataMichele Titolo
APIs: The Good, The Bad, The UglyMichele Titolo
Tackling the Big, Impossible ProjectMichele Titolo
No Microservice is an IslandMichele Titolo
From iOS to Distributed SystemsMichele Titolo
Recently uploaded
Advancing Equity and Inclusion for Deaf Students in Higher Education3Play Media
Roottoo Innovation V24_CP.pdfroottooinnovation
The Ultimate Administrator’s Guide to HCL Nomad Webpanagenda
Document Understanding as Cloud APIs and Generative AI Pre-labeling Extractio...DianaGray10
web test repair.pptxYuanzhangLin
Announcing InfluxDB ClusteredInfluxData
Mobile APIs
- 1. Mobile APIs @MicheleTitolo
- 3. Mobile
- 4. Needs • Fast • Full-Featured • Flexible
- 5. Fast
- 7. 300ms
- 8. Less API calls
- 9. REST might not be the best
- 10. Update multiple objects
- 11. Failure
- 12. Sync
- 13. 3rd Party APIs...
- 14. ...should be used by the server
- 15. Full Featured
- 17. “Can we ...”
- 18. If you build it, it will get used
- 19. Apps are fully functional
- 20. “The website does X”
- 21. Flexible
- 23. Products change over time
- 24. App functionality will change
- 25. Reacting quickly saves time
- 26. Optimize later
- 27. Version APIs based on payload
- 28. Non-breaking changes
- 29. APIs for User Experience
- 30. 1 Screen, 1 API call
- 31. 1 Save, 1 API call
- 32. Cascading is bad
- 33. Different clients, different needs
- 34. Thanks! @MicheleTitolo