eWhiteboard vs. Whiteboard.chat

Whenever the engineers & architects of my team require a brainstorming session, we normally use a whiteboard, as the enterprise does provide Miro licenses with associated. Hence, a whiteboard comes in handy when troubleshooting or discussing the requirements surrounding an application or technical infrastructure for a project. As it removes the dependency on requesting an additional Miro license, we use it. The board also loads faster than a Miro board.

Incentivized

• Team collaboration feature where multiple users can contribute at the same time.
• It has wide variety of tools that can be use for creative brainstorming.
• Whiteboard.chat has no license cost associated with it.

Incentivized

• The UI is lightweight and works well but can be more attractive.
• The templates available are quite generic and basic; themed templates can be added.
• Whiteboard navigation is mouse-dominated, but it also has too many hotkeys that make it confusing for the user. They can be easier.

Incentivized

The application, although it loads faster even at slower internet connections, and is a good alternative to Miro boards, still requires some more room for improvement. During live sessions, when multiple users contribute to the board, the updates are openly visible to all. Perhaps a privacy feature that hides text, available to the board admin, would allow me to give a rating. Being from an ersecurity background, I think the app also requires a secure sign-up process with MFA.

Incentivized

I'd rate it lower than Miro but higher than draw.io and Lucidchart. The other two do not have a real-time collaborator feature for users; they have limited tools for designing and no provision for syncing with third-party apps. While whiteboard. Chat does provide a provision for the creation of JIRA or Azure DevOps tickets directly from a sticky note, like Miro.

Incentivized

• Because the app is lightweight and less expensive, it loads faster, saving time in meetings and when sharing links.
• Embeds easily with Confluence docs.
• Templates are more simple and no variety needs some improvements.
• Standardized custom templates are not saved; adding the save template feature would help.

Incentivized