With great regret, I have seen in the last year that Fibery has given up being a general-purpose application, useful for building the most varied applications, to take refuge in the niche of workflow and project management applications (for the latter field I have more than one doubt that it is a truly competitive application, lacking basic functions such as Gantt charts). Yet Fibery lacks very few tools to outclass and annihilate products like Anytype, Obsidian and Capacities, making them clearly inferior in the field of knowledge management. Because Fibery is the only application I know of that provides powerful tools for the visual representation of hierarchical data. It is this feature, in the field of knowledge management, that makes it so high-potential. I try to list what tools are missing, in my opinion:
1] Graph view
Actually, by building it by hand with the whiteboard tool, you get an interesting graph view, because it is possible to enrich each displayed entity with fields of interest. But everything has to be done by hand, while it would be necessary to have a button to dynamically create the view. And the whiteboard doesnât update if I add entities, it has to be done manually.
2] Templates to differentiate the views of individual entities. I saw that the multi-view on the entity has been added in the pro version. Bad, very very bad, the other competitors have had this basic function for a long time and they donât charge for it. Here the designers of Fibery have been too slow and given the importance, putting it among the paid functions is wrong.
3] latex integragion, this integration is really very simple to do.
4] Entity preview in canvans embeded view, like in Capacities:
I also agree. View templates are a basic feature that every other tool has so Fibery is playing catchup here. Really frustrating that itâs a premium feature locked behind a higher price tier (that was only announced 1 day before it was launched). Also mind-blowing that we still canât duplicate relationship views.
I think Fibery has been clear that itâs focussed on being the operating system for business, not just a project management tool. Yes, Gantt charts are not available, but you can technically create them through calendar views and swim lanes.
What I was wondering is what is the use of a graph view? Iâve been a huge fan of graphs, even worked in a semantic graph computing startup over a decade ago, but the graph view in these kinds of systems never felt useful to me. The existing schema graph makes sense to me, but an entity graph view is just cluttered, at least the way Iâve seen most, which simply plot out everything.
What are your use-cases for a graph view? And why are they not supported by the list of references, which we have in Fibery?
This is not correct. What you really want it seems is PKM tool (for a single user). This is not Fibery goal and this is why we do not prioritize some features (like latex, offline support, and even mobile) on top. Fibery is focusing on teams. While you definitely can use it as a PKM software, I think there are better choices like Obsidian and even Notion.
We are working on some improvements here. For example, in some future release you will be able expand any entity and add a collection with some filter to the whiteboard.
Okay so we went from everyone else has it for free to no one is doing it, but it would be great if Fibery did so.
FTR Iâve been a ClickUp Vetted Consultant, a Coda Expert, and an unofficial Notion and Airtable service provider. Only Coda comes close to what @DiegoKamp described (unless heâs referencing Atlassian products. Iâm unfamiliar) Iâm not certain of what you mean by âtab functionalityâ but it does sound like a fantastic, separate feature request.
I donât get this post at all. I love a feature request a much as the next fella but entitled posturing is so gross. Letâs not encourage posts like these.
Yes, I agree with you that a graph visualizing the entire knowledge base is of no use. I didnât specify well; I am interested in the graph visualization of a specific entity and everything connected to it. As I explained, a satisfactory graph visualization is achieved with whiteboards, perhaps even better than what you get in Capacities or Anytype, because you can choose which fields to display. Keep in mind that I am using Fibery mainly in the context of Knowledge Management.
Could you point to the spot on your body where my qualifications hurt you? Or where I said we shouldnât discuss legimite concerns?
The tone of this post is a drag in any community forum. Itâs possible to communicate the direction we want Fibery to go in with decorum and without diminutive language.
We have always been able to ask for features we want by submitting individual feature request posts for good forum hygiene.
Huh? Youâre the one saying someone who doesnât speak English as their primary language and ended their post with âThank you for your attention and I greet you cordiallyâ was being gross and a drag.
Let the Fibery team handle their own community please.
I think itâs unrealistic to expect that Fibery will decide/declare up front what pricing tier will apply for all the yet-to-be-developed features, and Iâm not sure when is the most appropriate time to mention it for any given feature.
When development starts? A week before launch? A day before?
Also, Fibery has tended to release an MVP of a feature (sometimes as experimental) and then add more sophisticated functionality. This could mean that the pricing tier choice seems steep for the initial release, but this way is probably preferable to the alternative - releasing a feature in one tier and then elevating to a higher tier as the feature comes out of experimental/functionality improves (a mistake made once already ).
As has been discussed in other topics in this forum before, the definition of what is âessential functionalityâ or âtable stakesâ can vary from user to user.
In general, Fibery is priced so that users should feel like theyâre paying a fair amount for the value theyâre getting, but thereâs always people who will feel that itâs a bit overpriced (but hopefully a lot of people who think itâs great value).
This sounds like a classic PKM use case, which as Michael has said, is not the Fibery target.
We donât want to police the forum
Weâre mostly a bit nerdy in here, so if in doubt, remember API
I guess in the PKM use case this makes sense, in our case of a business collaboration platform it would still result in one massive graph as pretty much everything is connected to each other pretty much like Wikipedia.
But seems like Fibery is adding a drill-down functionality to the Whiteboard, maybe with some automations your wish can be fulfilled eventually.
Folks, we do love honesty and direct communication style. But please, donât do personal attacks. You can trash Fibery as a product as much as you want, but donât trash people in this community, please.
This is a crucial point, where I would like to bring back my experience. I use Fibery to create my personal knowledge base, no doubt about it, but I am also working on a space where I am implementing a KOS for the organizational unit where I work (in banking). In the bank I have identified some possibilities for using Fibery as a workflow management and project management application, but the use cannot be extended much, because it would have to heavily integrate with the existing banking information system, which consists of a very large number of closed applications (in this sense for a start-up Fibery could very successfully become the operating system of the organization, creating most of the operational processes with it).
Then I am also persuaded that Fibery is an application serving the team, but you will agree that every team needs to organize knowledge, and Fibery should also provide the solutions for organizing the teamâs knowledge; it is not like you can defer knowledge organization to an external application. I would not neglect the development of tools in this direction. Certainly the possibility of multiple views is a very good thing, this is an important feature. But even small implementations, as I suggested, such as Latex integration, or audio notes, would be useful.
The use of Fibery for knowledge organization, in my opinion, is particularly fruitful in the case of a knowledge base consisting of structured and hierarchical data, as well as textual data. In this case the tools for hierarchical data visualization made available by Fibery are the most powerful I have tried to date. Nothing like this is present in competing applications to my knowledge. If, on the other hand, the knowledge base is embodied in free-form, non-hierarchical textual documents (notes), then these advantages are reduced and one can use Notion, Obsidian, etc⌠Managing with relational databases the organizationâs information is the key point. Another very small improvement to be made, but of great impact, is to put for a field the uniqueness constraint. As the database grows, in fact, it is easy to run into the unfortunate phenomenon of duplicate records.
Finally, a last note on paid pro features. I am not against it a priori; if a feature costs a lot to develop, it is legitimate to charge for it, at least in part. However, I would not charge for features that contribute to the graphical output and impact the end-user experience. Rather, as in other SAAS, you can charge for the x+1 version of the AI and provide the X version for free, or charge for the space occupied by the Workspace when you exceed x GBytes, as almost everyone does.
Have a good evening.
Well done. It would be nice to have the graph button, which does all the work automatically, i.e. generates the graph view (using whiteboards, without implementing new objects), I would put it here:
True, I saw Michaelâs response, the solution they propose is interesting. However, the risk you expose is real, the overabundance of information in a single graph in the end is not very useful.
Have a nice evening!
This is absolutely true, but letâs make it concrete. How many teams use Latex? Usually it is science-heavy teams, and we donât have many requests for its support yet.
As for audio notes, I am not sure I get it. You can upload audio file into Fibery rich text and even create transcript with few clicks.
Not sure I get it. Every entity in Fibery has unique ID.
Thank you. I didnât know this app, I will try it. I was thinking about an integration in Fibery of some javascript that makes you record from the microphone to be triggered by a click (with a button on the interface or triggered by markdown with /âŚ). Anyway you can record with the application available on the computer you save the file and import it etc⌠It is a much more time-consuming. activity, though. Iâd like a built-in, quick-to-operate feature that places the audio directly in the canvas.
Have a good day.
Here I disagree, since using it a lot, I have run into instances of duplicate records. The number of these cases increases as the database grows, without implementing some kind of control. Think about the case where you enter an employee in the employee master database, a mandatory field is certainly the serial number that uniquely identifies the employee, this field must have a uniqueness constraint, otherwise I can assign the same serial number to multiple employees. Same goes for car license plates, computer serial numbers, customer tax numbers, etc., etc.
The lack of the uniqueness constraint was one of the first limitations I pointed out. It also amazed me that not only Fibery does not provide this feature, but neither do all the other competitors. Then it is true that Fibery is not a true database management software, but such a constraint we should have. Never mind multi-field constraints, and other more sophisticated features, but the uniqueness constraint on the single field I would put.
Have a good day.
).
