title: Best way to manage updates on an iOS client/server app
body: <p>I have a logistical question: I'm trying to figure out the best way to manage APIs getting out of sync with an app.  The best way to explain it is with an example:</p>
  
  <p>Let's say MyApp Version 1.0 posts to a "submit_feedbacK" API that requires first_name, last_name, and email.</p>
  
  <p>I then submit MyApp Version 2.0 to the App Store.  That version is designed to post first_name, last_name, gender, and email to the API.  All of these are required fields on the API.</p>
  
  <p>The problem I have:
  - If I update the API before the new App is live, it will break Version 1.0
  - If I wait until Version 2.0 is live and remotely cripple 1.0, I have to time it correctly.</p>
  
  <p>I'm going to guess that the 'right answer' is to maintain two different APIs.  But if both APIs post to the same live database, that makes things a bit awkward. </p>
  
  <p>Does anyone have suggestions on how to model this?</p>