Abstract vs. Nuclino

• 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

Nuclino is suitable for just about any company. It is intuitive and helps keep any company organized.

Incentivized

• Versioning for desginers
• Collaboration between team members

Incentivized

• Workspaces are helpful to segment information.
• Being able to download files directly from Nuclino is useful.
• Having the ability to link to external docs is useful.

Incentivized

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

Incentivized

• No real offline use is possible.
• For small teams it's ok, but pricing is too high if lots of employees need to work with it.

Incentivized

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

I love Nuclino's usability. The layout is clean, simple, easy to follow, and bright. I like that there is a read-only account option so that less-tech savvy people can still use it and they won't need to worry about deleting key information from the database. Similarly, I like the features that allow multiple contributors to have the same features to edit.

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

The Nuclino knowledge base is good. Most answers to your questions can be found there. I didn't need to contact support at all.

Incentivized

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

Incentivized

Nuclino is the clear winner when it comes to ease of use for both the administrator and user. Less setup time and less "training" time. The streamlined interface is quick and intuitive to learn and is not cluttered as compared to Confluence. Every tool you need to use to create a page or administer the workspace is available immediately on screen or by right-clicking. In contrast, Confluence buries many tools in administrative interfaces and only allows use of some features once you make several clicks to include a "macro" or "plug-in". We use both tools and I get complaints constantly from my team about how complicated Confluence can get just to author a quick page.

Incentivized

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

Incentivized

• Having a central documentation allowed users to find data more quickly, which resulted in 50% less "question" type bugs that would appear in our queue.
• Collaborating documentation before development resulted in less bugs; this is part process but the ease of sharing and making related documentation easy to access encouraged users into adapting the process.
• Increased use in documentation allows support response time to be higher for triage since supporting documentation is ready to go.

Incentivized