# 🐨 Fibery Product Report: September 2025

**URL:** <https://community.fibery.io/t/fibery-product-report-september-2025/9784>\
**Category:** News & Announcements\
**Created:** [October 10, 2025, 3:07pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784 "2025-10-10T15:07:20Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [October 10, 2025, 3:33pm UTC](https://community.fibery.io/t/fibery-product-report-september-2025/9784/4 "2025-10-10T15:33:49Z")

</div>

> [@mdubakov](#):
>
> Notion AI works quite fast and nice

Thinks fast, acts slow. Tried adding 200 sample items it did it one by one. Tried then updateing those 200, but because only 50 were loaded on screen it only saw 50 and only updated those… one by one…

Fibery: Thought for longer, acted much faster.

While adding sample data is niche, I do have a client that throws in meeting notes, and it makes all the tasks, so this in general about working with data in bulk. Fibery AI \> Notion AI.

> [@mdubakov](#):
>
> Generalize context filters into dynamic values

Exciting! Maybe using formulas…? Or even just the lookup arrow like with other filters “This PA \> Assignees”

> [@mdubakov](#):
>
> Files field

So looking forward to this one!!

> [@mdubakov](#):
>
> I’ve been thinking about making File a proper Database, but it seems we should wait till Core will be free and happy again, and maybe then we will start _Global Databases (Documents, Users, Tasks, Files, etc.)_. Then we will maybe migrate Files to proper entity, but not now.

Would love it to be a files database in some future, but also sharing thoughts that I’m scared of the “Global Databases”. Users and Files make sense as global as they are fundamentally different. But not all workspaces use Tasks or Documents, so having them as templates, and anyone can add or remove custom databases to global databases would be more ideal imo.

Also, maybe different workflows need files for different things, so you’d then have separate files databases for different use cases and relationships. Lots to think about

> [@mdubakov](#):
>
> I’m working on templates

If [whiteboard were fields](https://community.fibery.io/t/split-whiteboard-view-to-a-canvas-field-and-a-network-view/8687), you could have templating work in the same way as it does with entities. “Templates” database, and when entity linked to template, overwrite the the whiteboard field with the template’s whiteboard field data. I’m standing my ground on this one haha.

Whiteboards are getting more and more separate from the Fibery ecosystem and I’m worried it’ll be harder to bring them in later. Not sure where the data for the whiteboard templates will live…

> [@mdubakov](#):
>
> Mobile

Looking forward to this!! I think it will make it much easier to get buy in. I’ve heard it be a must-have a few times.

---

_[View the full topic](https://community.fibery.io/t/fibery-product-report-september-2025/9784)._