Setting up Android Studio shouldn't be the longest part of getting started with mobile testing. Drizz now detects when it's missing, runs the install for you through your terminal, and creates the emulator image automatically, so you go from "haven't installed anything" to "running your first test" in under five minutes.
THE PROBLEM
The first hour with most mobile testing tools is just setup.
If you've onboarded onto a mobile testing tool before, you know the drill. Before you write a single test step, you have to:
- Download Android Studio
- Create an account
- Install the SDK and required components
- Configure system images
- Spin up an emulator
On paper, none of these are hard. In practice, the whole sequence runs about 30 to 45 minutes, and that's on a good internet connection with a machine that has the right specs. On anything less, the variance gets ugly fast.
For a tool that's supposed to make testing faster, the setup itself is the slowest thing on the path.
WHO THIS MATTERS FOR
QA, PMs, and anyone who isn't an Android engineer.
If you're an Android developer, Android Studio is just a tool you already have. But mobile testing isn't only run by Android developers anymore. QA leads, manual testers, product managers, founders running test scripts on their own app, none of them want their first hour with a testing tool to be a Stack Overflow tab marathon about SDK paths and AVD configs.
This isn't a UX nicety. It's the difference between rolling a tool out to a team of three engineers versus a team of thirty across QA, product, and support.
WHAT'S NEW
Drizz detects what's missing, asks once, and handles the rest.
Drizz now does the entire Android Studio setup for you, automatically, the first time you need it.
Here's the flow:
1. Drizz detects what's missing. On launch, Drizz checks whether Android Studio and the required emulator image are installed. If they aren't, you don't get an error. You get an offer.
2. One tap to start. "Looks like Android Studio isn't set up. Want me to handle it?" Yes? You're done with the hard part.
3. Drizz drives your terminal. Drizz connects with your Mac terminal, runs the right commands in sequence, and walks the install through to completion. You press enter when prompted. That's the extent of what's required from you.
4. The emulator image is ready when it's done. By the end, you have a configured emulator image you can use immediately to run tests, no manual image creation, no AVD wrangling, no fiddling with system images.
TIME ON TASK
Before vs after
It's the same setup, on the same machine. Drizz just takes the steps you'd otherwise click through and runs them for you, in the right order, the first time.
WHY IT MATTERS
Testing tools are only useful if people actually start using them.
The biggest gap in mobile testing adoption isn't the testing itself, it's everything that happens before the first test. Every minute of setup friction is a minute the tool is competing against "I'll do this later." A lot of "later"s never come.
What changes with auto-setup:
- New users on a Drizz workspace can run their first test the same day they install
- Non-Android-native team members (PMs, manual QA, support engineers) can self-serve
- Cross-platform teams stop blocking on whichever member of the team has the right local setup
- Onboarding a new hire onto your test suite stops being a half-day task
This isn't a flashy feature. It's the kind of thing you only notice because something that used to be annoying isn't anymore. That's the point.
GETTING STARTED
Live now on Mac. No flag, no opt-in.
Auto-setup ships with the latest Drizz desktop release for macOS. If you don't have Android Studio installed, Drizz will offer to set it up the next time you need it. If you already have it, nothing changes.
If you've been holding off on rolling Drizz out to a wider team because of setup friction, this is the unblock. Book a walkthrough and we'll run it through your team's environment.
