Thanks for all these clarifications, but even if Blocks as Objects are awaited, what about @UnwokeNetizen 's excellent feedback? Why doesn’t the person working on UX answer these questions themselves?
As a layman, I may be wrong, but let’s take the following example: In terms of metrics, moving the “Bin” to an icon only visible on mouse-over drastically reduced the Bin use, but that didn’t mean that users were no longer interested in cleaning up their data. The problem is that this kind of forgetfulness accumulates and some users reach a point of saturation that doesn’t encourage them to make their voices heard in the forum, precisely because of the lack of consideration they’ve seen for the UX over the time. It’s a vicious circle.
Let’s take another, much more striking example: Toggles, their functions are useful, but you must have far fewer people using them routinely or intensively than the competition. Simply because you haven’t yet taken into account this tiny UX correction that would simplify life for everyone who wants to use them.
This UX oversight, which has been there from ages and has never been taken into account, especially in view of the overall work time/value, is a perfect example of what many users perceive as poor prioritization, which is very unfortunate.
Now we come to the worst example: The Anytype search, whether global or in a Set/Object, is so unreliable and dysfunctional that it makes me sincerely reconsidered my desire to use Anytype I’m not talking about possible improvements, I’m talking about the fact that I have a Note whose first word is “Anytype” and which appears in search results if I type “An” or “Anyt”, but which is invisible if I type “Any”.
Making it not worth searching for an object, so not worth create them afterward. And this problem is global and has such a negative impact on Anytype that I can’t understand why it hasn’t been prioritized and fixed! How can new users project themselves with such unreliable search?
The voting system for a feature request is IMO an unrealistic one, because for it to have any value, each member would have to scrupulously discover and evaluate the usefulness of each of the other requests. I think we should prioritize bugs and FRs as follows:
Bugs :
- The most severe and impacting first.
- The fastest to fix and which concern the broadest uses in second place.
Feature requests :
- Fastest to implement and concerns the broadest uses first.
- Most requested in second.
Now that we know that two developers are in charge of the desktop department, I’m left with a rather naive question: why not hire a few more people, given your current growth and the funds you’ve raised?
You’ve created a base of users who deeply love your values your vision, but some are disillusioned by your management. I think a lot of users are still hoping for a change, but it’s no longer a heartfelt journey as hope fades with each update where it should be growing, what a paradox.
There is no anger, just sadness.