Q3 2025 Roadmap

[mdubakov]

Our internal roadmap for Q3. I hope we will do at least 2/3 of it
- extra-features that we want to take, but unlikely will take.

Permissions (July-Sep)

Space permissions are about to be transitioned to the new model which finally unlocks these Features:

• Allow to have Databases outside Spaces (in Default Space)
  • Plus, figure out how default Space should work for Guests
• Consolidate default access template names across Space, Database, and Entity levels
• Deprecate Contributor Space access
• Allow not to extend access from Space to its Databases

While waiting for Andrew’s last touches, we’ll help Architects understand who has access to exactly what:

• Show all Users who have access to a Database
• Show all Users who have access to a Space
• Introduce access audit for Users and User Groups

And these would be the two major things left from Permissions scope 2025:

• Configure access to Users
• Add create capability to access templates

Once the theme is not on active development anymore, Anton will produce a bunch of content around access management: guides, tutorials, marketing materials.

Import

Our aim is to make CSV import, by far the most popular way to bring data into Fibery, robust and intuitive. There are no major Features left but there are a lot of smaller things that we’ll prioritize based on the demand:

• Import self-related entities via a single CSV file
• Import Date Range Field from two different source columns

Also, we’ll make it possible to Update existing entities via CSV import—perhaps, via the new Create-or-update (upsert) entity core command.

In parallel, we’ll Make import more discoverable and improve the general UX, regardless of the data source. Most likely, this will include supporting import in our AI builder.

We’ll also polish the 3rd-party connectors used specifically for transitioning from some tool to Fibery:

• Sync Notion standalone Pages to Fibery Database
• Slice ClickUp Tasks into multiple Databases based on Task Type
• Support external relations and People Fields in integrations

is a common and robust workflow to Import or sync Users from another tool.

Mobile

The main goal for the mobile team in Q3 is to launch a beta version, then release version 1.0 of the iOS/Android app for mobile and tablet with an updated design, rich text editing toolbar, push notifications and improved user experience.

Mobile scope:

• Update the view/entity toolbar
• Editor panel for the rich field
• Bottom navigation menu
• Notifications for iOS
• Notifications for Android

AI (July-Sep)

Our main goals here:

1. Build and test new onboarding experience via AI Agent. There is an assumption that it will be an easier way to start using Fibery and shorter time to value. AI getting started (full throttle)
2. Improve Ask agent to be more helpful. So far adoption is moving forward, but numbers are far from great.
3. Maybe explore new frontiers, like build custom UI widgets or full pages in Fibery (time tracking, service desk, etc)

Preliminary scope

• All View types creation: Timeline, Gantt, Calendar, List, Feed, Form, Map
• Set Chat Context (Space, Database, exact Entity, View) via Mentions
• Create a Report with AI
• Create an Automation (Rule or Button) with AI
• Maybe Generate custom UI pages (internal and public) with AI

From a simple Todo App into a full Team Task Tracker in 20 mins (with AI + Fibery)

Some views and UI improvements (July-Aug)

Continuation of simplification team mode for 2 more months. There is an intuitive feeling that it has to be done and internally people also want to do it. So we will do it.

Preliminary scope:

• Specify which Entity View to open based on some field value
• Make User Entity View(s) useful
• Board View Improvements
• Replace many New [Database] actions with a single New action in Table View
• Quick Filters Improvements
• (Not so) tiny UI fixes across Fibery App

Files (~dev starts in July/Aug)

Make Files great (for the first time). Can be considered as a continuation of the polishing/simplification theme as well.

• Multiple files/attachment Fields per Database
• File unit on Views with previews, DnD, etc
• Better UI for files (add file, etc)
• Gallery View
• Ability to open/preview file instead of downloading it

Whiteboard (July-Sep)

Improving Whiteboard as we can with limited resources. Victor helps with History and Undo here, then go to Files area.

• Whiteboard version history
• Make “Undo” work well
• Embed views into the whiteboard (reports, tables, etc)
• Support all relations
• Sections polishing
• Connectors improvements
• Mind Map
• Templates
• AI in Whiteboard

[Michael_Ichter]

I’m excited for this quarter!

[helloitse]

I’m excited for the continued improvements to AI and Import, those will be major value adds for people transitioning to Fibery and teams that use the tool as a primary work tool like mine!
I’m deeply disappointed that the improvements for Q3 don’t reflect more of the issues surfaced by the Fibery UX/UI enhancements thread. Wasn’t it announced that the team is moving on from the prolonged whiteboard sprint? I rarely use whiteboards so I admittedly, don’t know if they were a true sore spot for the platform, but the problems with the calendar and list views are debilitating. The rich text experience is also a death-by-1000-weekly-cuts situation on my team.

It could be that I’m in a silo, but is the whiteboard truly this much more important than other views?

[mdubakov]

@helloitse

It could be that I’m in a silo, but is the whiteboard truly this much more important than other views?

Only 1 developer works on Whiteboard and his only expertise is whiteboard view, so it will be continued.

[Mircea_Braescu]

@mdubakov

Whiteboards - Support all relations

What is this about?

[alex]

@mdubakov

Whiteboards - Support all relations

There are some types of relations (formulas, highlights etc.) that are not currently supported on Whiteboard.

[Mircea_Braescu]

Would it also include fixes for things such as …?

[helloitse]

