|
|
|
|
|
by FerdSlav
1369 days ago
|
|
I have been at a few companies now that seem to have drank the "server-driven UI" punch and were actively architecting their mobile applications to be entirely dependent upon a stable connection to their backend to display anything beyond a splash screen. The argument for the architecture always falls along the lines of "enabling rapid deployment" and have had systems architects directly convey that they did not cache any data as it could result in displaying outdated or undesired content. Personally, I have come to despise this architecture as, in my experience, it provides marginal gains in process for a developer while increasing technical complexity, backend scale/dependence, and a sub-optimal user experience. |
|