Q4 2025 Roadmap

Our internal roadmap for Q4. I hope we will do at least 3/4 of it, we are trying to create more realistic plans now :slight_smile:.
:unicorn: - extra-features that we want to take, but unlikely will take.
:red_question_mark: - extra-features we are thinking about and still not sure about

Permissions

We will implement:

  • Share Entity to web via a link using access templates
  • Allow to hide Space data (entities) from Admins
  • Allow not to extend access from Space to its Entities (this feature was planned for Q3, but core permissions re-work took much more time. Anyway, it will be done this quarter)

Unlikely we will take anything else, but other important features in permissions to complete in this theme (Q1 2026 most likely) are:

  • Configure access to Users
  • Add create capability to access templates
  • :unicorn: Introduce custom access templates for Databases access

Whiteboard

In Q4, we’ll focus on deeper integration of Fibery data in Whiteboard, adding embedded views (table, board, timeline, etc.) and improving how entity relations work to make working with data smoother. We’ll also introduce a set of useful templates to help people get started with Whiteboard more easily.

  • Insert views into the Whiteboard
  • Whiteboard: Support all relations
  • :unicorn: Whiteboard: Templates

Mobile

We’ll release the first beta version in October and launch on the App Store and Google Play after that. After collecting feedback, we’ll continue updating the internal parts of the app in later releases.

Simplicity and usability

Many different assorted things will be done here.

  • Use the same Database multiple times in List/Table Views
  • Use the same Database multiple times in Smart Folders
  • Quick Filters where users can change values + personal filters unification

Then something below:

  • Hide “No parent” group in multi-level Smart Folders
  • “No parents” section looks annoying and can’t be hidden
  • :red_question_mark: Hide Tabs and Fields (including buttons) when specific criteria are met (and maybe introduce collapsible groups inside Entity View)
  • Batch drag and drop cards on Timeline & Gantt View
  • Generalize context filters into dynamic values

Files

Files re-work was planned to Q3, but dragged to Q4. Good news is that we already working on it, so no more shifts! Our goal is to make Files great (for the first time) and support all major use cases.

  • Multiple Files Fields per Database (almost done, will be released in October)
  • File unit on Views with previews, add action
  • Download all files from file field and from entity
  • Open/preview file instead of downloading it
  • Gallery View

And maybe some more minor things like

  • :red_question_mark: Sort files
  • :red_question_mark: Add file via URL from UI

AI

In Q4 we will complete migration to Multi-Agent and improve Agent’s speed and functionality. The main goal is to create scalable and performant architecture for new sub-agents. If we will succeed in October/November, we will focus on at least two-more sub-agents (Reports and Whiteboards). Context is also an important part of agent work, so likely we will work on it too.

  • New multi-agent approach
  • Create & Update Whiteboard View with AI
  • :unicorn: Set AI Agent Context (Space, Database, exact Entity, View) via Mentions
  • :unicorn: Create a Report with AI

Automations

We’re going to improve automations based on users requests and our own vision. I hope we will re-think AI + Automation completely. Features we will add initially:

  • Support File Field in automations
  • Duplicate automations to other databases

Then we are not sure, maybe we will work on more features

  • :red_question_mark:Access the previous value for Rules
  • :red_question_mark:Dynamic values in automations (Rules and Buttons)

or maybe we will go for UI re-design, or maybe we will go for full Rules re-design, including server side. You can help us by answering few questions about automations here. Nothing is clear here… This is the most blurry area so far.

8 Likes

Wow! Lots that I’m excited about! And this was a nice surprise:

And also:

This will make things look nicer.

I’m especially excited about the mobile beta and the permissions changes. Thank you!

1 Like

I thin mobile view needs some additional polishing. Mainly top section with entity name. When scrolling we can only see few letters and not the actual name. Maybe hiding icons below some menu like on views would be nice. Looking forward to mobile version :slight_smile:

I completely agree, for now, we are working on the overall behavior of all pages and elements, and later we will improve the elements specifically for mobile devices.

Super excited for these!!!

Question: Will the create ability in access template be able to be given to guests?

I still have my reservations about the term: “Extend” to databases from space. I think the easiest way to explain the issue is that when access to databases is not extended, “Editor” and “Viewer” have the same space access… no? Or will editor now have edit access to views..?

I really think the space access menu needs to be split into view access and database access would make most sense.

Defining access to all views, and defining access to all databases. Then more access can be given per database if that is chosen. My thoughts.

I agree, I have created some great boards but the “no parents” areas that result would be nice to have not visible, would clean up the boards and save space

Already hoping that the files gets to ship first. :slight_smile:

2 Likes

Yay for gallery view update

2 Likes