HomeCommunityMobile, Graphics, and Gaming blog
November 5, 2026

Help shape the future of Arm profiling tools for mobile games

Help shape the future of Arm's mobile game profiling tools. Share your Streamline workflows, essential features, and challenges in our developer survey

By Julie Gaskin

Share
Reading time 2 minutes

When you are building a mobile game, finding the bottleneck is part of the challenge. You also need to understand what the data means, decide what to change, and check whether it worked.

We want to hear how Streamline helps you with these tasks today and where it makes them more difficult. Your feedback will help us prioritize future engineering work on Arm performance profiling tools for mobile graphics and gaming.

Share your experience in our Streamline survey

Tell us what matters in your workflow

Streamline helps developers investigate CPU and GPU workloads on Android devices. However, a list of capabilities only tells part of the story. We want to understand how you use those capabilities to answer real performance questions.

Perhaps you rely on timelines and counters to investigate a demanding scene. Perhaps annotations help you connect activity in your game with hardware activity. Or perhaps your team depends on saved captures, reports, or scripts to compare results and share findings.

Which parts are essential? Which take too much effort? And which do you rarely use or find easier to handle another way?

What would be hardest to lose?

As we plan the future of our profiling tools, we want to understand the capabilities you depend on, including the less visible details that support your workflow.

The survey asks about:

  • Your investigations: what you are trying to learn and how Streamline helps you reach an answer.
  • Your essential features: the views, counters, and analysis capabilities you rely on and why.
  • Your three hardest features to lose: what would become slower, harder, or impossible without them.
  • Your frustrations: anything that makes profiling difficult, confusing, or unnecessarily time-consuming.

Concrete examples are especially useful. Tell us about a recent investigation. What triggered it? Which information mattered? What gave you confidence to make a change. You do not need to share confidential project details to explain what worked, or what was missing

Help us focus on the right problems

Whether you use Streamline every day or only when a difficult performance issue appears, your experience matters. We welcome feedback from developers working with commercial engines, custom engines, and native graphics applications across teams of all sizes.

Your responses will help us decide which capabilities to prioritize, where to simplify the experience, and which features may no longer be useful. If something is indispensable to your work, this is your opportunity to tell us why.

Take the Streamline survey and help shape what comes next


Log in to like this post
Share

Article text

Re-use is only permitted for informational and non-commercial or personal use only.

placeholder