The only difference between Postmates and Uber Eats is that Postmates customers overwhelmingly tip the delivery driver. The Postmates app and systems is horrifically engineered. Uber Eats is an exceptionally better system.
Lack of SSR != An engineering horror. Crawlers can handle these pages effortlessly these days. So long as the client-side performance is good, SSR isn't very important.
In aggregate it's all a horror, given how easy it is to add SSR with Next.js. I know, I work on crawlers and scrapers professionally, and it's wayy easier, if you want a robot to scrape you, to have a site with SSR disabled. It's just generally faster and and a better experience for the user, and cheap to add.
As an aside, Stripe IIRC seems to use half-SSR, half client-side fetching really interestingly to fetch data below-the-fold after load, for even faster load times. That there is excellent engineering.
Are you talking primarily about the customer-facing apps?
I wouldn't go so far as to call the Uber Eats driver app an "exceptionally better system", it mostly works (modulo some annoying bugs that keep reappearing every few updates) but it's painfully obvious that they don't bother to do any serious QA on it. [They should send Dara out to be a driver for a few days, he'd love it!]
