0:0019:20

Rapid Iterations with Server Driven UI

Akanksha Gupta 19:20 2022

Robinhood moved its UI to the server and shipped in days instead of weeks

One button sat left-aligned on iOS and centred on Android, simply because two engineers built the same design at different times. Multiply that across three thick clients and app store reviews, and a basic feature takes months. Robinhood engineering manager Akanksha Gupta shows how her team handed rendering to the server, and asks when that power stops being worth its cost.

See how SDUI works, a sample response, its trade-offs and how Robinhood adopted it

Watch on YouTube

In short

Akanksha Gupta, Engineering Manager at Robinhood, explains how server-driven UI (SDUI) moves rendering logic from iOS, Android and web clients to the server so teams can ship and experiment faster. She walks through a sample response, weighs the advantages against real challenges such as testing and performance, and shares how her team moved Robinhood's ETF pages and charts to SDUI.

“The biggest thing here is that even once this is done, we are really at the mercy of our customers to go ahead and update their app version so that they can make use of the latest features.”
“So, in the market, and personally, we've gone from like weeks to literally, you know, matter of days, like as soon as you have the change in, and your server deployments can be controlled through internal approval process.”

What you will learn

  • Explain how server-driven UI differs from traditional client-rendered mobile development.
  • Read a server-driven UI response that combines a data model with a view model.
  • Weigh the gains of SDUI (shared logic, shorter releases, A/B testing, faster incident response) against its costs.
  • Anticipate SDUI challenges such as nesting depth, testing risk and large response payloads.
  • Plan an incremental migration to SDUI and build a business case from the product backlog.

Key takeaways from the speaker

  • How do we iterate and ship products faster to our customers using server Driven UI
  • How is server driven UI different from our conventional engineering
  • What are the pros and cons, is it a one size fits all solution?
  • Robinhood's engineering team journey to Server driven UI(charts)

Details

Level
Beginner
Format
Talk
Technical depth
Practitioner
For
Early career, Mid-career, Senior individual contributor
Length
19:20
Published
July 2022

Questions this talk answers

What is server-driven UI?

The server returns both the data model (what to display) and the view model (how to display it), so the client becomes a rendering slate with very little logic of its own.

Why is traditional mobile development slow to iterate?

Each platform implements the UI separately, every release goes through App Store or Play Store review, and users must update their app before seeing changes. Bad releases are also hard to roll back.

What are the main challenges of server-driven UI?

The client has no UI context, so interactions and logging must be built into the framework, and teams must choose sensible backend abstractions and nesting depth. Testing becomes riskier and large responses need load testing for performance.

When is server-driven UI not worth adopting?

For a very small, basic app with mostly static data, SDUI might be over-engineering, so teams should weigh the pros and cons for their stage.

How did Robinhood migrate to SDUI and sell it to the business?

The migration took several months in milestones, moving static data first and charts as a fast follow-up. The team sold it with a one-pager showing backlog items scoped at weeks that could ship in a day or two.

About this talk

How do we ship faster and better products to our customers?

In the traditional software development, the data is driven by a backend service while the load of UI resides on the clients. As we scale, all our clients (IOS, Web, Android) end up with custom logic residing at client side. This can cause logic to diverge across platforms. Further, things become ugly if there is a new bug or feature needed as the app needs to follow a full release cycle on App Store. This often takes weeks to get the changes out to production in customer’s hand. Next, we are at the mercy of our customers to update the app version to be able to use the latest features. This slows us down with both iteration and experimentations.

In this fast-paced world where technology is changing every minute, do want to wait this long?

Enters Server driven UI where the server drives the UI. The data and UI is sent from the server to UI that simply acts as a rendering slate with no/little logic of its own. This opens a plethora of opportunities for companies to be agile and build faster to ship awesome products to their customers.

In this talk, we will introduce server driven UI to the audience, its pros and cons and share my engineering team’s personal journey from conventional to server driven UI development.

Topics

Related talks

Browse the library

What Is NoSQL?

Heather Maga Business Owner / Software Developer, Copper Owl Development

In NoSQL, the database stops checking your data and the developer takes over

Beginner AI and data 2020