[{"data":1,"prerenderedAt":132},["ShallowReactive",2],{"blog-en-onboarding-in-six-sentences":3},{"id":4,"title":5,"body":6,"cover":116,"date":117,"description":118,"draft":119,"extension":120,"locale":121,"meta":122,"navigation":123,"path":124,"seo":125,"stem":126,"tags":127,"__hash__":131},"blog\u002Fblog\u002Fen\u002Fonboarding-in-six-sentences.md","An onboarding in six sentences",{"type":7,"value":8,"toc":107},"minimark",[9,13,16,19,24,27,30,33,39,43,46,49,52,55,59,66,69,72,75,79,82,85,88,94,98,101,104],[10,11,12],"p",{},"The first thing meetre says to you is \"Hi.\" Two letters and a full stop, white, big, centered on a dark screen with a sparkle above it. Then, about two seconds later, it says \"It listens.\" Then \"It writes it down.\" Then \"And it stays on this Mac.\" Then \"Let's set you up.\" At the very end: \"You're set.\"",[10,14,15],{},"That's the whole script. Six sentences, and one of them is a greeting.",[10,17,18],{},"I spent more time on those six lines than on some entire features, because onboarding is the only moment where an app gets your full attention. You just installed it. You're curious. You haven't formed an opinion yet. Whatever it does in the next forty seconds becomes the opinion.",[20,21,23],"h2",{"id":22},"one-line-per-scene-never-a-paragraph","One line per scene, never a paragraph",[10,25,26],{},"The rule in meetre's design book is blunt: one short line per scene, never a paragraph. Most onboardings I've clicked through try to explain the product. Feature lists, carousel dots, \"Swipe to learn more\". By the third slide I'm hunting for the skip button, and I'm the kind of person who reads release notes for fun.",[10,28,29],{},"meetre doesn't explain. It sets a tone. \"It listens. It writes it down. And it stays on this Mac.\" is the entire pitch, and the third line is the one that matters, because privacy is the reason the app exists. If you only remember one thing from the first launch, it should be that.",[10,31,32],{},"The type is SF Pro Rounded, semibold, somewhere between 40 and 96 pt. That's the only place in the whole app where rounded display type is allowed. Everywhere else it's plain SF Pro at system sizes. Keeping the softer face for this one moment makes it feel like a greeting instead of an interface.",[34,35,36],"blockquote",{},[10,37,38],{},"Onboarding doesn't teach anyone how to use your app. It decides how they'll feel about using it.",[20,40,42],{"id":41},"pacing-you-can-skip","Pacing you can skip",[10,44,45],{},"Scenes advance on their own, each staying between 1.7 and 2.4 seconds. Click, Return or Space skips ahead. Transitions are a soft scale plus fade over 0.7 seconds, and with Reduce Motion turned on it's fades only.",[10,47,48],{},"Auto-advance is risky. Too fast and people miss things, too slow and it feels like a hostage video. The fix was to make every line short enough to read in under a second, so the timing is really about rhythm, not reading speed. And because skipping is always one keypress away, impatient people (hi) never feel trapped.",[10,50,51],{},"Behind the words there's a mesh-gradient aurora in indigo and violet, with a hint of green in one corner, drifting very slowly. It stays at or below 55% opacity, which is the difference between atmosphere and a screensaver from 2009. You notice it on the second scene rather than the first.",[10,53,54],{},"There's sound too, and only here. Soft synthesized bells, a rising arpeggio on hello, a single note per step, a barely audible tick on hover. The everyday app is completely silent. A mute button sits bottom right, and nothing is louder than about −5 dB, because the worst possible place for a startling chime is the start of a call.",[20,56,58],{"id":57},"permissions-that-say-why","Permissions that say why",[10,60,61],{},[62,63],"img",{"alt":64,"src":65},"meetre onboarding screen titled \"Two quick permissions.\" with a hand icon, two rows for Microphone (your voice) and System audio (the others) both checked green, a note explaining macOS calls the second one Screen Recording, and a Continue button","\u002Fimages\u002Fblog\u002Fmeetre\u002Fonboarding-permissions.png",[10,67,68],{},"Here's where most Mac apps lose people. macOS calls the permission for system audio \"Screen Recording\", which is technically correct and terrifying. You install a meeting transcriber and it immediately asks to record your screen. I'd say no too.",[10,70,71],{},"So the permission scene names both permissions in human words. \"Microphone, your voice.\" \"System audio, the others.\" Underneath, one small line: macOS calls the second one Screen Recording, meetre only keeps the sound. Each row gets a green check once granted. Then one button: Continue.",[10,73,74],{},"That small line probably does more for trust than the whole privacy section of the README. It answers the question at the exact moment you're asking it.",[20,76,78],{"id":77},"never-show-the-logs","Never show the logs",[10,80,81],{},"The setup itself happens on one glass card. At most five toggles, each an icon and a few words. One prominent capsule button that says \"Install\" or \"Set up\". The on-device line underneath. If an option needs more input (like a Hugging Face token for splitting multiple remote speakers), the field reveals itself inline instead of opening another screen.",[10,83,84],{},"Then the models download, which takes a while, because there are several gigabytes of them. The progress is a ring with a slowly turning sparkle and one line of text that changes as it goes. My favorite is \"Downloading the brain.\" It is, technically, a language model. It is also, emotionally, the brain.",[10,86,87],{},"What you never see is a log. No scrolling terminal output, no pip warnings, no \"Collecting torch\". If something fails you get one sentence, the last error line, and a \"Try again\" button. Logs are for me, and they're one click away in Settings when you need to send them. During a first launch they're just noise that says \"this might be broken\".",[10,89,90],{},[62,91],{"alt":92,"src":93},"meetre onboarding final screen reading \"You're set.\" with a pointer toward the sparkle icon in the menu bar","\u002Fimages\u002Fblog\u002Fmeetre\u002Fonboarding-done.png",[20,95,97],{"id":96},"ending-with-a-direction","Ending with a direction",[10,99,100],{},"The last scene says \"You're set.\" and points at the ✦ in your menu bar. That's on purpose. meetre doesn't have a dock icon you'll stumble over. It lives up there, quietly, and if the onboarding doesn't show you where, you'll close the window and wonder where the app went.",[10,102,103],{},"Every onboarding should end by pointing at the next thing you'll actually do. Not a \"Get started\" button that drops you in an empty dashboard. A direction.",[10,105,106],{},"Six sentences, a few soft bells and one honest line about Screen Recording. I've shipped features that took weeks and said less.",{"title":108,"searchDepth":109,"depth":109,"links":110},"",2,[111,112,113,114,115],{"id":22,"depth":109,"text":23},{"id":41,"depth":109,"text":42},{"id":57,"depth":109,"text":58},{"id":77,"depth":109,"text":78},{"id":96,"depth":109,"text":97},"\u002Fimages\u002Fblog\u002Fmeetre\u002Fonboarding-hello.png","2026-10-15","meetre's first launch says \"Hi.\" and then barely anything else. On short lines, auto-advancing scenes, a slow aurora, permission screens that explain themselves, and why an installer should never show you its logs.",false,"md","en",{},true,"\u002Fblog\u002Fen\u002Fonboarding-in-six-sentences",{"title":5,"description":118},"blog\u002Fen\u002Fonboarding-in-six-sentences",[128,129,130],"UX","Onboarding","Motion","T-ToSlOUJOfAbuvMUmpa0QKloUMSorHx3JS0d1_s8D4",1792165382772]