Mobile apps: Third-party integration strategy

Traditional client-server model
  1. Security-first approach
  2. Easy implementation
  3. No new learning curve needed
  1. Single point of failure
  2. High latency as it has to go through multiple layers
C2S2C
  1. UX first approach
  2. Very less latency
  1. Lack of security because of direct association of API keys in the mobile app
  2. Needs more attention to handle retry mechanisms
  3. Chances of missing the response back from the third party systems because of the state of the mobile app
C2S2S
  1. High persistence and availability first approach
  2. Highly reliable
  3. Highly secure
  1. Need to pay more attention to the security involved in the S2S callback
  2. More network calls and high latency
Combination of both C2S2C and C2S2S
  1. Best in class approach by taking the best of all the above approaches
  2. A highly available, scalable, persistent, and resilient solution
  1. Less cost-effective
  2. More operational overhead

--

--

--

Mobile application and connected-devices development consultant. Enthusiastic and excited about digital transformation era.

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Shankar Kumarasamy

Shankar Kumarasamy

Mobile application and connected-devices development consultant. Enthusiastic and excited about digital transformation era.

More from Medium

Top 8 reasons to opt for Hybrid Mobile Application

Mobile CI/CD With App Center Part 2

How to Display Product Variations — P1 — Using Meta Box and Gutenberg

How to Display Product Variations — P1 — Using Meta Box and Gutenberg

Create Pickup & Delivery App Like Makespace (On-Demand Storage)