This post contains major unsolved problems in Fibery from product side. Some of them are in progress, while most are not and will be in our focus in near future. The list does not includes relatively trivial problems that we know how to solve, like Required Fields or Mobile.
I just want share it to give you a glimpse of what we will be focusing on in 2025. Please note that all these plans are just⊠plans. Reality can (and will) correct them.
In Dev: Permissions & Sharing
While we have a conceptual solution and will implement it soon, there is still a lot of work around UI and setup simplification. Also information sharing is still a huge problem, so it is impossible to build public-facing solutions in Fibery like HelpDesk portal or even share views.
In near (Q1-Q2 2025) future we will deliver:
- Share Entities with Groups
- Share Databases with Groups
- Configure access to Users
Some problems has no we well defined solutions (yet):
- Canât hide information from Admin (and Private Databases)
- How to build Service Desks (Feedback Portal)
- How to share View s
In Dev: Structures in left sidebar
Left menu setup is far from ideal. It does not work well for large companies, spaces and entities canât be mixed, space setup mode breaks the flow. There is a hope to solve many problems in nearest future. Here is what we want to release in Q1 2025.
- Nested Spaces (and make Spaces optional, so it will be possible to mix Spaces, Views, Smart Folders on a top level)
- Separate âMyâ from âAllâ in the sidebar and disable DnD for usual users
- Show Databases in left sidebar and remove Space setup
Near future: Dependency management
Dependencies are important for any complex processes related to projects and product management, so it impedes Fibery adoption in various domains and a show-stopper for some use cases.
We are going to focus on this after major core permissions changes. Likely Q2 2025. It will include at least:
- Dependencies in domain between entities and some rules to change dates automatically
- Timeline View dependencies visualisation (and maybe other views as well, like Whiteboard or even Board)
Near future: Multi-relations (Polymorphic)
What is Polymorphic relation?
- each end of a relation can hold Entities of different Databases.
Invoice â(Invoices)ââ(Paid By)â Client, Partner
- polymorphic relations can be of any cardinality, including one-to-one:
User â(User)ââ(Profile)â Employee, Freelancer, Contact
- polymorphic relations can include self-relations as well:
Issue â(Blocks)ââ(Depends On)â Issue, Incident
Weâve added them for Highlights already, and it works well. Next step is to add them to usual databases. This feature is maybe important for Global Databases as well, since we want to link Documents to many different Databases. However, current limitation of 6 entities maybe not good enough.
Next: Global Databases
Some databases are quite generic (global), like Docs, Tasks, Events, Meetings, etc. Global Databases can live in the root Space after Spaces redesign. In most cases they need multi-relations, but we can try to handle it via weak relations (Comments is an example).
Next: Documents as View â Document as Global Database
Weâve made a mistake from the beginning and modelled Document as a View. It was the fast way to do it, but it caused a lot of limitations and problems. Now we have two options to create wikis and people get confused.
We will fix this mistake and make Document a proper database (Global Database).
Other conceptually unsolved problems (but less important⊠maybe)
It is unlikely that we will take these problems in 2025, but some improvements are possible here and there.
- Near-sync communication (Chats, Comments, Thread View, etc)
- Context empire (smart folders, dynamic filters, etc)
- Dates as Databases. There are many problems with date as a simple field representation, like lack of grouping, poor visualization, etc. It is quite hard to unify dates concepts, but we have some ideas, like create a special integration that will populate databases like Year, Quarter, Month, Date and use relations to entities and these databases.