With features like intelligent code completion, deep integrations with dev tools and extensibility, IDEs have fundamentally simplified the way we code. Why can’t the tools we use to organize our work perform the same magic?

Using the knowledge bases and task managers of today often feels like a burden. Something always irks us about the user experience. We don't enjoy using the tools in teams and we seem to make trade-offs when it comes to the single-player tools. An all-in-one tool but slow and clunky, a local-first knowledge base but non-collaborative and poorly integrated, a capable issue tracker but the UI sucks... On top of this, the tools that are supposed to help us document our knowledge or organize our agenda are often disconnected from each other. It turns out, most of these collaborative interfaces have never been designed for developers but for PMs with developers in mind.

Our mission at acreom is to build the workflow tool you will love using as a developer. Individually, and in the team. Building such a tool is a difficult technical and design challenge.

When we asked ourselves (countless of times), what would an this tool we'd love using look like? This is the spec we have in mind today:

• lightweight but powerful markdown editor at the core and closely integrated with tasks. We believe the knowledge base should be easily actionable not separated from the "doing" part.
• fast capture-first organise-later interface
• optimised for keyboard
• local-first with sync and real-time collaboration
• deeply integrated with other devtools
• community driven and extensible with high quality plugins any 3rd party engineer can develop
• magical to use with an IDE-like assistance to offload organisational hassle

We are building acreom to make building easier for other makers. We named it acreom to signify the creator, it's user.