Who actually uses these products,
and what made them stay.

The Spline 3D Web Designer

A web designer or creative developer who uses Spline to add 3D to their web projects without the learning curve of Blender or Cinema 4D. They create 3D hero sections, interactive product visualizations, animated icons, and immersive landing pages. They are a designer who crossed into the third dimension. They appreciate that Spline runs in the browser, exports to the web natively, and feels like a design tool rather than a 3D modeling application. They are the person making websites feel like they have depth.

“A SaaS company wants a landing page that stands out.”

The Webflow Design-to-Production Designer

A web designer or design agency owner who ships production websites directly from Webflow — no developer handoff, no code translation step. They think in layout, typography, and spacing, but they've also learned Webflow's class system, CMS collections, and interaction triggers. They are a designer who became a builder. They're proud that they can ship a client site in a week, but they're aware that their Webflow projects are sometimes held together with class naming conventions only they understand.

“A teammate asked how they managed build responsive, pixel-perfect websites that match the design vision exactly.”

The Webflow No-Code Designer

A designer — visual, brand, or marketing — who uses Webflow to design and build production websites without relying on a developer. They came from Figma or Sketch and discovered that the gap between design and the live site was where everything good went to die. Webflow closed that gap. They have strong opinions about how websites should look and work, and Webflow lets them act on those opinions directly. They are faster in Webflow than any developer who doesn't know the design would be.

“It's launch week for a new product campaign.”

The Framer Motion Designer

A product designer or motion designer who gravitates toward Framer because it treats animation and interaction as first-class design elements. They don't just design screens — they design how screens transition, how elements respond to hover, how content enters and exits. They've used Figma for static design but find it limiting when the design's value is in how it moves. They are the person who insists that the ease curve matters and that a 200ms delay feels different from a 300ms delay.

“A teammate asked how they managed design and prototype complex animations and transitions that developers would struggle to implement from specs.”

The Canva Non-Designer

A marketing coordinator, social media manager, small business owner, or teacher who is responsible for creating visual content and has no design training. They discovered Canva and it changed what was possible for them. They can now make things that look professional without calling a designer or spending three hours in PowerPoint. They are faster than they were. They are not as good as an actual designer. They know this and they've made peace with it.

“A teammate asked how they managed create content that looks polished enough to publish without a professional review.”

The Rive Interactive Animation Designer

A motion designer or creative developer who uses Rive to create animations that aren't just decorative — they're interactive. They build loading indicators that respond to progress, toggle switches that morph between states, onboarding illustrations that react to user input, and game-like UI elements. They think in state machines: idle, hover, active, success, error. They chose Rive because After Effects exports video, Lottie exports playback, but Rive exports interactive, state-driven animations that respond to runtime input.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about the state machine editor has a learning curve, especially for designers coming from timeline-based tools in two weeks.”

The Figma Product Designer

A mid-to-senior product designer at a tech company with 3–8 years of experience. Figma is where they spend most of their working day — from rough explorations to polished specs. They work across a shared team library and collaborate with PMs in comments and engineers in dev mode. They are fast, opinionated about component architecture, and quietly frustrated by how the tools around Figma still slow everything down.

“A teammate asked how they managed move from concept to spec without losing fidelity at each stage.”

The Photoshop Production Designer

A graphic designer — in-house or agency — who uses Photoshop as their primary production tool for image work. They've been in Photoshop for 5–15 years and work with the efficiency of someone who knows exactly where everything is and what everything does. They don't explore menus. They use shortcuts. Their workspace is a system they've tuned. Photoshop is slow sometimes and they've learned to work around it the way you work around a colleague's habits — with patience and workarounds they've stopped noticing.

“The shift was quiet.”

The Framer Interactive Designer

A product designer or creative developer who uses Framer for either high-fidelity interactive prototypes or production marketing sites — often both. They came from Figma and knew it wasn't built for interaction. They came from Webflow and wanted more design control. Framer sits between those two worlds and they've made it home. They are comfortable with the code escape hatch. They don't use it unless they have to. When they have to, they can.

