Hi! I’m Jordan Nnabugwu, a Software Engineer III at Very Good Ventures.
Let me paint a picture: You’ve got a few paywall designs you want to test. Normally, this means building custom A/B test logic, waiting for app store approvals, maybe even pausing dev work while marketing catches up. What’s the solution?
Recently, I’ve been working with something that feels like a cheat code for mobile development: Server Driven UI (SDUI). And I’m here to tell you, it’s a game-changer.
From Hardware to High-Velocity Mobile
Before joining Very Good Ventures, I spent time as a hardware engineer at Intel and Galtronics. Then I transitioned into software, working at places like Whisker and contributing to Open Food Facts. Whether it was IoT devices or mobile apps, I kept running into the same friction: UI updates were slow, and reacting to real-time user needs felt impossible. That’s what got me excited about SDUI.
This year, I had the pleasure of attending Fluttercon USA 2025 for the first time—and even more exciting, I got to take the stage for a lightning talk on Server-Driven UI in Flutter.
.png)
In my session, I explored how a server-driven architecture can decouple content from logic, giving teams the flexibility to release faster and adapt in real time.
The Old Way Slows You Down
Let’s talk real talk: Traditional mobile development has serious bottlenecks.
- You’re at the mercy of the App Store: Every tweak, even a button label, requires a new build, a new submission, and a wait.
- Marketing campaigns are stuck in the past: Want to launch a promo tomorrow? Sorry, you should’ve planned that two weeks ago.
- Personalization? Good luck: Unless you baked in every variation upfront, you’re not adapting to real-time behavior.
And in an environment where user expectations are sky high, that just doesn’t cut it.
Enter SDUI: The Server Drives, Your App Renders
Server Driven UI flips the script. Instead of shipping all your UI in the app itself, you let your server define what the UI should be—layouts, text, components—and your app renders it on the fly.
The result? UI changes become instant.
- Want to launch a new banner? Go for it.
- Need to personalize content based on user behavior? Easy.
- Want to A/B test three layouts? You can do that without even updating the app.
SDUI removes the friction—and it’s kind of addictive.
This Isn’t a New Concept: it’s a Smarter Take on the Old Web
If this sounds familiar, it should. Web development has done this forever. In the early 2000s, every web page came fully rendered from the server. Then we went all-in on client-side frameworks. Now, we’re seeing the pendulum swing back.
Why? Because today’s tools have eliminated the technical barriers, and SDUI is just smarter.
Real-World Inspiration: NuBank
One company that totally nails this approach is NuBank. They serve over 100 million users with a rapidly growing team. And they use SDUI to scale fast.
- 70% of new screens are built with SDUI
- 43% of the app is now server-driven
- They push updates instantly—no app store delay
- Their teams ship independently and iterate in real time
That’s the kind of velocity I want for every product team.
Picking the Right Tool for the Job
If you’re thinking about trying SDUI, there are a few tools I’ve explored:
- Remote Flutter Widgets (RFW): Powerful, binary-based. A bit of a learning curve, but solid.
.png)
.png)
- Swap: A Dart wrapper around RFW with a smoother developer experience.
.png)

- Stac: JSON-based, super friendly for teams just getting started.
.png)
.png)
Your choice depends on your team, timeline, and how deep you want to go.
When to Use (and Not Use) SDUI
Great for:
- Promo banners
- Real-time personalization
- A/B tests
- Dashboards with flexible content
Not ideal for:
- Animations or gesture-heavy screens
- Offline-critical experiences
- Entire apps (trust me—go hybrid)
I suggest using SDUI where flexibility matters most, and where keeping your performance-critical views static is key.
Final Thoughts
The first time I saw a fully updated UI land in an app without a release, I had one thought: “Why isn’t everyone doing this?”
SDUI has changed how I think about mobile development. It’s not just faster—it’s smarter. It helps you:
- Stay nimble
- Deliver better experiences
- Give your teams autonomy
- Build products that can adapt in real time
And honestly, it’s fun. It unlocks a new level of creativity for developers—and that’s something I think we could all use more of.
Curious about implementing SDUI? Reach out, I’d love to talk!