Can you be more specific on how your tool compares to specific product? I've used many and been disappointed. Yours (from the home page) seems similar to Quip, which is nice but seems a bit clunky and doesn't have enough integration with tools i already use.
We do a lot of this stuff on Google Drive, Github and Slack Posts. Google Drive is nice because it has permissions and company administration. Slack is nice because everyone uses it, it is easy, and it's naturally where these types of conversations happen already. But Slack posts are sort of buggy and unfinished, and Google Docs don't have persistent chat.
Github is nice for developers but doesn't extend beyond them, and has no real-time functionality.
Curious how you see yourself fitting in this world?
Slack is where our conversations live, but trying to keep more persistent and organized information there didn't work well for us.
We are also using Google Drive, but mainly for file management and working on documents which require full control over the styling and layout (e.g. legal documents that need to be printed). For more dynamic content and ad-hoc information, it feels too heavy to us.
Github (Wiki) is great for static text content and fine grained change tracking. Besides that, it's rather hard to use for non-developers as you pointed out.
We use Nuclino for collaborating on rich content that is more persistent than conversations in Slack and which does not need the overhead of a system like Google Drive. We haven't used Quip too much, but feel that it's rather similar to Google Drive with the files, folders, documents, spreadsheets and the likes.
To keep the core experience lightweight in the long term, we plan on supporting integrations that extend Nuclino.
Comments
Can you be more specific on how your tool compares to specific product? I've used many and been disappointed. Yours (from the home page) seems similar to Quip, which is nice but seems a bit clunky and doesn't have enough integration with tools i already use.
We do a lot of this stuff on Google Drive, Github and Slack Posts. Google Drive is nice because it has permissions and company administration. Slack is nice because everyone uses it, it is easy, and it's naturally where these types of conversations happen already. But Slack posts are sort of buggy and unfinished, and Google Docs don't have persistent chat.
Github is nice for developers but doesn't extend beyond them, and has no real-time functionality.
Curious how you see yourself fitting in this world?
Great question, we are using similar tools!
Slack is where our conversations live, but trying to keep more persistent and organized information there didn't work well for us.
We are also using Google Drive, but mainly for file management and working on documents which require full control over the styling and layout (e.g. legal documents that need to be printed). For more dynamic content and ad-hoc information, it feels too heavy to us.
Github (Wiki) is great for static text content and fine grained change tracking. Besides that, it's rather hard to use for non-developers as you pointed out.
We use Nuclino for collaborating on rich content that is more persistent than conversations in Slack and which does not need the overhead of a system like Google Drive. We haven't used Quip too much, but feel that it's rather similar to Google Drive with the files, folders, documents, spreadsheets and the likes.
To keep the core experience lightweight in the long term, we plan on supporting integrations that extend Nuclino.