Indeed, I think one of the biggest things holding back broader adoption of Fibery at this point is a lack of balance toward the most common use cases and general ease of use. Or at least the most common potential use cases of the broader market. By which I mean, Fibery may survey their current users and see “Hmm, only 25% actually use it for Project Management/tasks/etc.” and perhaps conclude it may not be so important to have really polished functionality here, or that the more flexible approach should continue to be the largest focus. After all that is where Fibery currently excels.
But of course there are all the people who are choosing not to adopt Fibery because of the - let’s be honest here - fairly clunky overall experience of doing task management, especially around notifications, and simple task functions like recurrence as highlighted in this topic. I’m sure Fibery team is aware of all this, but again I really do think a major effort toward ease of use, similar to the big Migration of Entity View to Blocks, would be a super valuable project for Fibery’s overall adoption, revenue, etc. I would love to see that be a next major area of focus after Blocks.