Taking mobile testing from 0 to 1
mabl · Zero to one
Mobile testing grew from early customer conversations into a new product offering, with close collaboration across engineering, design, and go-to-market teams. I helped guide the product work from discovery through launch and continued learning from customers after release.
The problem
Customers had one place to test web and APIs, then had to switch tools and processes for mobile. The challenge was bringing mobile into that same workflow without trying to rebuild every feature of a mature mobile-testing product on day one.
How we approached it
- Customer conversations helped us understand which mobile workflows mattered most and where existing tools were creating friction.
- We kept the first release focused on the capabilities needed to make mobile testing useful alongside web and API testing, rather than trying to match mature mobile tools feature for feature.
- Working closely with design and engineering, we aimed for an authoring and execution experience that felt familiar to existing customers.
- Early adoption patterns and customer feedback informed pricing and packaging discussions, so the commercial approach reflected how teams expected to roll mobile out.
- Sales, customer success, support, and marketing helped prepare the rollout, customer communication, and internal enablement.
- We shipped a focused first release that established mobile testing as a new product offering.
What changed
- Customers could test mobile alongside web and APIs instead of juggling a disconnected workflow.
- The first release stayed focused enough to ship, learn from customers, and expand from evidence instead of trying to match established mobile tools feature for feature.
- Pricing, launch, and enablement were treated as part of the product work early, which made the release easier for customer-facing teams to support.
- The launch established a foundation for continued improvements informed by customer feedback and real-world usage.