Bug 166588 (First_Launch_Welcome) - Meta: new Welcome / First launch dialog fine-tuning suggestions / feedback
Summary: Meta: new Welcome / First launch dialog fine-tuning suggestions / feedback
Status: NEW
Alias: First_Launch_Welcome
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
25.8.0.0 alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsUXEval
Depends on: 166545 166591 166593 166594 166595 166596 166600 166543
Blocks:
  Show dependency treegraph
 
Reported: 2025-05-15 10:34 UTC by steve
Modified: 2025-05-15 22:05 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:


Attachments
2025-05-15 tab 1 whats new (1.34 MB, image/png)
2025-05-15 10:35 UTC, steve
Details
2025-05-15 tab 2 user interface (183.72 KB, image/png)
2025-05-15 10:35 UTC, steve
Details
2025-05-15 tab 3 appearance (127.70 KB, image/png)
2025-05-15 10:35 UTC, steve
Details
example for a good theme selection (27.68 KB, image/png)
2025-05-15 10:35 UTC, steve
Details

Note You need to log in before you can comment on or make changes to this bug.
Description steve 2025-05-15 10:34:47 UTC
Description:
A new dialog to help users setup their toolbar and appearance has recently been added in https://bugs.documentfoundation.org/show_bug.cgi?id=137931

This is a nice and needed improvement to inform new users about available toolbar options and get them to feel at home in LO just the way they like it.

Here are some fine-tuning suggestion / feedback for which I don't have the capacity to file one bug per minor UI problem. While each individual feedback issue may seem minor, I still think in the sum they show, that there is still room for improvement and at least some issues should be addressed prior to a rollout in a stable release.

Steps to Reproduce:
Look at new setup dialog. Screenshot attached.

Actual Results:
1. First tab does not support dark mode: I'd expected this dialog to support light and dark mode. For dark mode that means: white font on dark background. Currently there is a large white space, which looks alien in dark mode.
2. back button: while each tab allows to move forward via the "Next" button, there is no "Back" button. Tabs can be navigated by the top, but again, if there is a "Next" button, users will also expect a "Back" button. The logic goes both ways.
3. "What's New" tab name: what does that mean? This is not about changes in LO. What's New is not a good title for a welcome text. "Welcome" would better convey what that tab is about.
4. What's New tab has a "Credits" button. That is out of place at that location. About screen has credits link and that's where it belongs.
5. The image in first tab looks grainy. Would it help to either improve the image if possible or make it a tad smaller in order to reduce level of grain? Or maybe use the new revamped iconset instead which have a more modern look?
6. User Interface tab: Currently the toolbars are titled "Options" and the preview is titles "Preview. But are those headlines really needed? Why not use a single headline and call that entire section "Select a toolbar layout". This describes what actually is going on.
7. The description text of each toolbar option could be a light grey instead of white (in dark mode) or a dark grey instead of black (in light mode) to take away focus. Not sure if this is defined somewhere in design spec for LO. It is just a description after all and the preview is great to learn about the selected toolbar style. Using such details helps users to focus and what is important. The text is still there but takes less focus resulting in emphasis on Toolbar options and preview.
7. Appearance: the two colums are not aligned. The entire dialog looks rather unorganized. Instead of the current somewhat convoluted interface, just showing three Theme options: Light, Dark, System with a radio button would make a much nicer UI. A screenshot of how musicpod app presents its theme selection is attached. May I suggest to just call that headline "Theme" instead of "LibreOffice Themes". Users are very aware that they just opened LibreOffice app.
8. use a similar approach for Customizations. The current UI is a great way to raise user frustration. Not everybody is an arch user and enjoys tinkering with complex settings.
9. If possible (and it seems to be the case already on macOS) the changes should be immediately be reflected in the app UI. Should that be possible on all OSs then there is no point in having the "Apply" button.
8. Dialog title "Welcome To LibreOffice.": Giving users a warm welcome is great and I understand the sentiment. But the dialog title is not the correct place for that. If you want to welcome them, do this in the text used for the first tab. The dialog title should be descriptive of the dialogs content, e.g. "Look and Feel" would be appropriate for this setup dialog. Also please don't use a dot at the end of the dialog title e.g. "Look and Feel."

