UX Copy Rewrite — Onboarding Flow
LibreOffice:
First-Launch Experience
Analysis and rewrite of the onboarding dialog box that appears on first launch of application on desktop — examining how copy and interface structure fail to optimially orient new users.
The Original
This dialog box appears the first time a user opens LibreOffice after a fresh install. It is the product's first impression — and its first opportunity to introduce the user to the product, or lose them by lack of orientation.
Welcome to LibreOffice!
✕
Welcome
User Interface
Appearance
Options
○ Standard Toolbar
○ Tabbed
○ Single Toolbar
○ Sidebar
○ Tabbed Compact
○ Groupedbar Compact
● Contextual Single
Preview
The Contextual Single interface shows functions in a single-line toolbar with context-dependent content.
What's Wrong
01
The title does nothing. "Welcome to LibreOffice!" is a label, not a welcome. It establishes no warmth, sets no expectations, and tells the user nothing about what they're about to do or why it matters. A welcome should orient — this one just announces.
02
The choice is premature and jargon-heavy. A user who just downloaded a word processor is being asked to choose between "Groupedbar Compact," "Tabbed Compact," and "Contextual Single" before they've opened a single document. These are developer names for UI patterns — not descriptions a new user can act on. Only "Standard Toolbar" communicates anything, adn that depends on what they've used in the past. This allows past experience with other products to set the expectations for the new user.
03
The preview is too small to be useful, and does not provide a screen-wide preview of the options. The point of a preview is to show the user what they're choosing, and giving the user a chance to form their own context, within which they'll be working. A decontextualized three-item menu bar tells a new user nothing about how any of these options will feel in actual use — which is the only thing they need to know.
04
"Apply" and "Next" signal nothing. Apply what? Next to where? There's no indication of how many steps exist, what they cover, how long they will take, or what happens if you just close this dialog box entirely. The user is navigating blind.
05
The tab structure assumes intent the user doesn't have. Presenting "User Interface" and "Appearance" tabs on a first-launch screen assumes the user arrived with a configuration agenda. An agenda that may not have existed until the user was forced by the product to manifest one. This agenda is a continuation of whatever word processing products came before. Where distinguishing itself from other products could be an opportunity, here it becomes a liability. The user's experience is shaped by other products, rather than this product.
The Rewrite
The rewrite collapses seven jargon-labeled options into three plain-language choices, names each by what it does for the user rather than what it's called internally, and adds the reversibility signal that makes the choice feel low-stakes.
Step 1 of 3 — About a minute total
✕
How do you want your toolbar to look?
Pick what feels right — you can change this any time in View → User Interface.
Classic
A traditional toolbar across the top. Familiar if you've used Word or older LibreOffice.
Tabbed
Tools organized into tabs by task — like Microsoft Office's ribbon layout.
Minimal
Just what you need, when you need it. More writing space, fewer distractions.
Not sure
We'll use Classic for now. Easy to change later.
What changed and why: Seven options became four — three real choices plus an explicit "not sure" that removes the pressure to decide, with guidance on changing later. Labels name what each option does for the user, not what it's called in the codebase. "You can change this any time" converts a commitment into a preference. The step counter ("Step 1 of 3") makes the process legible, finite, and chronological. "Skip setup" gives the user an exit without forcing them through something they didn't ask for.