Abstract vs. XWiki Collaboration Suite

• Large teams with dedicated design operations support
• UX managers that want a facilitated workflow for their teams
• Disciplined teams of individual contributors that want to adopt a process in their UI workflow
• Cross-discipline teams that want a central collaboration space for reviewing and critiquing UI artifacts
• If your files are named "FOR-REALS_FINAL_FINAL_FINAL_Super-Important-Project (copy).sketch"
• If you're managing multiple pattern libraries

Incentivized

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

• Versioning for desginers
• Collaboration between team members

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.

• Asset exports are not as great as Zeplin and others.
• Filtering within files.

Incentivized

• 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.

as already explained this software only does branching... the rest is really poor and basic

Incentivized

Abstract has a difficult learning curve. If a feature-branch workflow is new to you, then it will take some getting used to. They make a lot of updates to the interface and these feature releases get ahead of their documentation. They rely heavily on an excellent customer support team and are present on various Slack channels to help design professionals with issues.

Incentivized

Abstract by nature is complex and has to respond to whatever changes in Sketch. So there are frequent issues. Support can be slow to respond and are not always helpful, but they are quick to find and patch the bugs. Overall, it's not the best support, but it hasn't been detrimental.

Incentivized

I purchased and administer Abstract. It was requested by our design department who evaluated it.

Incentivized

XWiki key differentiators in my opinion:

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

• Single source of truth for the team.
• Could quickly get expensive with corporate accounts.

Incentivized

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