Your mobile app relies on a third-party API update. How will you navigate the significant changes ahead?

One thing I have found helpful, specifically for external integration, is to know the roadmap of changes. During the initial stage itself, it will help one plan better. Imagine having a planned backlog for the next 2-3 sprints and then an external factor ruins it.

Start by understanding exactly how the API update will affect your app. Identify which features are impacted, whether it's backend processes, data handling, or user-facing elements. Knowing the scope of the impact helps you plan your next steps effectively.

Sometimes API changes are not versioned, or are not backward-compatible. This means that the API's and the app need to remain in sync! If this is the case for your app, you will need to choose the "Force Update" option when deploying to the App Store / Play Store. This way, all of your customers will receive the new application at the same time, and will no longer be able to use an old version of the app.

It is common for mobile app to rely on multiple 3rd party API such as Google Map, Ads, Metrics etc. It is wise to have either client adapter and/or server side aggregator. Both approaches are use to abstract away changes that can affect mobile apps. For server side aggregator, imaging you are using API A and B today. API B is charging a lot more next year so you sign up API C. Now without any changes to the mobile app, API A and C is being used simply because of the server abstraction. Client side adapter. When using API like metrics, instead of hardcoding to use Google Analytics, you have API adapter on the mobile that can switch to different provider such as Google or Amplitude etc. Changing provider doesn't require touch whole codebase

The update strategy will be defined by the impact of the change in the third party API. Fun is in knowing the details. Say the API has optional changes; this means, we continue to use it without any impact. Second scenario, say the API is versioned and there is time available before it is deprecated; this means, we will have sometime at hand to make changes to go to new API. Lastly, say it's a mandatory change with no option but to change, this means, we have no choice and have to refactor the changes. Plan the sprint and take up the tech stories. Knowing the third party API roadmap will help you decide which update strategy to choose.

Develop a clear strategy for integrating the new API. This might involve updating your app’s architecture, modifying certain workflows, or even revising timelines. Make sure your team is aligned on the approach and any deadlines that need to be adjusted.

Refactor to support abstraction. It is wise to have either client adapter and/or server side aggregator. Both approaches are use to abstract away changes that can affect mobile apps. For server side aggregator, imaging you are using API A and B today. API B is charging a lot more next year so you sign up API C. Now without any changes to the mobile app, API A and C is being used simply because of the server abstraction. Client side adapter. When using API like metrics, instead of hardcoding to use Google Analytics, you have API adapter on the mobile that can switch to different provider such as Google or Amplitude etc. Changing provider doesn't require touch whole codebase.

Prepare to refactor parts of your code to accommodate the changes. This could involve rewriting certain functions, updating API calls, or reworking how data is processed. Take this opportunity to clean up any legacy code, ensuring your app remains robust and efficient.

If the API update affects the user interface or experience, plan for the necessary UI changes. Keep the user experience smooth by ensuring that any transitions or new features introduced by the API are intuitive and enhance usability.

Run thorough testing to ensure the API update doesn’t introduce any bugs or issues. Test different scenarios, edge cases, and the overall app functionality to ensure everything works seamlessly with the new API version.

After implementing the update, monitor the app closely for any unexpected issues. Be ready to iterate quickly if something doesn’t work as expected. User feedback and analytics can be invaluable here, helping you catch and fix problems early.