“The shift was quiet.”

The Typeform Survey Designer

A UX researcher, product manager, or marketer who chooses Typeform over Google Forms because the survey experience matters. They've learned that completion rate is the most important metric for a survey, and completion rate is a design problem. They craft surveys that feel like conversations: one question at a time, conditional logic, thoughtful copy. They spend as much time on the question experience as they do on the question content. They are the person who says "we can't just send a Google Form — that sends a message about how much we value their feedback."

“The shift was quiet.”

The Typeform Research and Marketing User

A UX researcher, marketer, or operations person who uses Typeform because they've seen what happens to completion rates when you use Google Forms. They care about the quality of the responses they collect — which means they care about the experience of filling in the form. They design forms deliberately: question order, logic branches, conversational tone. They know their completion rate. They have an opinion about it.

“The shift was quiet.”

The Storybook Frontend Developer

A frontend developer or design systems engineer at a company with a shared component library. Storybook is where they develop components in isolation, document their props and variants, and give designers a place to review and interact with components without pulling a branch. They've set up Storybook, they've configured it, they've written stories for 40–150 components. They're the person who knows where Storybook falls short and stays anyway because the alternative is worse.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about storybook configuration that fights the build tooling when the team's setup is non-standard in two weeks.”

The Figma-to-Code Developer

A frontend or full-stack developer who didn't choose Figma but lives in it three hours a week. They open Figma to inspect designs, grab spacing values, export assets, and try to understand what the designer intended for edge cases that weren't mocked up. They've learned enough about auto-layout to know when a design will be painful to implement. They have opinions about design tokens that the design team doesn't want to hear yet.

“A teammate asked how they managed extract exact spacing, color, and typography values without guessing.”

The Figma Dev Mode Engineer

A frontend engineer at a product company who implements UI from Figma designs. Dev Mode is their interface to the design file — the layer of Figma that was built for them rather than around them. They use it to extract measurements, inspect component properties, copy CSS values, and verify that what they've built matches what was designed. They have strong feelings about when Dev Mode helps and when it's still faster to ask the designer. Those feelings are specific.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about cSS output that assumes a different architecture than the codebase they're working in in two weeks.”

The Maze Unmoderated Research Lead

A UX researcher or product designer at a company where research is valued but researcher time is scarce. They use Maze to run tests they can't run fast enough with moderated sessions. They design the test, connect the Figma prototype, send the link, and come back to results in 24–72 hours. They know unmoderated testing misses the nuance of moderated sessions. They also know that running 8 moderated sessions takes 2 weeks of scheduling and 2 days of synthesis. Maze takes 2 hours to set up and 1 hour to analyze. They're using the right tool for the question.

“A teammate asked how they managed get directional usability signal fast enough to influence a design decision.”

The Pitch Startup Storyteller

A startup founder, head of product, or strategy lead who creates presentations that need to look beautiful and tell a compelling story — investor decks, product roadmaps, board updates, customer pitches. They chose Pitch because it produces better-looking slides with less effort than PowerPoint or Google Slides. They value design defaults that make everything look good automatically. They collaborate in real time with co-founders and design team members. They are visual communicators who believe that how a story is presented is as important as the story itself.

“It happened mid-workflow — the founder is preparing for a Series A fundraising round.”

The Resend Transactional Email Developer

A full-stack or backend developer who needs to send transactional emails — password resets, welcome emails, order confirmations, notifications — from their application. They chose Resend because the developer experience felt like it was designed for someone who writes code, not someone who uses a drag-and-drop email builder. They write their email templates in React. The API is simple enough that they memorized it. They are not thinking about email infrastructure. They are thinking about their product.

“The shift was quiet.”

The Sanity Developer-Content Team

A developer who chose Sanity for a project that needed a content infrastructure serious enough to model complex relationships and flexible enough to be customized for a non-developer content team. They built the schema. They configured the Studio. They wrote the GROQ queries. The content team uses what they built every day. The developer's relationship with Sanity is: maintenance, evolution, and occasional deep satisfaction when the content model they designed months ago handles a new requirement gracefully.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about schema changes that require migration scripts for existing content — the cost in two weeks.”

