Abstract vs. PeopleOne

• 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

We are using [PeopleONE] to collect and manage our field data for payroll, invoicing, and production management purposes. So far, it works quite well for those uses. Additionally, we are using the app to manage communications from our offices to our field management at upper and middle field management levels. We have successfully used the application to communicate important upcoming events, COVID protocols and reporting processes, and other initiatives. I am unfamiliar with the limitations of this technology or applications for which it would be unsuited.

• Versioning for desginers
• Collaboration between team members

Incentivized

• The UI, both for desktop and mobile apps, is simple and virtually self-explanatory.
• Compared to apps we have used in the past, PeopleONE is fast, in both data entry and retrieval.
• The team responsible for creating our specific requirements for the app is exceptionally responsive. It is made up of creative problems solvers who have built a product that meets every need we have presented.

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

Incentivized

• We haven't actually experienced any issues of note to record here. Every concern, requirement, or change we have requested has been swiftly and satisfactorily resolved by the Impiger team.

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

Incentivized

[I give it this rating] because it has addressed all of our needs in a succinct manner and it operates efficiently.

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

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

Incentivized

• Improved accuracy of data collected
• Improved efficiency of data collected
• Improved efficiency of payroll and invoicing processes
• Decreased time, in the field and in the office, involved in managing data