That’s encouraging.
Alright folks, let’s go double the user base so we can have a full time developer dedicated to all our favorite views!

[njyo]

That’s an exciting Q3! Looking forward to all those improvements!
Thanks for the hard work as always!

[alex]

Unfortunately this is a issue with our rich-text snippet, not a whiteboard-related one. We’ll see what we can do.

[jpajot]

Can’t wait for the files and images improvements! Thank you. The rest is obviously also very exciting: views to be open based on some fields, whiteboards… some good fun!

[jandrabek]

I love it! These plans are incredible.

Do you also plan for improvements to home section or dashboard view development?

[Jean_Jordaan]

@mdubakov

make it possible to Update existing entities via CSV import—perhaps, via the new Create-or-update (upsert) entity core command

Feedback which I gave to a totally unrelated app a few days ago

The import template should accommodate a Source ID column.

Importing items should update items with matching IDs.

For any import, it should be possible to export the corresponding items including both the Source ID column as well as the Fibery ID (read-only) of the item, in order to facilitate a re-import with corrections. (Ignore rows with (invalid) Fibery IDs that don’t match an item in Fibery.)

It should be possible to delete existing items via import, e.g. by blanking all column values but the ID in the import sheet.

[RonMakesSystems]

Really looking forward to what’s to come!

I personally don’t understand the need to create databases outside of spaces. Especially if under the hood its just a Default Space, with preset permissions? It’s for companies that are small and only need one space? It feels a bit like adding complexity where there doesn’t need to be. “Databases live inside of spaces… unless its outside of any space, in which case they are in the default space” I think sticking to a set hierarchy isn’t bad, and adds structure and clarity. The need for views outside of spaces was a patch for the lack of “View access to views in a space without all the data”. But we can not extend db’s, there’s less of a need I think.

With that, I think its a lot more inutive for new users if you split the conceptual understanding of a space to have “Views” and “Data” then instead of “Do not extend database”, its: “How would you like to share views? (View, create, edit, delete access)” and “How would you like to share data? (view, create, edit, delete, share access)”

Then i can give people configurer access to the views, and only view access to the data, for example. It does the same thing under the hood, but I think conceptually it makes more sense for new users. Or else it feels like a bit of a puzzle.

@mdubakov

• Configure access to Users
• Add create capability to access templates

This will make things CRAZY! Really looking forward to it! Really unlocks lots of opportunity.

The views and UI improvements, I’m also really excited for! Just one thing im skeptical about is the “Specify which Entity View to open based on some field value”. I feel like its solving the problem in a hacky, less than ideal way. It means that as I’m editing the entity, it won’t change views, just set what view OPENS then I open the entity. Could it also trigger when the entity is already open to change the entity view?

There’s a lot more in here that i’m really excited for like files, gallery view, better quick filters. These 3 months are gonna be great.

@Jean_Jordaan

The import template should accommodate a Source ID column.

Yes! The import works well when importing one DB, but if trying to import related data, it just doesn’t work… You can add relations, and it will then add them as references, but if those relations have any data, good luck importing it now that the references were already created.

[Chr1sG]

@RonMakesSystems

I personally don’t understand the need to create databases outside of spaces. Especially if under the hood its just a Default Space, with preset permissions? It’s for companies that are small and only need one space?

For people coming to Fibery for the first time, understanding Space as a concept is secondary to understanding Databases as a concept. The simplest workspaces do not need any Spaces, but will always need at least one Database.
Allowing Dbs at the top level makes the learning curve less steep.

Also, some Databases do not naturally live in any single Space, e.g. Documents, Meetings. It’s easier to let them live at the top level than forcing them to fall under ‘Development’ or ‘Marketing’ or ‘Finance’.

[Yuri_BC]

@RonMakesSystems

create databases outside of spaces

I think its may be a transitioning step to make databases independent of Spaces, and refactor the purpose of Spaces.
Spaces were and are problematic from a systems perspective functionality, this has been discussed over the years. For example, a space dictates permissions and it also dictates how the URL of entities look like, moving databases between spaces is very problematic, etc.
I’m not aware of the actual intentions of the current high level system architecture of fibery, but maybe @mdubakov can explain?

[mdubakov]

@jandrabek

Do you also plan for improvements to home section or dashboard view development?

Home page will have few updates

• My Work widget
• Insert/Create View widget
• AI widget
• and maybe some more, but here we less sure

[RonMakesSystems]

@Chr1sG

The simplest workspaces do not need any Spaces, but will always need at least one Database.

I’m not sure I agree. Neither with you or with Yuri haha.

What’s an example of a space with no spaces? Wont it need spaces as it grows? Are you trying to accommodate for small 3 people teams at the expense of a clear structure and hiarchy for the larger teams?

Spaces are the Fibery Equivalent of a Postgres Schema. This allows you to set who has access to create new databases, remove databases. You would still need to be able to set who has access to create databases/remove databases for the Default Space. And you probably dont want that person to be an admin (with billing access). If you give permission access to the top level space, you still need to understand the concept of spaces… It just adds another exception to the structure.

[karthikk_vijay]

@mdubakov

Specify which Entity View to open based on some field value

This is much appreciated!!!

@mdubakov

File unit on Views with previews, DnD, etc

Hoping that you guys allow preview of file in link view like
##Christopher
-profile pic of Christopher as file-