How server-driven UI is revolutionizing mobile app experiences
Article Summary
Careem was losing weeks waiting for app releases just to update a banner. During Ramadan, when customer behavior shifts daily, that delay was killing their food business.
The Careem engineering team built AppEngine, a Server-Driven UI framework that lets business teams update app experiences without code changes or app releases. They share how they solved the rigid release cycle problem.
Key Takeaways
- UI updates now take hours instead of weeks, no app release needed
- Marketing teams control layouts through self-serve authoring tool, zero engineering required
- Mobile app acts as lightweight renderer fetching dynamic UI from backend
- A/B testing and personalization happen server-side without code deployments
- Engineering freed from UI tweaks to focus on building new capabilities
Careem's AppEngine framework eliminated engineering bottlenecks for UI changes, enabling real-time experience updates that respond to customer behavior within hours.
About This Article
Before AppEngine, Careem needed weeks to launch changes to discovery screens, promotions, and banners. Marketing, Product, Product Ops, and Engineering all had to coordinate, and any update required code changes tied to the app's release schedule.
Careem built AppEngine with three parts. A thin mobile client renderer handles display. A backend orchestrator generates UI components dynamically based on personalization rules and business logic. A self-serve authoring tool lets Product Ops configure experiences without asking Engineering for help.
Ramadan-specific discovery screens and sub-pages now launch in hours instead of weeks. AI-driven personalization shows users curated iftar and sahoor deals based on time and their behavior. Engineering teams can now focus on building new capabilities instead of making UI tweaks.