Simra Husain — DevOps Engineer

I didn't start with performance engineering — I started like most mobile devs: building screens, wiring APIs, fixing bugs, and shipping fast. But after four years of building fintech apps in Flutter, I kept running into the same problems. Screens that stuttered under real data. Memory usage that climbed and never came back down. Cold starts that made users close the app before it loaded. The usual answer was "it works on my machine." That answer stopped being good enough for me. So I started profiling. I learned the Flutter rendering pipeline inside out. I dug into Dart's garbage collector, FFI bindings, C++ interop, and the actual mechanics of what happens between your setState() call and the pixels on screen. I got obsessed with the question most mobile devs skip: why does this feel slow? Now I work across Flutter and Android, building apps and SDKs for production systems — especially in fintech and real-time applications where dropped frames aren't just annoying, they cost money. I write about all of it on Medium. Not "10 tips to optimize your app" listicles — actual teardowns with profiler output, flamegraphs, and the kind of detail I wish I'd had when I was debugging my first memory leak at 2am. If you've ever stared at a DevTools timeline and thought "what am I even looking at," my articles are for you. Read them here: https://medium.com/@simra.cse When the profiler is closed, I'm usually somewhere in the mountains, pretending my phone doesn't have Slack on it.

Stackforce AI infers this person is a Flutter Performance Engineer specializing in Fintech applications.

Experience: 4 yrs 5 mos