I believe it's still true. Apple's swift/obj c++ don't use garbage collection. Android default java/kitlin does, so android is inherently more memory intensive.
Now if you want general ref counting you have to use atomic counters, and those will trash your performance on modern machines beyond fixing. And then we didn’t even mention that big object graphs will have to be recursively freed, an overhead that can’t be amortized in this case. Oh and you do need a tracing step one way or another to free cycles.