What's not next?
Transparency is key to Capacities. Every few months, we write to tell you what is next, but there are also some commonly requested features that definitely aren’t coming up soon. We think it’s good to share them too. We hope this can help you decide if Capacities is for you.
All of this is subject to change of course, but as we stand at the time of writing, we are not focusing on the following additions, and may never add them.
We also want to stress that we don’t add these features in the near future because we think they are a bad idea or not in line with our vision but because we have to prioritize our resources and focus on the features that we think are the most beneficial and align with our vision at the same time.
The following will not be added anytime soon:
Capacities is a desktop-first app. While we think that handwriting support can be added at some point, we don’t think it should be a big priority at the moment.
We love the idea and we see a lot of potential but first things first. We think we need to get a few more things right before we can focus on this.
Advanced automation, logic or formulas and Formula Property for objects
Capacities should be a tool that just works. We prefer to make the overall tool simpler and more powerful before we focus on very advanced features.
Flashcards and Spaced Repetition
We think that flashcards and spaced repetition are a great idea and we think we have a good foundation for it. We also think that it is a feature that can be added at some point in the future.
Alias are important for deep knowledge work but based on the time we’d need to allocate for it, we think time is better spent on other features.
We think that RTL support is important for a few users but I think it’s reasonable that we focus on other features first, before we expand the language support.
We have many ideas around how Capacities could be a game-changer for collaborative knowledge work and for teams. We committed on creating the best tool for individuals first. Until we achieved that mission, we keep collaboration and team features on hold.
These features are up for discussion but we don’t have a clear plan for them:
We understand that many people coming from other tools want a global graph view in Capacities. We think it’s more important to focus on using other ways of visualizing your knowledge first.
Object inheritance is a very powerful concept. Nevertheless, we want to focus on building a simple and intuitive tool first. Such features can lead to a lot of confusion and complexity. Already now, you can replicate properties in other objects which is more work but achieves the same result.
These features will not be added from our current point of view:
We value privacy a lot and it’s one of our core principles. We extensively wrote about that and we also have a post explaining in detail what the trade-offs of E2EE are and why we decided against it.
We want to create a sustainable long lasting business without conflicting interests and with the support of all Capacities Believers and subscribers of Capacities Pro we could achieve a very strong basis for this. We think that subscription based pricing for SaaS software is the most sustainable way to run a business and to be able to continue developing Capacities. We hope that makes sense.
We extensively wrote about our thoughts on plugins here.
There are varied reasons for not including these features as things currently stand, such as optimal use of resources, or a feeling that these features don’t align with our vision of Capacities. You can read more about our general approach to building Capacities here.
Whilst we are not expecting to add these in the foreseeable future, we would love to hear your thoughts on the relevant tickets in the feedback board. Feel free to continue to vote and comment to share your thoughts.
