Skip to content

Building Robust Client

Z edited this page Jul 30, 2014 · 2 revisions

Convener

Z – @zdne

Attendees

  • ~ 15 attendees
  • 3 of 15 attendees has developed a client in the last 365 days
  • only one attendant was a client (fronted) developer-only

Notes

It is imperative client developers see the benefits in using de-coupled hypermedia systems. There must be a clear benefit(s) solving a really painful problem – for example iOS clients can be updated only after Apple reviews the submission which might take couple of weeks – building a robust client that is resilient to API changes enables independent evolution of the API while it is not breaking the clients in the field.

Demo

Related

Z' slides from mobile developer's conference: https://speakerdeck.com/zdne/robust-mobile-clients-v2

Questions

  • most of the questions were related to modeling the API state machine
  • concerns were about the potential complexity of the state machine
Clone this wiki locally