April 3, 2025 / Inter as the primary font, Fibermoji, some small improvements

Inter as the primary font

We’ve made all fonts the same, using Inter, on every operating system. Now, Fibery looks the same everywhere and we can solve problems with spacing and paddings that different fonts caused.

Fibermoji

April Fun Day was a blast, but it’s time to bring things back to normal. Fibermoji are here to stay, but animations are now off by default, and we’ve toned down their expressions for a cleaner, calmer interface.

Miss the madness? No worries! There’s a new toggle waiting for you under Settings → Preferences. Enjoy a more refined look – or turn the fun back on with a click!

Deactivate user and change email via context menu

Another quality of life improvement: now Admins can activate and deactivate users as well as change their emails from anywhere, not just settings:

The confusing read-only Active? Checkbox is gone now and is only available in filters, colors, and sort.

You can now tell the deactivated users apart by a badge on the Entity View and dimmed font color on other Views.

Next week, we are looking to deprecate standalone user management settings in favor of the more familiar and versatile Database/Entity UI.

:butterfly: Improvements

  • Space setup mode with databases got some updates. We’ve added a visual separator between databases and views, and made New Database and New View actions more visible
  • New button on top of all Views opens a popup now with a form. It is a more consistent behavior, and you can still add new entities inline using inline UI elements. You can also customize what form will be visible by default via this New button click
  • Text Assistant AI model upgraded to chatgpt-4o-latest. It is also possible to use this model in automations for rich text fields via [ai model=chatgpt-4o-latest] your prompt [/ai] tag. This model works way better for many cases

:shrimp: Fixed Bugs

  • Sidebar:
    • Databases are hidden from sidebar by default for new Admins
    • Click on collapse/expand button does nothing for database in search results
    • Proliferation of blue lines on entities drag and drop in sidebar
    • ‘Remove from smart folder’ option should be hidden for sub-folders as it does nothing until parent folder belongs for SF
  • Smart Folders & Context Views:
    • Error in attempt to re-order sub-document in smart folder
    • Can’t drag and drop document to make it nested for another doc
  • Documents / Rich Text: ‘Position out of range’ error on removing column in rich-text
  • Desktop: Can’t drag and drop items in collapsed sidebar in Fibery desktop version
  • MCP Server: Type description is not compliant with MCP protocol
  • Missing color in the “Spectral” color palette
  • Zendesk: Entered zendesk sub-domain with 'http:.." leads to 401 error
  • Table View: Keyboard input: numpad Enter doesn’t create new entity
  • History & Audit Log: Upgrade banner is not displayed in entity history if there are no updates within plan’s timeframe

:love_letter: P.S. We are launching a newsletter for power users like you. Architects Weekly brings Fibery tips, updates, and curated resources straight to your inbox every week.

12 Likes

Can we change the colour for a person in any way other than renaming ourselves? We’ve got a small team and it would be good to choose different colours for everyone while we can.

Note that if you set your own avatar it will go away. It is like empty state icon

1 Like

Fibermoji is just a fun name for placeholder avatars. Please upload real faces or any images you’d like - this approach will be much more scalable :slight_smile:

We won’t be developing this feature further (aside from fixing bugs), but I can share a Figma file here with all the components and colors, so you can create your own Fibermoji

1 Like

These were SO GREAT! Just a nice little touch (like your Anxiety page) that I am so happy you released and that they remain available in the experimental tab!

Many thanks!

4 Likes

I just showed the Anxiety page to a friend as well as the Fibermoji. He loved it, and Fibery in itself as well! :blush: Glad that the Fibermoji stay! Together with the great product that just keeps improving (because of a hardworking and smart team), good communication, amazing transparency and all the other good (sometimes self-deprecating) humor it is just such a joy to be a Fibery user!

Btw do you now do Fibe programming in the team? :laughing:

5 Likes

Love this for improved data input! But while this is more consistent across the workspace, I also already found myself telling people “Just make sure to press the plus button at the top and not the bottom in order to add or else it won’t show the form”. It’s inconsistent within the view itself. I think being able to set the “add new” behaviour per view (If its a form or in line, and what form to use) would be nice. Or the ability to hide either inline additions or the plus button per view? (Even better if it could be per db in view)

The main up-side of the in-line additions is that you set which fields are relevant in that specific context, but instead the form popup uses the same form across the workspace. The inline entity is essentially your “form”.

What if it worked like this (where plus is the same for both in-line and plus button, with the option to set it to open form instead)

No required fields:

  1. Don’t ask for name in order to create. Just create. Make sure its created in view of user or scroll to it. + hotkey when clicking the plus to “create and open” + hotkey to create new below. (explained in tooltip on hover). This way it can be created, then opened in new panel to add whatever fields. If conditional multi-entity views is released this becomes the “form” so to speak.
  2. When entity created focus on the first editable field in order. Whether thats name or other. No editable field in view? Open entity in right panel.

With required fields (not accounting for table view bc thats harder. ideally it uses existing columns, but adding in extra columns for hidden required fields during input might be too confusing or technically challenging.)

  1. Show all editable fields that are visible in view + any required fields to be inputted. Show this in view of where ever the user is scrolled to or scroll to it. This way it does not need to be created, then edited. Allow creation after all required fields are filled. Indicate required with orange border.
  2. Button to create + hotkey to create and open + hotkey to create and add another (explained in tooltip on hover)
  3. Do not sort it yet. As if someone didn’t use the shortcut and then wants to open it and its sorted its a pain to find.

Forms as data input are still missing the dynamic filtering functionality, so any dbs that need this would be bad to create with a form view. The push for form view in add needs to bring form input up to per with in-line input. Finding the way bring the pros of each together would be ideal. As opposed to letting each user choose based on what they need to input.

Also noting that Feed view has no inline ui element to create.

I didn’t see it get any love in the comments yet, so I just wanted to pop in here and say how much I LOVE the new, updated font. The legibility, especially at smaller point sizes, is noticeably better than the previous font. Well done!

I love how you guys are always looking to improve the “little” things that make a big difference :raising_hands:

6 Likes