Our view at Stack - our team love using Miro as an online workspace for innovation, enabling distributed teams to dream, design, and build together. With a full set of collaboration capabilities, it simplifies cross-functional teamwork, meetings, and workshops. Create concepts, map user stories, and conduct roadmap planning in real-time.
If your work requires you to create diagrams, you might be familiar with draw.io (also diagrams.net), an open-source, web-based diagramming tool offering complex and niche diagrams: network diagrams, server rack diagrams, floor plans, and more.
You might also use Miro, an innovation workspace that lets you virtually collaborate with colleagues on a variety of tasks and projects — whether it’s brainstorming, planning, designing, or building the next big thing. It doesn’t matter if you’re mapping out a complex process, visualizing a system or cloud architectures, or just trying to make sense of your thoughts, Miro’s user-friendly interface makes it easy for everyone to contribute.
Miro and draw.io are both powerful diagramming tools, but using them together is even better.
Why we like draw.io
draw.io offers a wide range of advanced features, such as custom libraries, data linking, and export options. By using draw.io within Miro, teams can leverage these powerful features to collaborate on sophisticated diagrams.
Here is just some of what you can do with draw.io in Miro:
- Import existing diagrams built in Lucidchart, Gliffy, and Visio. No need to start from scratch. Seamlessly move your existing diagrams from other tools into Drawio to take your work over the finish line — without losing context.
- Export diagrams as SVG, PDF, VSDX, and more. Easily share your draw.io diagrams with partners, customers, and other stakeholders using a variety of file formats.
- Leverage thousands of highly technical shapes. draw.io supports niche shapes, plans, electrical circuits, and other visualizations often unavailable in other tools. This includes ArchiMate enterprise architecture modeling language.
Learn how to get started with the Miro-built draw.io app to build floor plans, electrical circuits, or any number of other diagrams.
Why draw.io and Miro together is awesome
draw.io has been around since 2005, so it’s been battle-tested by longtime users and the open-source community. It’s a popular choice for those seeking a tried-and-true diagramming solution. By using draw.io in Miro, you get even more out of it.
Collaboration
By using draw.io within Miro, teams can collaborate on even more diagram types. After one user builds the draw.io diagram and adds it to a board, the rest of the team can join in to add stickies, comments, and other feedback, fostering a more collaborative and efficient work environment.
Centralized workspace
By using draw.io in Miro, you can keep all project-related content, including diagrams, in one centralized location. This makes it easier for teams to access, share, and reference diagrams alongside other project materials, such as notes, documents, and images. The result? No more silos.
Tool consolidation
The Okta 2024 Businesses at Work report indicates that large companies (those with 2,000 or more employees) use an average of 231 apps. Why not make your life easier and consolidate tools, and get the best of both worlds.
How to use draw.io in Miro
Using draw.io in Miro is easy. To launch the app, follow these steps:
- Navigate to the creation toolbar on the left.
- Click the More apps icon (+) and type: draw.io diagrams.
- Launch the Draw.io Diagrams app.
Watch this video to see how you can create and collaborate on any type of diagram, including importing from other tools into Miro:
[embedded content]
Build a draw.io diagram in Miro today
As you can see, draw.io is a fantastic diagramming tool offering a wide variety of shapes and a high level of customization, and together with Miro you can bring your diagrams and people together in one workspace.
If Miro is of interest and you'd like more information, please do make contact or take a look in more detail here.
Credit: Original article published here.