Server-Driven UI: one contract, an infinity of clients.
Web, Android and iOS update themselves without touching their code. Behind the scenes of a shared contract.
In a lab, a scientist has been turning a problem over in his head for weeks: the same visual, coded three times, for the web, for Android, for iOS. One evening, he ends up saying it out loud, in front of his two lab mice: what if a single contract were enough to drive that visual on all three at once?
The mice heard everything. And they don't intend to stop at the visual. What a component triggers, where it leads, what needs to be measured when someone interacts with it, all of that can live in the same contract too. So every evening, in secret, they pick the experiment back up and push it a little further.
One evening, the scientist hears a noise, pushes the door open, and catches them in the act. Before his eyes, the web, Android and iOS update at the same time, without a single line of code being touched on their side. He looks for the catch. There isn't one. It really works! Far beyond what he had imagined at the start.
What happened in that lab, we tell you at DevDay. A three-voice field report, unfiltered: what worked, what broke, what we would do differently.
