1. The Birth of Docswave
Google Apps are the optimal collaboration solution for businesses using functions of email, calendar, storage, voice and video conversations, and so on. In particular, among the best and unbeatable features of Google Apps is the ‘share function,’ allowing instant sharing of information such as documents and schedules with selected members.
However, there is one thing not available through Google Apps: it is the ‘workflow.’ While it is possible to share a document with multiple members at once through Google Apps, it is not possible to share it in a certain sequence (i.e., assign a process in which the document is approved). In other words, the function of e-approval or reporting is not available through Google Apps. This is where Software in Life came in. We developed Docswave in 2015 to enable enterprises using Google Apps to enjoy the merits of Google Apps as well as utilizing the workflow of Docswave to make their work processes smarter.
2. Our Philosophy of ‘Documents’
(1) The Philosophy of ‘Flow’: “The flow of documents should be smooth anytime and anywhere; it should be natural to users.”
According to our philosophy, documents should be delivered to the recipient according to the creator’s intention, anytime and anywhere, with ease as well as a natural flow. This will help businesses make prompt decisions; it will also play an important role in the company’s progress. Docswave focuses on this philosophy of flow and intends to contribute to the success of all businesses.
(2) The Philosophy of ‘Wave’ (i.e., flexibility): “Documents should be flexible, allowing changes when necessary.”
In the simple e-approval system, flexibility is not needed as the only functions include approving and rejecting documents. However, as cooperation is essential in a workflow, flexibility in modifying documents at each step is necessary. Docswave allows the requester (i.e., ‘creator’) to give authority to approver(s) to modify documents, granting flexibility to the documents in process. In essence, Docswave plays the role of a ‘workflow,’ going beyond traditional e-approval.
(3) Our Concept of ‘Storage’: “The documents created by our users belong to themselves, not to the Docswave system.”
Many groupware services save users’ contents in their own database. This system provides users with contents but not the ownership for which they created. Thus, once the service expires, accumulated contents also disappear. To improve this inconvenient structure, Docswave has been designed to save all documents in the Google Drive of each user. Our philosophy is simple. Documents created by a user belong to the user, not to Docswave. Docswave considers this ‘philosophy of document storage’ as the basic courtesy of confidentiality of our users’ contents.