I’ve been concerned about how to manage project-related information for years. After reading your article, I feel I relate to most of the points you listed, both personally and professionally.
At OTDocs, we are currently developing NotiFile, an app which tracks files without the need to upload them online. One of the main feature of this NotiFile app is the possibility to use a file as an entry point for a group chat focused on that file.
The trick is: you can only join the chat if you actually have the file. It doesn’t matter where you store it, or how you got it, as long as you can drag-and-drop it into the app window, you’ll join.
This “File First” approach aligns with your article on several levels:
- Chats are segregated per file (on file bundles) which limits the scope to what actually matters: the content and lifecycle of the file.
- Participants are people that matter to the conversation: the one who have the file.
- We do not plan to use a message count in ‘unread’ chat markers.
There is much more to say about how NotiFile actually follows your point of view, not only for chats but also for file tracking and versioning, and we would like to get in touch with you to talk about it.