FigJam vs. XWiki

If you're working in small product teams, like triads, and already using Figma, this is a no brainer for white boarding, quick/fast sketches, wireframing, collaborative doodling ... it gets less appropriate with large teams, infrequent. IMO, due to the way in which they price, it's better to keep the inner circle small-ish.

Incentivized

XWiki is very well suited for a very wide range of web collaboration and web development.

• One file, auto updated, no need to get latest
• Easy to preview
• Lack of client is benefit to some (not me)

Incentivized

• XWiki makes it easy to manage semi-structured information, which is at the heart of every knowledge nexus of organizations. It makes it easy to manage in a single system both structured data (such as memberships, projects), and unstructured data.
• XWiki offers a very rich API for creating enterprise applications quickly that are easy to maintain and evolve collaboratively.
• XWiki templating and skinning system is extremely flexible and powerful.

• It misses easy-to-use pre sets of diagrams. The ones presented seem to be not native and hard to use. Miro is a good benchmark.
• Navegating throught projects in the main page is confusing, specially when people are not admin users.
• It should suggest ways of organizing the pages designers do, specially when the project is big and have many pages and sections.
• It could have, for example, a draft version for every page, so that one can hide it when they finish the work, but can open it whenever something needs to be modified, versioning the job.

• While the basic pieces are available for turning XWiki into an advanced semantic system, some features could be made available more prominently to the user for easing the use of faceted and typed links, paving the way for a new era of collaborative knowledge sharing.

I don't use it often, because the organization I work in uses a different environment on a commo basis. This is rather used between the designers, who prototype the solutions in Figma - they just have it as a workbook/notebook for their ideas. However, if those need to be shared with stakeholders or other organization members, the designers are expected to use a different environment.

Incentivized

FigJam works best in pair with Figma, as it allows you to keep track of your project in one place, supporting all phases of the process. The functionality is more intuitive, quick, and efficient. Visually, I also prefer it more —it’s more enjoyable and playful, making the experience much more engaging.

Incentivized

XWiki key differentiators in my opinion:

• Fast app development framework with very rich API
• Open-source strategy, opening the way to collaborative innovation

• FigJam saves a lot of time ... it's nice to have all my visual notes/sketches within Figma itself where a lot of design work lives
• The project organization and other features contribute to the ease of answering that age old question ... "where can I find that mockup?"
• Dev Mode is pretty cool. Not many use it, so some designers may spend unnecessary time spec'ing out things that no one will appreciate, let alone look at.

Incentivized

• XWiki has a positive impact on the OW2 communication and collaborations strategies. It saves time when developing applications.