Six Calls One Screen

Your mobile app's home screen fires six requests to six services, discards most of each response, and feels slow on cellular networks. The web client needs a different subset of the same data and is happy with the current APIs. What is the standard fix?

Add a backend for frontends owned by the mobile team that composes the six calls server-side and returns one trimmed payload

Add optional field-selection query parameters to all six services so the mobile client can request fewer fields

Cache all six responses at the CDN edge with a short TTL so repeat visits to the home screen render from the nearest point of presence

Add one route in the shared gateway that calls all six services and returns their full responses concatenated, leaving the client to discard what it does not need