Title appears wrong. The past two year requirememt was 1GB and that has been raised to 2GB. Not more than. There's some decent bints about how to use the platf

Title appears wrong. The past two year requirememt was 1GB and that has been raised to 2GB. Not more than. There's some decent bints about how to use the platform effectively here. onTrimMemory is something most apps probably just dont do. Knowing when and how to use mmap to access resources is obvious to folks with some systems backgrounds, but we'd be lucky if that's half of mobile developers. In general it's just really easy to build badly behaved apps anywhere, on any platform. Seeing the magnitude of resources we're using & seeing problems develop is something mentioned in the article, but so often requires fairly expensive paid observability tools & a team that knows & has capacity & backing to care & spend the time. Most orgs care way too much about shipping features that pad their resume; few get promoted for keeping software in good shape.