API Architecture Summit 2014- APIs: A Mobile Developer's Perspective
•Télécharger en tant que PPT, PDF•
0 j'aime•171 vues
A talk I gave at The API Architecture Summit hosted by Layer 7 on API design considerations for mobile devices and wearables
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (11)
Similaire à API Architecture Summit 2014- APIs: A Mobile Developer's Perspective
Similaire à API Architecture Summit 2014- APIs: A Mobile Developer's Perspective (20)
Plus de Niall Roche
Plus de Niall Roche (6)
Dernier
Dernier (20)
API Architecture Summit 2014- APIs: A Mobile Developer's Perspective
- 1. Get in touch n.roche@ucl.ac.uk APIs: A Mobile Developer’s Perspective Niall Roche @niallroche
- 2. • Background • Brief History of Mobile & APIs • Mobile API Good Practice • API issues for Mobile • BaaS • Future API Considerations Agenda
- 3. • Mobile Developer - pretty much every platform! • Lecturer in Distributed and Mobile Computing • UCL Decide - building App Lab Digital Testbed • Tech Trainer • Mentor at Background
- 4. “Helping London’s entrepreneurs test, iterate and launch their ideas” DECIDE services include: •Open Device Lab •User Experience Expertise •App Store – closed testing service Get in touch at decide@ucl.ac.uk UCL Decide @ucldecide
- 5. • Occasionally Connected / Disconnected • High Latency & network congestion • Low or varying Bandwidth • Battery Issues • Storage Restrictions • Processing Restrictions Mobile Issues
- 6. • Small screen sizes and bad browsers - bad HTML support • No easy way to get content out of DB or existing system • Solution was to extract content by Screen Scraping • Horrible selection rules in Regex • Pages broke if content changed (and it usually did!) • Needed to repurpose content to be mobile friendly • Or alternatively maintain Two different versions of content • Web version and Mobile version A Brief History of Mobile
- 7. • Two major changes happened • Mobile Changed • Devices, browsers and networks got better • Mobile Internet became usable • Backends Changed • Along came Web Services then APIs then REST APIs • Life became easier! A Brief History of Mobile
- 13. WebsiteWebsite Dat a Mobile AppMobile App ProxyProxy XML / Text / JSON HTM L
- 14. WebsiteWebsite Dat a Mobile AppMobile App ServerServer HTM LDesktop Browser Desktop Browser XML / Text / JSON
- 18. • Data entry still a bit issue for users, help to avoid typing • reactive autocomplete like Google search • Interactions should not be bursty, not chatty • bad for the battery • do more with a single interaction • not too much in a failure scenario! • Reactive to the network type do more on WiFi • Check if EDGE vs LTE or measure throughput Mobile API Good Practice
- 19. • Use lightweight data exchanges JSON / BSON • no SOAP please! • Consider just sending the data that has changed only • Design APIs to make Entities cacheable when offline • Design to be easy to sync data and effectively recover from interruption - this is not easy! • Support cross platform, with apis and samples • Http pipeline - make more of the bandwidth you have Mobile API Good Practice
- 22. • Don't have APIs that are not easy to test or to mock out • No polling please! Bad in general, terrible on mobile • Users access services from multiple devices & concurrently • desktop & multiple mobile • don’t presume a single connection, adapt accordingly • Don’t push what has already been seen • Don’t Fetch a large set of results at once • could vary based on device or network or user pattern API issues for Mobile
- 23. • BaaS great to start with and for simple apps and prototyping - more time to concentrate on the App • Push integration is a must - key for Mobile, keeps users engaged • handling the plumbing around managing device ids • manage Apple/Google/Microsoft API integration • Need SDK & samples for major platforms & HTML5 • Use Appropriate and Secure Storage & Authentication • Offer Offline & Sync and your developers will love you! BaaS
- 24. • Great in the beginning but have medium-term issues • When app needs to go beyond basic CRUD • e.g. take action once entity added deleted updated • Problems with migrating data into other systems • Customisation beyond functions in the platform or extras that can be purchased BaaS issues for Mobile
- 25. • The Web is changing • Offline Apps - Chrome WebApps • WebSockets - Push (Server Send Events) • SPDY (HTTP 2.0) • priority on Web Requests • Leaner with less headers • The Growth of Wearables and Embedded / M2M • Back to small (no) screens, limited processing API Future Considerations
- 26. • Amazon AppStream - GUI in the cloud for streaming UIs • Api for rendering complex User Interfaces at sever-side • Shows potential of the future, older cheaper mobile devices that can handle rich content • Trend early towards updatable apps, • ease of pulling down new logic or app updates are now a patch • rather than a complete replacement and down in background API Future Considerations
- 27. Julia Shalet, Product Doctor 1 27 #needtoknowmobile for hipsters, hustlers & hackers Next Evening Programme: 25th March – 27th May 2014 Shoreditch, London “…Brilliant insights from industry pros, fresh thinking, interesting contacts, a new understanding of what it means to be 'mobile‘…” CPD Accredited, hosted by UCL & Mobile Monday London 20% Discount Code: Niall
Notes de l'éditeur
- Our alumni have gone on to receive awards, establish important partnerships, receive early stage funding, get jobs they want & get to the top of the App stores.