About reminders/alerts/notifications:
I want to agree with @Oshyan, @B_Sp, @Patrice_Gorin, and others that are speaking about the need for better notifications and alerts over everything as well as polishing.
If we want to use the “use cases” as an excuse, I’d say notifications/alerts/communication would be used in every single use case across Fibery, which should make it a top priority. There is always a need to be reminded (e.g. perform task, follow up) or be updated about something (e.g. state updated).
Fibery is amazing at housing aggregated data and creating function around it. To @webinit’s point about use cases and a features, we don’t see Fibery as just a Product Management tool, even though we do use it as such—there are many more uses. General Proj Management, Hardware Management, Operations Processes, R&D, Internal Knowledge and Tool Wiki, etc. The thing that makes Fibery so great is that it fits many use cases, within one org. Not because it is a product tool that we are trying to mold to different use cases. How are we expected to use Fibery as an all-in-one and create processes and functions around all this data without effective communication and alerting supporting it? Honestly, when we heard that Fibery was focused product teams, we were a bit disappointed, as we felt the features would start focusing most on that vertical, rather than an “all-in-one” tool.
One of the main reasons we keep leaving Fibery over the last 3 years is the lack of alerting and reminding features. No matter what app we’ve created in Fibery and for what purpose it serves, alerting, notifications and reminders are vital. Fibery team themselves say it takes time to master the platform. This means on a team, there will likely be a small number who can be considered experts of the app. Good alerts, reminders, and notifications help less experienced users follow a clear path to utilizing the app and expert team members stay in the know. Additionally, alerts keep everyone coming back to the app.
Forms are great and useful but in my opinion, weren’t a priority. Form entries can be created via Integromat, Zapier, or API. And what’s a form submission worth without proper notification, alerting, and reminders in place? Same with the current notification system… What is the data in your Fibery instance worth if you don’t have full, easy-to-understand and follow context?
I suppose if you have a specific type of team that is great at staying on top of entities without robust alerting systems, it’s doable… but proper notifications/alerts and reminders are still essential IMHO.
At the end of the day, we keep coming back to Fibery because of its ability to mold to different processes and link to other data points and items. I feel app polishing with the available features holds high importance.
Either way, we love Fibery and are once again re-evaluating it for our new use cases. We hope it stays strong and accomplishes everything it wants to!