The Evolution of Config-Driven (Server-Driven) UI Frameworks: What Commit Histories Reveal Across Open-Source Engines

Config-driven user interface (CDUI), also called server-driven user interface, moves user interface (UI) layout out of the app binary into server responses so teams can update screens without an app store release. Because one schema serves many installed app versions, edits to it can break older apps. We statically compared parsed schema declarations across four open-source runtime CDUI engines (Yandex DivKit, Cash App Redwood, EnsembleUI, and archived Spotify HubFramework) and one inactive comparator compiled at build time (Airbnb Lona). Out of 1447 commits touching schema paths, 730 modify a runtime engine’s schema: 61.4% only add declarations, 38.1% remove or retype declarations, and 0.5% mark deprecations (93% parser accuracy against two-rater human labels). Standalone schema files had a higher share of additive commits than schemas written in code, though across four runtime engines this difference is not statistically significant. By Fisher’s exact test across commit halves, breaking edits fell significantly only in Redwood (73.3% to 25.0%, $p=0.012$). Finally, we compare systems across modularity, centralization, and strictness, showing when additions still break older clients (including Redwood throwing by default).