Q: What are your top 3 missing things/features in Fibery?

BTW, what are your top 3 missing things/features in Fibery? :slight_smile:

For me:

  • entity-level permissions
  • customizable entity views and Dashboards (Blocks?)
  • better support for scripts, e.g.:
    • debugging
    • code reuse (e.g. modules or libraries)
    • more high-level API functions (e.g. “duplicate an entity”)

…and more:

  • more-polished and consistent UI (e.g. better keyboard and focus handling)
  • more-functional Table view, with a more “spreadsheet-like” experience
  • some kind of polymorphic type support

Now that we have a lot of power in Automations, buttons, etc. to do notifications, reminders, etc. I am mostly good on needing additional “functionality”/features. I consider the above 3 to be more about making Fibery into a more “bespoke” system that is more deeply customized to my needs, allowing my users and I to focus on what is important to us, to document as much as we want without it getting in the way when we don’t, e.g. alternate layout views, not having to have a relation field for every possible related type but using polymorphic and a single field to represent certain kinds of relationships much more cleanly, etc.

The one additional priority I’d add would be improvements to the Notifications, I think. I would want an entire page/screen dedicated to this, and/or maybe even a special Block type so I can embed a (optionally filtered) notifications view in any page (ooo). It should show more info and be more sophisticated in general. And/or perhaps some aspects of a “my work”/“my view” would meet the same need as well or better…

I would also love some more spreadsheet-like functionality in Table views, as @Matt_Blais suggests, though it doesn’t quite make it into the top 3 for me.

1 Like

Can I also share my top 3?

  • to be able to insert different views inside docs to build our own dashboard / overviews
  • being able to customize the view of an entitty and how data is presented there. Migrating entity views to blocks might help us do that? A very simple ex… i have some project entity and when I open it I want to see the description, a timeline and below a table view (which is much more readable in many cases than the simple card view used currently) of some tasks
  • allowing guest users to edit/submit data + native forms. The main reason for this is that I want to use Firbery in as many areas as possible, like hiring (let people submit applications) or user feedback (let users vote and discuss features). I know that some can be implemented by using Zapier plus some other app, but I don’t like to use more 3rd party apps. I don’t want to use Typeform for every form submission or some feedback app when 90% of features are already inside Fibery.

Extras i would love

  • Show image in some summary view, like the Kanban view.
    For us it would be incredibly useful if we could just paste image from clipboard (Windows+Shift+S → CTRL+V). Attachment extension is nice and we use it, but not well suited for “featured image” (?) and pasting from clipboard. We would use it with our in-office customer to show a high level overview over their orders, and they want to see the images they’ve selected (which we just screenshot and paste in). As it is now we’d have to go into each entity.
  • Usability on mobile and touch devices. Former I have heard from several people, because Trello can (even have their own app I think?), and they want to add stuff to the Workspace when they’re on the fly and think of stuff. For touch device it would be nice if we could use it in the office here on a tablet to go over orders we have laying around.
  • Publicly share a view with just a link. I want to show people development process. There should have to be some restrictions on opening up entities though, because I selectively show fields in my view. Some fields and their values are not meant for others to see.

Of the most pressing, which is really upsetting:

  • “Archive” status for Entities at the level of the system core.
  • Filters for Relations.
  • Extended Table view (grouping, batch edit, etc).

Other functions, the absence of which can be tolerated for now:

  • Limited functionality of Document (not as in Notion: 0)
  • “Action Center” as a separate custom object. Very conveniently implemented in Planfix. And people have already given examples above.
  • Limited comment functions.

I listed what was not indicated in the roadmap in the near future.

But it should be borne in mind that I have collected little statistics on work cases so far. The second part of the list can change dramatically.


+1 for Extended table view

1 Like
  • Form view
  • More robust views/cards (e.g. Improve and Expand Card Layout Across Views. Fibery’s views are just not as useful and polished as other services out there. Especially the timeline and calendar views)
  • A personalized space: Clickup as a whole has much better personalization (view configuration, etc) and a spot where you can see all “your” stuff you are working on, coming up, etc

I have to agree with @Oshyan 's list and the sentiment that I am hoping that a few foundational features are added that can then allow building more interesting things on top.

  • Blocks: to enable embedding of views, entities (in-line or as blocks) which will really help with generally being able to reorganize entity views and creating things like dashboards. I am hoping that this is also supported in markdown templates (i.e. you are able to insert view blocks into entities when they are created using rules with parameters defined at creation time)

  • Polymorphic relations: that is consolidating relation fields so that every relation (even those that are rare/occasional) don’t have to be explicitly defined. I am also hoping this would include adding properties to relations. I think this makes fibery’s relations truly graph-like and allow things like building knowledge systems or even building a very powerful CRM or contacts graph where you are interested in connections between people but also how they are are connected)

  • Improvements to table view: this includes grouping and aggregate/rollup functions, searching & temporary filtering (i.e. for quick lookup of current data without permanently changing view filters), and some more rendering options for URLs and rich text fields.

I tend to group things that in my mind go together or seem to require consideration together even though they might considered distinct features so apologies if I crammed more than 3 things above.

As far as other items:

  • Search improvements: this includes search & replace (for simple text & for entity references), extending search to other fields, scoping, setting filters (e.g. for closed items), and providing more context in search window.

  • Geospatial field types: this is not a priority for anyone but it remains a pain point for anyone dealing with physical world (construction, real-estate, architecture & engineering, retail, etc.). Even possibility of having json fields that at least check json formatting would be a good start.

  • Plugins/extensions/custom blocks: to allow users to create some features that are not priorities for fibery core. I understand this has to be done very carefully so just adding it as a consideration when building some of the underlying things like block to enable this in the future. One use case for me is implementation of a map view/block using leaflet (related to above).

Thanks again for all the hard work. It is amazing what has been accomplished to date :grin:


For now,

  1. Pinned column (table view)
  2. Much easier way of adding rows to a table (the one inside a document or a rich-text field)
  3. Sorting Rules in the Configure App window
1 Like

I agree 100% on your list!

If only three then

  1. Hiding fields from the entity view/permissions level for certain fields
  2. Pinned Columns in Table View
  3. More robust/intuitive formulas for handling the combination of text and data fields
  1. Form view
  2. Form view
  3. Form view


This is the only thing left that makes Airtable better than Fibers and the only thing that forces me to use third-party solutions, which is far from efficient.
take care


We have Form View in our plans for the next several months. We heard a lot of similar feedback and decided to prioritize it higher.