Skip to main content


Whatever you do: For me it is important to keep the user name, since I switch between different accounts. For the spacing: As long as it still works on narrow displays, I'm fine with everything.
And the avatar image isn't enough for you to tell which account you're logged into?
I'm not a very visual guy. Also I use a bunch of test accounts where I don't care about the avatar and mostly use the same one.

Occurs to me I could just drop the user name to the second toolbar, there's plenty of space for it there:

Proposed Toolbar 3

On narrow screens the username text goes away because it switches to the mobile slide-in menu, which has the username as the first item.

I could also just disable the desktop user menu and enable the mobile one for all screen sizes.

(As a side note I've noticed there are quite a few UI elements that are duplicated - one for the desktop layout and one for mobile. I'm assuming that's because Frio predates just using media queries to make a responsive layout restyles a single menu).

@Random Penguin Oh, Frio uses media queries alright, but it often has completely separate elements for desktop and mobile views, which explains the duplication.
It seems like the media queries were grafted in later on. Using server-side PHP detection for mobile devices and selectively enabling/disabling UI elements and swapping stylesheets was how we did it back around 2010 before media queries were a standard. IMO Frio needs to be streamlined and updated so it uses a responsive layout with just one set of UI elements. But I don't want to do it. That's why I'm working on Booklook and why its starting point is Vier.
I've got one wish: When you move stuff around, please have a look for aria elements or navigation elements that are only there for screenreaders.
What is your specific concern? That they end up out of tab order? That hidden things don't get read?
My only concern is that whatever is done, screenreaders should still work like before.
The only way I have to check that is with VoiceOver, which I do, and I've only noticed the two issues I mentioned. From CSS I can't do anything about the order of aria elements or properties in the HTML code.
Thanks for checking with VoiceOver!

Today I noticed that VoiceOver seems to be broken. It was working fine before the macOS 15.7 security update. Now it will only read and navigate to links and form elements. It skips over any static text. Quick look in Apple forums and it seems it's also broken in Tahoe.

I guess I'll have to fire up one of my old Macs that's stuck on an earlier macOS version when VoiceOver still worked.

Nowadays with Apple software quality in decline combined with their poor or rather non-existant documentation of internal changes debugging such changes is a serious pita. πŸ™„

What facebook does looks like good UX. Logo then search, then the different icons with more spacing. It is not by accident that they only show 5 icons in the middle and move less used options to the right side. That is such a sweet design, I'd love if it Friendica could adopt it.

As for the username: wondering if that could default to off and an covered by a setting which allows showing username in 2nd toolbar as suggested? I love the cleaner look which gives a better structured overall feeling. Even wondering if "Search" is sufficient for the search field. Users are likely aware they can also search names and hashtags etc.

My screenshots are Friendica 2024.12. Instruction text appears in a tooltip when you focus on the input. In 2026.01 that text is in the field: "Search: @name, !group, #tags, content"

Personally I don't like it. I think it looks cluttered. The text doesn't fit in the field in pretty much any language. And how much hand-holding do we really need to do with a search field these days?

Nonetheless, part of this update will also expand the Search box on focus so all the placeholder text is visible. At least on the desktop layout. There simply isn't space on mobile. Which is why I don't see the point of having anything other than the word "Search" in there. But the only option I have in CSS is to hide the placeholder text entirely.

#tags
Wouldn't the easiest solution be to change the translatable string to just Search? Would that be possible @Michael πŸ‡ΊπŸ‡¦ ?
Which would change it back to how it was. Somewhere between the 2024 and 2026 releases the translatable string got moved from the tooltip into the placeholder. I don't know why.

There were a few changes in regards to the search box and tool tip. I am not sure, but the idea might have been to add the tool-tip to the search box and remove it. Also back then "Search" did show twice which was odd. This was when instead of showing a spotlight icon there still was a search button, so showing search seemed redundant.

We are now in a much better and mature place so it is fair to do another adjustment.

My two cents (well, three):

If Facebook had notifications in the center - and Friendica moved that to the far right, I believe it would cause confusion for people accustomed with Facebook. But since Facebook has it at the far right already, I don't think it will be bad to move it to center in Friendica - where it would be more identifiable.

As for spacing, I like the more condensed look with less white-space.

And finally - I also think it is a good idea to keep user name - maybe below the avatar.

... and let me thank you as well. What you have done here is absolutely amazing for Friendica. I truly applaud your work ... even though you have mentioned in another post, that it has been quite challenging.

β€οΈπŸŽ‰πŸ™

I really like the last version with notifications to the right and the username below the avatar, and for the same reason as Michael: Different accounts with the same avatar image.
Loving the solution you came up with. This looks fantastic. Been wondering: would it make sense to make the username a link and clicking it opens profile? That could replace the profile entry from the drowdown listing. Wdyt?
Nope. It's part of the button that opens/closes the menu. To turn it into a link would require changing the HTML. I can't do that from a scheme, all I have to work with is CSS.

If Notifications opens another tabbed view, I’d prefer it stays where it is, otherwise, open to a dropdown menu on the far right. I’ve still yet to commit to serious Friendica use, so take my feedback with that in mind.

I’m so pleased you’re still working on this. πŸ™‚

No worries, it will still be a dropdown menu.
⇧