Notion vs. Focalboard for handling the Design Thinking Data, Appendix of Report 5
Notion vs. Focalboard for handling the Design Thinking Data, Appendix of Report 5
I confirmed the possibility of using Focalboard, an alternative software to Notion, to handle the design thinking data devised in Report 5. In conclusion, Focalboard could not handle the design thinking data for the following three reasons.
Focalboard cannot automatically transfer references data from To-Do List to Got-Done List quickly because it cannot filter variables of Checkbox type. (Refer to page 6 of Report 5.)
There can be only one link to child and parent references. Foracalboard can not form the k-ary tree since the array type is unavailable in Focalboard. (Refer to page 5 of Report 5.)
Emulation of pointers to other nodes is impossible due to a lack of the Relation type. However, I can partially circumvent it by setting the link to the page by using the URL type. (Refer to page 7 of Report 5.)
Focalboard is very stable and has a complete user interface, including drag-and-drop of the board if you don't use the above three functions. Also, the data visualization of Focalboard is comparable to that of Notion, as shown in the following figures. Unfortunately, I wish more types were available for variables in the database, like Notion, shown in the following table. But, I think it is an excellent software that is second to none compared to Notion. In addition, Focalboard is still in the early stages of development, so I expect more enhancements in the future. I also believe that developing an open-source knowledge management software in competition with the proprietary software is meaningful for collaborative activities in art and science.
Gallery view of Notion and Focalboard
Gallery view of Notion and Focalboard (2)
Board view of Notion and Focalboard
Board view of Notion and Focalboard (2)
Table view of Notion and Focalboard
Calender view of Notion and Focalboard