lens-studio

3 posts

figma

The Best Advice to Bring to Work in 2025 | Figma Blog (opens in new tab)

The article gathers practical workplace advice from leaders at Ableton, Snapchat, Coda, and other companies. Their principles emphasize finding inspiration beyond familiar sources, automating low-value work, shortening users’ path to meaningful results, designing meetings around clear purposes, and maintaining momentum through difficult work. Together, they argue that effective work depends less on rigid formulas than on experience-based judgment. ## Look Beyond Design for Inspiration - Pablo Sánchez of Ableton recommends drawing ideas from emotions, memories, science, nature, and other fields—not just existing design conventions. - Designing for yourself first can produce work with genuine personal energy that resonates with users. - Ableton’s Note app borrowed from Brutalist architecture rather than traditional music software, creating a stripped-down experience focused on immediacy. ## Automate Work That Gets in the Way - Product managers should focus primarily on understanding customers, delivering value, and enabling sound decisions—not perfecting internal artifacts. - When documentation, reviews, or OKRs consume as much time as product development, teams should delegate or automate them. - Peter Yang uses AI to synthesize brainstorms, summarize customer feedback, and improve product requirement documents. ## Accelerate Users’ Time to “Magic” - Products should help new users reach their first meaningful “aha moment” quickly instead of overwhelming them with tutorials. - The goal is to move people from following instructions to confidently creating and sharing something of their own. - Snapchat’s Lens Studio team mapped the user journey and reduced the path from download to first submitted project from 19 steps to four milestones. ## Cultivate Different Types of Meetings - Coda’s Shishir Mehrotra distinguishes three meeting categories: - **Cadence meetings:** Regular staff meetings, standups, and syncs that track progress against goals. - **Catalyst meetings:** Decision-making forums, product reviews, and design critiques that resolve questions and drive change. - **Context meetings:** All-hands meetings, off-sites, and orientations that share information, establish context, and build connections. - Teams need a healthy balance, since too many catalyst meetings can cause burnout. ## Keep Moving Through Difficult Work - Dan Mall compares difficult progress to the tedious parts of training that are usually omitted from an exciting montage. - His advice is to build momentum to counteract the discouragement and monotony that can accompany worthwhile goals. The broader recommendation is to focus attention on meaningful outcomes: use unconventional sources of inspiration, remove unnecessary effort, guide users quickly toward value, give meetings a clear purpose, and keep building momentum when progress feels slow.

figma

The Long and Short of It: Issue no.5 | Figma Blog (opens in new tab)

Issue no. 5 of Figma’s newsletter, “Come together,” argues that progress depends on community, collaboration, and shared inspiration. Ahead of Config, it highlights creators and leaders whose work shows how connection—whether in person or online—helps turn ideas into reality. The issue spans product development, design quality, creative experimentation, AI, and community events. ## Building tools that feel magical - Charmaine Lee, product manager for Snap’s Lens Studio, shares principles for creating developer tools that delight creators. - Her approach emphasizes hands-on involvement, collaboration, and understanding the creator’s experience rather than following rigid product-building rules. - The feature presents creator-focused product development as an “all-hands-on-deck” effort. ## Craft, beauty, and product quality - Leaders from Stripe, Linear, and Figma discuss how to define and measure craft and beauty in digital products. - Katie Dill, Karri Saarinen, and Yukhi Yamashita explore the relationship between form and function. - Their central argument is that thoughtful design is not merely cosmetic: quality and beauty can contribute directly to product adoption and business growth. ## Designing quilts in Figma - Former product designer Nicole Boettcher uses Figma to plan and design handmade quilts. - Her process demonstrates how digital design tools can support physical, artistic work beyond conventional interface design. - The project playfully extends the idea of “moving rectangles,” connecting her former profession with her current craft. ## AI and creative tools - David Hoang, formerly of Replit, discusses how AI is changing creative tools, product design, and development workflows. - He recommends responding to rapid change through shared learning and strong communities. - Cohorts that combine accountability with fun can help people stay motivated as they develop new skills. ## Config and community opportunities - In-person Config tickets are sold out, but virtual attendance and local watch parties remain available. - Readers can follow the live blog for speaker highlights and event coverage. - The issue also promotes illustrator Thomas Colligan’s artwork, new Config merchandise, and the upcoming Figma Store release. Figma’s overall recommendation is to stay connected: creative progress is strengthened by mentors, collaborators, peers, and communities that make learning and experimentation possible.

figma

Charmaine Lee’s 10 Rules for Building Developer Tools | Figma Blog (opens in new tab)

Developer tools feel “magical” not because of polished interfaces, but because they help users quickly become confident creators. Charmaine Lee argues that teams should optimize what happens after the initial “aha moment,” shorten the path to meaningful creation, and build products through close, authentic engagement with developers. ## Prioritize lasting adoption over onboarding - The first-time user experience (FTUE) should not be overloaded with every product capability. - The real measure of success is whether users understand and continue using the product after the initial discovery moment. - Lens Studio 5.0’s public beta omitted a formal FTUE, testing whether the product was intuitive enough to use independently. ## Shorten the path to “magic” - Teams should identify how long it takes users to move from downloading a tool to creating and sharing something valuable. - Lens Studio’s team mapped a 19-step journey from visiting the website to submitting a first project. - By removing unnecessary steps and avoiding guidance for actions users already understood, they reduced the experience to four key moments. - User-journey mapping and testing help reveal which steps create delight, friction, or confusion. ## Meet developers in their communities - Product managers should engage directly with developers at meetups, conferences, hackathons, livestreams, and online communities. - Charmaine monitors AR discussions and attends events to learn developers’ language and gather candid feedback. - Building long-term context from these conversations enables better product decisions and more informed responses to user needs. ## Replace traditional marketing with DevRel - Developers tend to respond poorly to conventional marketing and prefer authentic communication. - Effective developer relations includes: - Real experiences and detailed product-building stories - Transparency about mistakes and limitations - A balance between accessible explanations and technical depth - DevRel should be a company-wide responsibility, not limited to a specialized team. - When employees advocate for both the product and its users, they can foster a more loyal developer community. The excerpt’s central recommendation is to design for users’ sustained progress, not merely their first impression: remove unnecessary friction, understand developers firsthand, and communicate with them honestly.