There was a good year or so period where I ran into 4 or 5 critical bugs that stopped me using the service entirely for days or weeks at a time. One of the dumbest was being unable to enter a credit card because the form required a field that wasn't being rendered. 6 months later I switch credit cards and again can't use the app for weeks because it wants a 5 digit postcode even after setting the country to 'Australia', but the server side check was still working and 86'd any combination of bs 5-digit code that was working.
Several times I've had something go wrong with the ordering system itself (on the UberEats side). Once an order was put through twice and two meals showed up on my doorstep. Another time I copped a cryptic error message followed by a Javascript crash and my card was charged but no order was logged upon refreshing the page (which indicates to me that something wasn't properly atomic and maybe some business logic was happening on the front end that shouldn't be? Presumably fixed now, I hope)
Even right now, as I type this, there's a bug on UberEats introduced in the last few days or weeks that's leaking variable names through to the front-end. I've got 'components.BadgeSoldOut.message' and 'components.CartItemCustomization.upTo' all over the place. I'm sure when that gets fixed another one will crop up next week.
There was a good year or so period where I ran into 4 or 5 critical bugs that stopped me using the service entirely for days or weeks at a time. One of the dumbest was being unable to enter a credit card because the form required a field that wasn't being rendered. 6 months later I switch credit cards and again can't use the app for weeks because it wants a 5 digit postcode even after setting the country to 'Australia', but the server side check was still working and 86'd any combination of bs 5-digit code that was working.
Several times I've had something go wrong with the ordering system itself (on the UberEats side). Once an order was put through twice and two meals showed up on my doorstep. Another time I copped a cryptic error message followed by a Javascript crash and my card was charged but no order was logged upon refreshing the page (which indicates to me that something wasn't properly atomic and maybe some business logic was happening on the front end that shouldn't be? Presumably fixed now, I hope)
Even right now, as I type this, there's a bug on UberEats introduced in the last few days or weeks that's leaking variable names through to the front-end. I've got 'components.BadgeSoldOut.message' and 'components.CartItemCustomization.upTo' all over the place. I'm sure when that gets fixed another one will crop up next week.
404s and broken systems seem par for the course.