Miro is billed as “an online, collaborative whiteboard platform for ideation and brainstorming to bring distributed teams together, anytime, anywhere. It is designed to build and develop ideas with distributed teams as if you were in the same room, anywhere, anytime.”
It is available under a number of plans, one of which includes a free plan. Given the need for a collaborative whiteboard tool, and given that the design and development of such a tool falls late in the EATS development timeframe; Miro was hoped to be a useful tool to help bootstrap EATSv5 development, and a potential external interface that could have value as a form of external information exchange, or as a front-end for model development. That was the perspective from which its use is being evaluated.
As a tool for information exchange looked to be a tool that might correspond to Kumu or ConceptDraw as a tool with specialized focus for presentations, or model development. The whiteboard framework also has appeal as an alternative for a replacement for Compendium for group-based model development, and the general framing of a collaborative planning and discussion board. The idea also offered opportunities for tie in with the framework of a federated social network, which while thought of as a longer-term component, may also be closer to reality than previously anticipated.
I created a free account to be able to text the product and to assist with another project being done using Miro. The overall result was less than satisfactory. The system seems to function adequately as a collaborative whiteboard. However, the problem is the internal representation of the developed models appears to be held closely within the system, there does not appear to be a facility for import, and export of information was less than satisfactory. The primary export for interface, without development of an API is to a CSV file. The problem being that the CSV export seems to be limited to a one column data dump of objects, with no export of connections.
Not what I wanted to spend my time working around. Kumu, Insight Maker and ConceptDraw all make more sense for my needs with EATS.