Mike Amundsen reviews patterns in developer practices and trends in services and libraries - from the increase in the number of client-side libraries such as EmberJS, Angular, and Bootstrap to the appearance of new "API composition" platforms such as Strong Loop - that give us a picture of why it's important to identify and leverage the growing sentiment that "Clients Matter, Services Don't".
An internationally known author and lecturer, Mike Amundsen travels throughout the world consulting and speaking on a wide range of topics including distributed network architecture, Web application development, and other subjects. In his role of Director of Architecture for the API Academy, Amundsen heads up the API Architecture and Design Practice in North America.
Software is Changing the World. QCon empowers software development by facilitating the spread of knowledge and innovation in the developer community. A practitioner-driven conference, QCon is designed for technical team leads, architects, engineering directors, and project managers who influence innovation in their teams.
Semantics vs Structure
However, I would like to point out that instead of transformation of the message structure for preserving client-side compatibility, the 'correct' answer is to use semantics.
A semantically tagged message can be 'queried' by the client to extract the information it needs. The exact structure is not important. The issues ofcourse are message bloat due to semantic tagging and additional processing on the client / server sides. Both of these are probably big issues for mobile clients at this time.
UDEF - a lightweight tagging vocabulary - had some traction once but it is not front-and-center anymore. See en.wikipedia.org/wiki/UDEF
Very thought provoking