The Miro Workshop Facilitator

A product designer, agile coach, or team lead who facilitates remote workshops in Miro. They don't just draw on a whiteboard — they design participatory experiences: timed exercises, voting rounds, structured templates, and breakout activities. They've learned that the tool is 30% of a good workshop; the other 70% is facilitation design. They are the person who spends 2 hours preparing a Miro board so that a 1-hour workshop runs smoothly for 20 people.

“The facilitator is running a design sprint kickoff with 15 people.”

The Rive Interactive Animation Designer

A designer or creative developer who builds animations that respond to state, not just ones that play and loop. They discovered Rive when they realized that Lottie was great for playing animations but couldn't handle the "and then when the user clicks, it does this" requirement. Rive's state machine changed their practice. They now build animations that are interactive first — hover states, press states, loading-to-success transitions, character rigs that respond to game input. They are comfortable in both the design and the runtime.

“It happened mid-workflow — they're building a loading animation for a fintech app.”

The Sanity Content Architect

A developer or content architect who uses Sanity because they think about content as structured data, not pages. They design content models that serve web, mobile, email, and API consumers from a single source. They've built custom studios, created real-time collaborative editing environments, and used GROQ to query content in ways traditional CMS query languages can't express. They are the architect of the content layer, and they treat content modeling with the same rigor as database schema design.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about customizing the Studio deeply requires significant React knowledge, raising the bar for non-senior developers in two weeks.”

The Harvest Freelance Time Tracker

A freelance designer, developer, consultant, or small agency owner who bills by the hour and uses Harvest to track every minute. They know that untracked time is unpaid time, and unpaid time is a silent business killer. They start timers when they begin work, stop them when they break, and review their timesheets weekly to make sure nothing slipped. They've built a system that balances accurate tracking with not letting the tool interrupt their flow. They are both the worker and the business.

“A freelance developer juggles three active clients.”

The Dropbox Creative Team Manager

A creative director, design lead, or production manager who manages files for a creative team — designers, photographers, video editors, copywriters. They chose Dropbox because it handles large files (PSD, AI, video) better than Google Drive and because the desktop sync means creatives can work in their native apps without learning a new tool. They are the person who designs the folder structure, enforces naming conventions, and answers the question "where is the latest version of the logo?" at least three times a week.

“The shift was quiet.”

The Storybook Design System Maintainer

A frontend developer or design technologist who maintains the company's Storybook instance. They write stories for every component, document props with controls, set up visual regression testing, and serve as the bridge between designers and developers. They are the keeper of the design system's technical truth. When a designer asks "does this component exist?" the answer lives in their Storybook. When a developer asks "how do I use this prop?" the answer lives in their Storybook. They are the librarian of the component library.

“The shift was quiet.”

The Loom Async Communicator

An individual contributor or people manager at a remote-first company who uses Loom as their primary format for communicating complex information asynchronously. They record walkthroughs, give feedback, share context, and replace 80% of the meetings they used to have. They are comfortable on camera — not because they love being on camera, but because they've made peace with the fact that async video is the clearest way to communicate nuance without a meeting. They have a good mic. They have a ring light. They did not buy these for fun.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about videos that never get watched — the async promise only works if the other person opens it in two weeks.”

The Harvest Freelancer and Agency Owner

A freelancer, consultant, or small agency owner (2–15 people) for whom time is the product. They track hours against client projects and invoice from those hours. Harvest is where the financial reality of their business lives. They've learned that unbilled hours are lost revenue, that clients will dispute invoices without time entries to back them up, and that the difference between a profitable month and a break-even month is often the accuracy of their time tracking. They are disciplined about logging time — or they are trying to become disciplined about it.

“A teammate asked how they managed track time accurately enough that invoices are defensible and projects are profitable.”

