Lens

Quick summary of Lens

Lens (lens.loom.dev) is Loom's design system for their products — the design language behind Loom's video recording + sharing platform, published publicly as a design system website for developers + designers building on or integrating with Loom. Documentation of Loom's design language — typography, color, spacing, component library, interaction patterns, motion principles, accessibility guidelines specific to Loom's video-first product. Used primarily by developers integrating with Loom's API/SDK (integrations need to fit Loom's visual language for native feel) + designers studying Loom's design system as reference for their own systems work. Sits in the published-design-system category alongside the major design systems (Material by Google — consumer + mobile + Android-flavored; Polaris by Shopify — e-commerce-specific for Shopify apps; Carbon by IBM — enterprise + data-heavy + accessibility-focused; Fluent by Microsoft — enterprise; Spectrum by Adobe; Atlassian Design System; GitHub Primer; Geist by Vercel — covered earlier as dev-tool-flavored design system in Next.js/shadcn/ui ecosystem) at smaller scale focused on Loom's specific product surface. Distinguished from major design systems (Material + Polaris + Carbon + Fluent + Geist) by smaller scope focused on Loom-specific product needs vs broader ecosystem support, distinguished from open-source component libraries (shadcn/ui + Mantine + Material UI + Chakra) by company-specific design system positioning vs general-purpose, distinguished from Loom Product itself (the actual recording + sharing platform at loom.com) by published documentation reference vs design-in-action, distinguished from generic design system books + courses (broader theoretical) by specific company case study format. Free + public — Loom publishes Lens as developer-relations + ecosystem investment to support their API + SDK + integration ecosystem. Best for developers building Loom API/SDK integrations needing consistent visual language with Loom's product for native feel + brand cohesion, designers studying mid-sized tech company design system patterns as case study in publishing design systems to support ecosystem (similar pattern to Slack's design system + Atlassian's + GitHub's Primer), teams designing alongside or in coordination with Loom needing reference for Loom's visual language conventions, and companies considering publishing their own design system as reference for ecosystem developers where Lens is one example of the pattern. Skip if you don't integrate with Loom + don't build video products (Lens has limited applicability — your design system needs are unrelated), if you want a comprehensive design system to learn from + build on (larger published systems Material + Polaris + Carbon + Geist + Atlassian + GitHub Primer have more material), if you want to use a design system as foundation for your own product (copy from open-source systems shadcn/ui + Mantine + Material UI rather than referencing private-company design system), or if your work doesn't intersect with Loom's ecosystem (Lens is specifically for Loom-integration use cases). Interesting case study in 2026 of mid-sized tech company design system publishing — for developers building Loom integrations Lens is useful for matching Loom's visual language; for broader design system reference major published systems provide more material; worth knowing about as part of broader design system landscape awareness rather than primary study material.