[solardev]

As a frontend dev with some full stack experience, I don't think this should really be a matter of "we want vs they want", but of your underlying resource constraints and UX needs (UI performance, database indexing or write performance, caching layers, app store limitations, etc.). It's not a game of hot potato, but how it impacts the overall data flow, both ingestion (from data sources) and serving (to the end user). Ideally you'd choose what's best for the project and company overall, not any particular team's microscopic preferences.

But in this particular case it doesn't seem like there's much to debate. It's like a single line of code for the frontend to map or reduce that simple JSON into whatever they want. It shouldn't require a rebuild (or how do you do any sort of dynamic data?).

If this is a common problem though, then yeah a BFF can help with the political side of things, if both groups can co-maintain it. It's really just a codified API layer. Backend sends data to it, frontend can choose how they want to present it through simple transformations.