Abstract vs. Stackby

• 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

Based on my experience, I can provide specific scenarios where Stackby is well suited and others where it may be less appropriate: Project Management: Stackby is an excellent choice for project management scenarios. Its ability to create custom databases, track tasks, assign responsibilities, and collaborate in real-time makes it highly effective for managing and monitoring project progress. CRM and Sales: Stackby is well suited for managing customer relationships and sales processes. Its customizable database structure allows for organizing customer information, tracking leads, managing deals, and generating reports. The ability to integrate with other tools further enhances its usefulness in CRM and sales workflows. Content Planning: Stackby is a great fit for content planning scenarios. Users can create databases to manage editorial calendars, track content ideas, assign tasks to team members, and monitor content performance. Collaboration features facilitate seamless content collaboration and ensure timely publishing.

• Versioning for desginers
• Collaboration between team members

Incentivized

• Ability to collaborate with team members on the same spreadsheet
• Ability to integrate multiple tools for centralized utilization (i.e. Facebook, Google Analytics, project management, etc.)
• Ability to send SMS and messages using integration with Twillio and Whatsapp
• All spreadsheets/databases securely saved in the cloud instead of on local hard drive(s)

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

Incentivized

• Implement the same views available on desktop into the mobile app
• Internal automations (like Airtable)
• Ability to implement and display info as a dashboard (like Airtable)
• Polish up the formatting of formulas, inputting them causes user frustration due to the formula input cursor jumping around
• Better intelligence and ease of inputting data in bulk i.e have the fields automatically identify what data is being input and format appropriately (like Airtable does)

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

Stackby is overall pretty easy to use, especially if you're used to something like Airtable or SmartSuite. Some of the pages seem like near exact clones (though they put their own creative spin on things). I'd prefer a slighty fresher interface (like SmartSuite), but I'm willing to sacrifice that for the better price and great customer service.

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

Extremely responsive, helpful, and friendly support (unlike many other SAAS teams out there).

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

Incentivized

I have also tried Ora.Pm. Infinity has better graphical interface, but nowhere near as many features and the UI isn't as effective (i.e, moving around with keys). Grist has a much more technical interface and it comes from being more of a database/interactive spreadsheet vs Stackby. Grist has much more functionality in terms of formulas, but is much harder to learn to use and less other functionalities. Ora.PM is more of a test at a task management app, and doesn't compare - Stackby is much better.

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

Incentivized

• Positive impact on organising my marketing so I contact advertisers in an appropriate time frame and don't lose hours figuring out what's happening.
• Positive impact on organising challenges so that people feel more connected and supported, leading to future sales.
• Positive impact on understanding data so that I can use it more effectively.