OOM errors dropping by 30% when you go from 20 comments to 5 doesn't sound like "a job well done", that's more your initial hint to figure the hell out why 20 comments cause memory issues.
>Comment bundles are particularly heavy: They contain the comment text itself as well as its id, timestamp, and author metadata (including profile picture). ... Generating profile picture URLs is a CPU-inefficient operation because we must dynamically compute the correct CDN URL. The more comments we load, the more profile picture URLs we need to generate.
Is it loading the entire profile picture with each comment? Not just a small thumbnail?
Sorry, by "it" I should have written "the client." I meant to suggest my question of whether that is where their client OOM errors are coming from.
To prevent anyone from fiddling with the URL to generate thousands of differently sized images, they'll often have a way to 'sign' the URL to ensure people can't do this sort of attack. This can be expensive, depending on how its done I guess.
Is it only the first-mover myth that gets these companies such high regard in the industry? These are the kind of product issues you wouldn't expect with the kinds of technical interviews these companies use. Didn't they whiteboard inverting a red-black tree with anybody?
What Android device do you run?
What version of Android?
Is it stock Android from Google?
Stock firmware?
Not excusing the developers, but I want to point out that from my experience as a mobile developer, the sheer number of Android device configurations is a real problem to deal with, and often leads to lousy experiences on Android (along with Apps being a port of an IOS app, and teams outsourcing those ports to dev shops).
Reducing dating app friction to "sign in with Facebook and choose a few pictures you already uploaded" is a double-edged sword.