Download to read offline
Uploaded byMichele Titolo
APIs for the Mobile World
This document discusses APIs for mobile applications and provides 5 recommendations for building great mobile experiences through APIs. The recommendations are: 1) Keep API conventions consistent, 2) thoroughly document APIs, 3) maintain backwards compatibility in API versioning, 4) implement error handling and caching to insulate mobile clients from issues, and 5) design APIs specifically for mobile use cases and experiences rather than just exposing backend data. The document argues that mobile-optimized APIs can improve development speed and iteration, reduce bugs from client-specific implementations, and better support creating customized mobile experiences.
More Related Content
Similar to APIs for the Mobile World
APIs for the Mobile World
- 1. APIs for the MobileWorld Michele Titolo Lead Software Engineer @ Capital One
- 2. Why APIs forthe world?mobile
- 3.
- 4. Apps Have ToBe Great 👍
- 5.
- 6.
- 7. Can APIs makean app not great? Yes.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 15.
- 16.
- 17.
- 18. Don’t Return 200 With“Error”
- 19.
- 20. Endpoint “id” field /productsid /products/:id productID /cart product_id
- 21.
- 22.
- 23. Ask So AndSo Is Not Documentation
- 24.
- 25.
- 26.
- 27.
- 28.
- 29.
- 30.
- 31.
- 32.
- 33.
- 34.
- 35.
- 36.
- 37. Releasing An App Doesn'tMean People Will Use It
- 38.
- 39. The Bigger Your Ecosystem,The More This Is Needed
- 40.
- 41.
- 42.
- 43. Make an APIjust for mobile .5
- 44.
- 45. Tailor APIs toMobile Experiences
- 46. Not A NewConcept
- 47.
- 48.
- 49.
- 50. The most amazingmovie app in the world
- 51. Lets Add A NewFeature
- 52. Show nearby movietimes
- 53. # Obtain alist of movies GET /movies # Obtain a list of nearby theatres GET /theatres?lat=…&long=… # Obtain the showing times for a theatre GET /theatres/1234/times
- 54. server.makeMoviesRequest { (movieList,error) in if error { // handle error case } else { // handle success case } }
- 55. server.makeMoviesRequest { (movieList,error) in if error { // handle error case } else { // handle success case } } server.makeTheatresRequest(lat,long) { (theatreList, error) in if error { // handle error case } else { // handle success case } }
- 56. var moviesRequestComplete: Bool= false var theatresRequestComplete: Bool = false server.makeMoviesRequest { (movieList, error) in if error { // handle error case } else { moviesRequestComplete = true // do something with the data } } server.makeTheatresRequest(lat,long) { (theatreList, error) in if error { // handle error case } else { theatresRequestComplete = true // do something with the data } }
- 57. func makeInitialServerCalls (){ var moviesRequestComplete: Bool = false var theatresRequestComplete: Bool = false server.makeMoviesRequest { (movieList, error) in if error { // handle error case } else { moviesRequestComplete = true // do something with the data } } server.makeTheatresRequest(lat,long) { (theatreList, error) in if error { // handle error case } else { theatresRequestComplete = true // do something with the data } } } func makeTheatreTimesRequest(for: theatres) { for theatre in theatres { server.makeTheatreTimesRequest(theatre.id) { if error { // handle error case } else { // process movie times } } } }
- 58. func makeInitialServerCalls (){ var moviesRequestComplete: Bool = false var theatresRequestComplete: Bool = false server.makeMoviesRequest { (movieList, error) in if error { // handle error case } else { moviesRequestComplete = true self.movies = movieList } } server.makeTheatresRequest(lat,long) { (theatreList, error) in if error { // handle error case } else { theatresRequestComplete = true makeTheatreTimesRequest(for: theatreList) } } } func makeTheatreTimesRequest(for: theatres) { let closestTheatres = theatres..3 // get 3 closest theatres for theatre in closestTheatres { if !requestTimesForTheatreAndReturnIfAnotherRequestShouldBeMade(theatre) { break } } } func requestTimesForTheatreAndReturnIfAnotherRequestShouldBeMade(theatre) { server.makeTheatreTimesRequest(theatre.id) { if error { // handle error case } else { // process movie times } } }
- 59. func makeInitialServerCalls (){ var moviesRequestCompletedSucessfully: Bool = false var theatresRequestComplete: Bool = false server.makeMoviesRequest { (movieList, error) in if error { // handle error case } else { moviesRequestCompletedSucessfully = true self.movies = movieList } } server.makeTheatresRequest(lat,long) { (theatreList, error) in if error { // handle error case layoutMovies() } else { theatresRequestComplete = true if moviesRequestCompletedSuccessfully { makeTheatreTimesRequest(for: theatreList) } } } } func makeTheatreTimesRequest(for: theatres) { let closestTheatres = theatres..3 // get 3 closest theatres var theatreTimesAPIsFinished: Bool = false for theatre in closestTheatres { if !requestTimesForTheatreAndReturnIfAnotherRequestShouldBeMade(theatre) { theatreTimesAPIsFinished = true break } } layoutMovies() } func requestTimesForTheatreAndReturnIfAnotherRequestShouldBeMade(theatre) { server.makeTheatreTimesRequest(theatre.id) { if error { // handle error case } else { // process movie times } } } ‼ ❓ 🚫 🙀 💩
- 60.
- 61.
- 62.
- 63.
- 64.
- 65. Resource Based Apis MakeCreating Experiences Difficult
- 66. Solution: Apis For MobileExperiences
- 67. Logic Has ToLive Somewhere
- 68. Easier To Release AndIterate
- 69.
- 70.
- 71. 1. Keep ItConsistent 2. Document Everything 3. Honor Thy Contracts 4. Insulate The App 5. Make Something Special In Summary
- 72.
- 73.