Expected Results:
More fine-tuned dialog to give users the feeling, they are appreciated and some thought went into how LibreOffice presents itself on its first user interaction with new users. This may seem like a detail and there is so much else to do. But please don't underestimate the impression such a welcome dialog gives and which feelings it invokes in your users.

Thanks for considering.


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 25.8.0.0.alpha1+ (AARCH64) / LibreOffice Community
Build ID: 901e160d2ea863af71c180980a76a81ec03b6b65
CPU threads: 12; OS: macOS 15.5; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 1 steve 2025-05-15 10:35:03 UTC
Created attachment 200823 [details]
2025-05-15 tab 1 whats new
Comment 2 steve 2025-05-15 10:35:16 UTC
Created attachment 200824 [details]
2025-05-15 tab 2 user interface
Comment 3 steve 2025-05-15 10:35:28 UTC
Created attachment 200825 [details]
2025-05-15 tab 3 appearance
Comment 4 steve 2025-05-15 10:35:38 UTC
Created attachment 200826 [details]
example for a good theme selection
Comment 5 V Stuart Foote 2025-05-15 10:50:08 UTC
Good feedback...
Comment 6 steve 2025-05-15 11:18:03 UTC
(In reply to V Stuart Foote from comment #5)
> Good feedback...

... except for the odd numbering 🙈
We really need an edit option.
Comment 7 V Stuart Foote 2025-05-15 11:37:09 UTC
(In reply to steve from comment #6)
> (In reply to V Stuart Foote from comment #5)
> > Good feedback...
> 
> ... except for the odd numbering 🙈
> We really need an edit option.

No don't worry about two 8.'s --a non-issue. We knew you'd have input coming from bug 137931, 

https://bugs.documentfoundation.org/show_bug.cgi?id=137931#c68

Bugzilla can be a little harsh when editing, my "favorite" is losing any comment write-up when someone else posts to it first, back -> copy -> paste external, try to remember get any of the meta fields and the start again ;-)
Comment 8 V Stuart Foote 2025-05-15 11:42:07 UTC
@Eyal, do you want to work up your UX comments from bug 137931 here as well, and we can make it a meta of items for the new Welcome/First launch configuration dialog?

Individual tasks/items them go to this as "Depends on".
Comment 9 V Stuart Foote 2025-05-15 11:55:44 UTC
To revisit the Welcome/First launch dialog... adjust user profile:

From https://bugs.documentfoundation.org/show_bug.cgi?id=137931#c74

The new Welcome dialog works on Windwos os/DE builds. Just not for the general soffice.exe launch, and it has to be with launcher for one of the modules.

(In reply to Eyal Rozenberg from c#70)

> neither in the start center nor in Writer. Removing the
> ~/.config/libreofficedev directory worked :-(

Yes that works, or you can just delete the registrymodifications.xcu

Though can be a bit more precise and just toggle the FirstRun stanza from 'false' --> 'true', found in the .xcu as:

<item oor:path="/org.openoffice.Office.Common/Misc"><prop oor:name="FirstRun" oor:op="fuse"><value>false</value></prop></item>
Comment 10 Heiko Tietze 2025-05-15 13:06:58 UTC Comment hidden (off-topic)
Comment 11 Buovjaga 2025-05-15 15:26:34 UTC
Alright, I moved the issues to separate tickets, except for this one:

(In reply to steve from comment #0)
> 9. If possible (and it seems to be the case already on macOS) the changes
> should be immediately be reflected in the app UI. Should that be possible on
> all OSs then there is no point in having the "Apply" button.

Bug 156855 comment 17 at least mentions this.