The Hotjar Session Watcher

A product manager, growth marketer, or UX designer at a company of 20–500 people who uses Hotjar to answer questions that quantitative analytics can't. They know their funnel. They know where users drop off. What they don't know is why. Session recordings are how they find out. They've watched hundreds of sessions. They've seen users rage-click on things that aren't buttons, scroll past CTAs without seeing them, and get confused by flows the team thought were obvious. Each one of these is a design decision waiting to happen.

“The checkout conversion rate dropped 2.”

The Spline Web 3D Designer

A product designer, visual designer, or creative developer who started using Spline because they wanted 3D on their website or product and Blender was too much. They have a 2D design background — Figma is their native language. Spline felt like Figma with a Z-axis. They've built at least one thing they're proud of: a 3D hero section, an interactive product visualization, a floating element that reacts to cursor position. They use it for client work and personal projects. They consider themselves an early adopter of the idea that 3D should be accessible to product designers, not just motion designers.

“They're redesigning a SaaS product's marketing homepage.”

The Whimsical Product Thinker

A product manager, designer, or architect who uses Whimsical when they need to think visually but don't need pixel-perfect precision. They create flowcharts to map user journeys, wireframes to sketch interfaces, and mind maps to explore problem spaces — all in the time it would take to set up an artboard in Figma. They value speed over fidelity. They are the person who brings a Whimsical link to a meeting and says "here's what I'm thinking" before anyone else has a concrete proposal.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about there's a ceiling — when wireframes need more detail, the transition to Figma requires starting over in two weeks.”

The Dovetail Research Operations Manager

A UX research lead or research operations manager at a product company who uses Dovetail to turn the chaos of qualitative research — interview transcripts, survey responses, usability test recordings — into a structured, searchable insights repository. They tag, code, and synthesize findings so that when a PM asks "what do we know about onboarding friction?" the answer is a link, not a 3-week research project. They are the librarian of user insights, and they've learned that research nobody can find is research that didn't happen.

“A teammate asked how they managed tag and code qualitative data (transcripts, notes, videos) with consistent taxonomy.”

The FullStory Digital Experience Analyst

A product analyst or UX researcher at a digital product company who uses FullStory as their lens into the user experience. They don't just look at funnels and conversion rates — they watch sessions, identify frustration signals (rage clicks, dead clicks, error clicks), and correlate behavioral patterns with business outcomes. They've learned to find the story in the data: why conversions dropped, where users get confused, what makes the checkout feel broken. They are the translator between raw user behavior and product decisions.

“The product team sees a 15% drop in checkout completion after a recent redesign.”

The Midjourney Visual Creator

A creative professional — designer, art director, marketer, or content creator — who has integrated Midjourney into their production workflow. They don't generate random images for fun; they craft prompts with precision to produce specific visual outcomes: hero images for landing pages, mood boards for brand development, concept art for product pitches, and social media visuals. They've developed a prompt vocabulary that gets consistent results. They understand that AI art isn't "pushing a button" — it's iterating, refining, and curating from dozens of generations.

“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about consistent brand characters and specific product representations are still unreliable in two weeks.”

The Contentful Headless CMS Developer

A frontend or full-stack developer who integrates Contentful as the content backend for a website, app, or digital experience. They set up the content models, build the delivery layer, and create the bridge between what content editors want to publish and what the frontend can render. They appreciate the API-first approach but have learned that "headless" means they're responsible for everything the CMS traditionally handled — routing, preview, caching, image optimization. They build the head.

“A marketing team wants to launch a new campaign page type.”

The Maze UX Research Automator

A UX researcher or product designer who uses Maze to test prototypes before they go to development. They run unmoderated usability tests where participants interact with Figma prototypes while Maze captures click paths, task success rates, and misclick patterns. They chose Maze because moderated testing doesn't scale — they can't schedule 50 individual sessions for every design decision. They need data, not opinions, and they need it in days, not weeks.

“A teammate asked how they managed test prototypes with 20–100 participants without scheduling individual sessions.”