Built Around Real App Challenges

We started because apps kept crashing at the worst moments. Sound familiar?

Back in 2021, my co-founder and I were working on different projects in Vientiane when we both hit the same wall. Apps that worked perfectly in testing would slow to a crawl once real users got their hands on them. Battery drain complaints piled up. Crash reports came in faster than we could read them.

The tools available at the time? Either too basic to catch the real problems or so complex they needed their own instruction manual. We needed something in between—something that actually helped rather than adding another layer of confusion.

Team collaboration on mobile app performance analysis

What Guides Our Work

These aren't just words on a wall. They're how we actually make decisions when things get complicated.

Speed Without Shortcuts

Quick fixes never last. We dig into the actual cause of performance issues rather than masking symptoms. Sometimes that takes longer upfront, but you won't be calling us back in three months with the same problem.

Transparent Process

You'll know what we're doing and why we're doing it. No jargon meant to confuse, no black boxes where your app disappears for weeks. We explain things in plain terms because that's how we think about them ourselves.

Context Matters

An app for a retail chain has different needs than one for healthcare providers. We don't apply the same template to every situation. Your users, your infrastructure, your constraints—they all shape how we approach the work.

How We Actually Got Here

The first project we took on was almost a disaster. A local business had an app that kept timing out during peak hours—right when customers were trying to place orders. We spent two weeks convinced it was a server issue. Turns out the app was making redundant API calls that multiplied under load.

That taught us to check assumptions first. Now we start every engagement with monitoring before we touch any code. You can't improve what you haven't measured, and measuring wrong sends you down expensive dead ends.

By 2023, we'd worked with enough teams to spot patterns. Memory leaks from image caching. Battery drain from background location services left running. UI freezes from blocking the main thread. Most performance problems fall into recognizable categories once you've seen them enough times.

We built our diagnostic process around those patterns. It's not magic—just systematic elimination of common culprits, followed by deeper investigation if needed. Boring? Maybe. But it works more reliably than hoping inspiration strikes.

Who Does The Work

Small team, which means you'll actually talk to the people working on your app.

Souliya Phommachanh

Lead Performance Engineer

Souliya's been writing mobile code since 2016, back when apps still asked permission before accessing your location. She specializes in finding bottlenecks that only show up under real-world conditions—the ones that don't appear in synthetic benchmarks.

Before ForwardEvolv, she worked at a regional fintech where app performance directly affected transaction success rates. Nothing teaches you about latency like angry users who can't complete payments. She brings that same urgency to every optimization project.

Outside work, she runs a small workshop series teaching performance profiling to local developers. The skills shouldn't be locked away in specialist knowledge—more people understanding the basics means better apps for everyone.

Let's Talk About Your App

Got performance issues you can't pin down? Or just want a second opinion on your current setup? We do free initial assessments to see if we're a good match for what you need.

Start a Conversation