Realising I never added an official request for this. And I feel like it’s not being heard or not understood. I’m onboarding an organisation into their Fibery Space, and am finding myself telling them not to use Docs or Whiteboards. This is unfortunate because it has a lot of potential to be something really outstanding.
I feel that you guys tried to mix two things into one solution (network view + drawing canvas), making it bad at both. Let me explain:
View (Network):
A view shows existing data in certain ways. It does not have any data itself. Just the description and icon. Yes, you can multi-insert cards into a whiteboard in order to for it so act like a view, but you can also reference multiple entities in a rich text field for it to act like a list. It doesn’t make it a proper list view!
When you add new items to the database, they don’t automatically show in the whiteboard view (as they would in other views). You can’t filter or color code (as you would in other views). And deleting from a whiteboard doesn’t actually delete the entity, just deletes the reference (unlike other views). Whiteboard acts badly as a view.
Canvas (Containing knowledge / Data)
A whiteboard can contain images, text, etc inside of it. You can write business plans in a whiteboard, take meeting notes. But right now doing that is a really bad idea! Why? The data in a whiteboard is black box, you can’t search for it when search across the workspace, and so I also guess it isn’t indexed by AI (not sure if this is right though).
And the location of this data is also unclear. The whiteboard can be connected to an entity by adding a whiteboard field to a database, but its quite clunky and can easily be accidentally moved to another entity or unlinked if not careful.
And it doesn’t have any change-log history. Can’t see who added what. Like you would with a rich text field…
So it does this also badly!
You guys said you appreciate honest feedback, so to put it bluntly, it feels to me like whiteboard is a bit of a gimmick in Fibery right now. A check box to say you have it.
What to do?
Split into 2 things. Canvas field and Network view. Changes that will preserve data that exists already:
- Add a canvas field. This will look like an embedded whiteboard but will be in all entities in the database. Think of this like a rich text field.
Needed features for this to work and bring canvas to the level of a rich text field: Include whiteboard content in global search and references - #2 by Mircea_Braescu, Entities in whiteboard don't appear in reference, add sections / text / shapes using automations, see edit history of whiteboard, rich text fields inside of the whiteboard where you can mention entities as you type (maybe even replace all text elements to be this?), - Do the same thing you have planned for the Docs → Database migration. Not sure what you have planned, but with the canvas field I think it can work the same way.
- (Optional) introduce network view. No comments on the canvas, no following cursor (unless this is also bring to other views). Follows behaviour of other views, but instead of being nested heirarchy, it is in 2d space. Not sure if dragging the nodes around should be allowed, or if it should be stuck to a set of predetermined layouts. I think it should be stuck to layouts personally, seeing as moving the nodes closer or further apart could indicate “knowledge”. Its doing clustering on a view instead of data. When/if relationship properties arrive, maybe you could set a number for how close the relation is, and this would indicate how close it should be in the network. Then the data is actually in the database as opposed to it being in the view only. Not sure about this one though.
Closing thoughts
I really think Fibery has so much potential. It’s already one of the strongest pieces of software in this field. I think this is one conceptual challenges that wasn’t on this year’s list and needs to be solved for Fibery to be a complete solution.
If this isn’t clear, or you disagree, I’d love to hear it. But I felt the need to share it once more, and more comprehensively as I haven’t heard anything last time and I feel bad telling clients “Don’t use this feature as isn’t quite integrated nicely yet”.
Keep going,
Ron