Uber is Swallowing Glovo, and I Have Questions About the Tech

My phone just buzzed with a delivery notification, and it got me thinking. We talk about "seamless UX" in our pitch decks, but trying to route a dispatch rider through the chaotic energy of a rainy afternoon in Lagos, or navigating the unmapped streets of a university town in Owerri, is a different beast entirely.

The big news is that Uber is buying Delivery Hero for a staggering $14.8 billion. For those of us on the continent, this isn't just a corporate press release—it means Uber now owns Glovo and Talabat.

While the suits are talking about market share and gross bookings, my mind immediately goes to the codebase, the databases, and the actual humans on the ground.

---

The Nightmare of Merging Legacy Architectures

When you buy a company operating in 50 different markets, you aren't just buying brand equity. You are buying a massive, tangled web of legacy code, localized payment integrations, and regional APIs.

Glovo has spent years tweaking its platform to survive the specific quirks of African markets. Think about how we handle payments here. You can't just plug in a standard Stripe integration and call it a day. You have to write custom wrappers for Paystack, Moniepoint, and various mobile money APIs in Kenya and Ghana. You have to handle offline states because MTN or Airtel networks will inevitably blink out mid-transaction.

If Uber's engineering team decides to force-migrate Glovo’s entire infrastructure into the core Uber Eats stack, it is going to be a wild ride. Are they going to rewrite Glovo’s dispatch routing algorithms? How will they handle the transition without breaking the custom merchant dashboards that local restaurants in Gbagada or Akure rely on daily?

As a developer, the thought of mapping those database schemas makes me want to close my laptop and take a long walk.

---

The Offline-First Reality of the African Street

Let's talk about the hardware on the street. Your average dispatch rider isn't carrying the latest iPhone. They are running older, budget Android devices with limited RAM and screen burn-in, constantly fighting to keep their battery alive under the hot sun.

Glovo’s rider app has to be incredibly lightweight and resilient to survive. It has to handle GPS tracking without draining the battery in two hours. It has to work when the rider drops into a network dead zone in a basement kitchen.

If Uber attempts to bloatedly integrate everything into one single giant app, the performance hit on low-end devices will be disastrous. Local riders are already operating on a "No gree for anybody" mindset—if an app starts lagging, crashing, or eating up too much mobile data, they will simply close it and switch to a competitor.

---

Is There Still Room for Local Builders?

Every time a global giant consolidates its grip, people ask if it’s the end for local tech startups. I don't think so.

If anything, this creates a massive opportunity for hyper-local builders. Uber is big, but big means slow. They cannot easily pivot to solve the highly specific problems of a estate in Enugu or a tech hub community in Jos. They build for the mass market.

If you are a developer building a niche, localized delivery system—perhaps focusing on bringing fresh farm produce from rural Akure straight to suburban kitchens—you have an advantage. You can write custom code that handles the nuances of your specific community far better than an algorithm designed in California or Berlin.

We don't need billion-dollar valuations to build software that actually works for our people. Sometimes, all it takes is a clean API, a reliable offline sync, and an intimate understanding of the streets we walk on every day.