1 Replies - 730 Views - Last Post: 09 August 2017 - 11:36 AM

#1 darkec   User is offline

  • New D.I.C Head

Reputation: 0
  • View blog
  • Posts: 11
  • Joined: 29-November 12

How to handle old/new API for apps

Posted 09 August 2017 - 11:22 AM

Let's say I have stable API for iOS and Android and users are using my app version 2.0.

Now we see that we can improve current feature by adding some GET parameter on URL which can change the response just the way we want it. Backend is easy to update. Let's say we update Android and iOS and publish them both live and soon after we push backend code to the server. Now we have v2.1.

Now we have a situation where we have v2.1 live and this new backend code live which means v2.0 won't work because it doesn't have that GET parameter.

How to handle those kind of situation in general. Sure we can use some if else in our code in backend, but is there any better standard way to handle that situation especially if fix is bigger.

Is This A Good Question/Topic? 0
  • +

Replies To: How to handle old/new API for apps

#2 modi123_1   User is online

  • Suitor #2
  • member icon

Reputation: 14039
  • View blog
  • Posts: 56,188
  • Joined: 12-June 08

Re: How to handle old/new API for apps

Posted 09 August 2017 - 11:36 AM

Some folk have a different API url for their next version. Like a separate branch then give everyone X months to convert before it is decommissioned..
Was This Post Helpful? 0
  • +
  • -

Page 1 of 1