Multi-Instance & Macro Management enhancements

Introduction

As a UX designer who thrives on solving complex problems through both creative intuition and structured analysis, I didn’t just follow a process—I lived it, questioned it, and evolved with it. This was not a linear project; it was deeply iterative, shaped by fast cycles of listening, building, testing, and refining.

And I didn’t do it alone.

<aside> 💡

I collaborated closely with:

• 🎨 Taroon Tyagi – Design Principal, who brought valuable critique and systems-level perspective. We reviewed wireframes daily and defined interaction systems and built our design system which we call “Blueprint” Here is figma link to view our building blocks.
• 👥 Product Managers: Harsh, Abhisht, Alok helped define feature sets and guided us to execute this the best way possible.
• Our genius engineers who developed it with QA to fine-tune features and got everything we worked for to life! </aside>

Our collective goal: Transform the chaotic, crash-prone BlueStacks 4 (BS4) into a smarter, faster, and more user-centric BlueStacks 5 (BS5). We followed an iterative UX design process informed by heuristics, research, data, and user feedback.

Let’s start with what is BlueStacks?

BlueStacks is a desktop software that lets users run Android apps and games on a PC. But for serious mobile gamers — who often use multiple accounts or automation tools — the experience had grown heavy, unstable, and overwhelming in BlueStacks 4.

In this case study I will be sharing my work concerning these features:

Framing the Right Problems, Not All the Problems

My first instinct in any redesign is to understand not just what they click, but what they feel and do when things go wrong. This stage brought out my naturally investigative side!

Discovery & Empathy

I began with a deep-dive into user sentiment using a blend of quantitative and qualitative data: