And that concern wouldn’t even be necessary if Anytype simply did not include chat in the first place.
That was one of the reasons I chose Anytype as well. I think many serious users came here with the same expectation: a local-first app whose distributed protocol acts as an automatic, disaster-proof backup in case of fire or any other catastrophic event.
You already understand the core expectation users have for Anytype: they want a reliable, sovereign Swiss-army-knife for their lifelong private knowledge, protected from lock-in and accidental loss.
To align with that expectation, the following attitudes would be appreciated:
- Zero tolerance for small bugs, reinforcing confidence that the team is proactively preventing any potential systemic failure.
- A smooth, dependable writing experience for a tool people use every day over their life.
- Steady, disciplined, long-term decision-making from a team that knows they are building an “ark,” not a trend-driven app.
However, the current situation looks different:
- Bug backlogs have been growing, as Kyanite mentioned, and there is now visible frustration with the dev team’s dismissive responses.
- A basic feature like find-and-replace within a page has been unaddressed for over three years, yet the team is preparing to build advanced search functions for chat.
- Delays in features are repeatedly justified by saying this is needed for “great tech”, without acknowledging user priorities.
Maybe these red flags seem trivial to you because you are satisfied with chat and with Anytype’s current direction. But on the other side, many users—including me—are increasingly worried about whether the dev team is genuinely committed to building the reliable, sovereign knowledge tool we were promised.
AI and chat can be fine additions—if the developers remain aware that existing users have more foundational expectations that must be prioritized. Instead, the team appears swept up in hype at a moment when cool-headed triage is needed.