Less flash, more flow: what makes a developer tool feel inevitable
Charmaine Lee, product manager for Snap AR’s Lens Studio, traces her love of developer tools back to a code editor on Neopets. The editor let her tweak her profile page’s colors, fonts, and images live. Years later, she sees the same thread running through the Slack API, Unity, and Lens Studio: “a feeling of magic.” The risk, she warns, is mistaking a polished UI for a product developers will actually adopt. “A sleeker design doesn’t necessarily equate to a better product for users,” she says. Her principles for building tools that earn that feeling start with a shift in focus.
Growth starts after the “aha” moment
Too many teams treat the first-time user experience (FTUE) as the entire product. Lee argues that the real test comes after the moment a user discovers value. When Lens Studio 5.0 launched in public beta, the team dropped the FTUE entirely, forcing the product itself to be intuitive enough to work without a guided walkthrough.
Her team maps the user journey in FigJam to find what sparks delight and what stalls momentum. That exercise revealed roughly 19 steps between downloading Lens Studio and submitting a first project. The team started trimming immediately—and also stopped investing in features that user testing showed were already intuitive. The lesson: measure “time to magic,” not just activation. The goal is to turn users into creators who are proud of what they build and want to share it.
Get out of the building—and into the community
Developers are social. They show up at conferences, meetups, livestreams, and hackathons, and Lee goes where they are. She attends AR meetups, travels for hackathons, and checks the Lens Studio keyword on X each morning. The payoff is candid, real-time feedback and fluency in the community’s language. “My superpower as a PM is having the time to build massive context comprising every dialogue that’s ever occurred about our tool,” she says, and being able to pull insights from that context to inform decisions.
This replaces traditional marketing, which developers are “allergic to.” They respond to an authentic voice, granular stories about how a product was built, transparency about mistakes, and a balance between accessibility and technical jargon. DevRel shouldn’t be a separate team, Lee insists; everyone is responsible for evangelizing the product and advocating for users. Snap AR encourages team-wide participation in events like Lens Fest and on social channels where demos, hacks, and questions flow both ways.
Break down silos, speed up shipping
A developer tool is more than its editor. Documentation, support, and the core product have to feel like one system, which means the people building them have to work as one team. In the past, Lee’s group lost context around known issues and confused users about whether to contact support or DevRel. Now, product, design, engineering, documentation, and support report to the same manager, and the alignment shows. She notes other structures can work, as long as transparency and accountability are incentives.
On shipping cadence, Lee recommends being less precious. Holding features back until they felt polished delayed valuable user input; switching from six-week to two-week release cycles changed how the team works. Faster shipping invites honest feedback, which Snap AR collects through a UserVoice portal that feeds into internal Slack for discussion before responses go out.
Let users build for each other—and cross the design/dev line
Reduce reliance on your product team for support by giving developers places to collaborate—forums, Discord, X—and ways to customize what you’ve built, such as open-source repositories and plugin APIs.
The line between design and engineering is also blurring. More developers are flexing design skills, and designers are learning to code. Lee encourages overlap, amplified by AI and collaborative tools. She recently prototyped an ad hoc feature request by duplicating a designer’s Figma file and editing text, images, and components to match the design system. The designer then used Dev Mode to build an AI assistant panel—one that pulls from documentation, tutorials, forum posts, and other resources to answer Lens Studio questions—that worked in production immediately.
Stay small and play
Most developer tools serve far fewer users than consumer apps, and that is an advantage. With less pressure to scale, teams can focus on first principles: building strong relationships through ad hoc meetings, school workshops, and personal Discord support. They can also refine core functionality, usability, and performance before racing to add features.
Finally, keep the builders happy. When a product team has fun, the delight transfers to the product. Lee points to quirky touches like ASCII art in code or cursor shakes that trigger a high five. At Unity, her team held extended reality (XR) “field trips” every Friday—play sessions that doubled as stress tests and feedback loops. Recently, a brainstorm that started with the most outrageous ideas on sticky notes created a low-pressure space for collaboration.
Lee stays motivated by the bigger picture: AR is “the ultimate magic that extends the human experience.” For her, that means a technology that can close distances with family across the globe, deepen friendships, and spark wonder.
Charmaine Lee is a product manager working on Lens Studio, Snap’s AR development and design tool. Previously, she built XR tooling at Unity Labs and Microsoft.
Peter Yang’s 10 rules for making products that customers love
