With features like intelligent code completion, deep integrations with dev tools and extensibility, IDEs have fundamentally simplified the way we code. Why can’t other tools we use perform the same magic?
Using the knowledge bases and task management tools of today often feels like a burden. Something always irks us about the user experience. There is myriad of choices but the tradeoffs we have to face don't seem to change. 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 full of friction... The tools that are supposed to help us document our knowledge or organize our team 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 a dev-first workflow tool you will love using. In the team, but individually as well. Avoiding the above mentioned trade-offs represents a difficult technical and design challenge.
So we ask ourselves, what would an ideal tool we'd love using look like? With a bit of thinking about the problem and talking to users we ended up with the following spec:
We are building acreom to make building easier for other makers and we named it acreom to signify the creator, it's user.