Real Decision
How client application needs shaped API design across web, mobile and operational tools.
Problem
Different clients need different data shapes, response patterns and integration styles, but too many API variants create complexity and ownership overhead.
Decision
API design was driven by client usage patterns, allowing GraphQL where flexible client data composition provided value and REST where explicit contracts and operational simplicity were the better fit.
Why Not
Force one API style on every client and service.
Treat protocol choice as a framework preference instead of a product decision.