TrustRadius Insights
Zeroheight is a versatile design system that has proven to be invaluable for users in various ways. It serves as a centralized space for …
Starting at $49 month
View PricingOverview
What is zeroheight?
zeroheight helps teams create, manage and maintain their design systems. Using zeroheight, designers, engineers, and product teams can collaborate and build design systems that can be easily shared across teams.
Recent Reviews
Pricing
Starter
$49
Cloud
month
Enterprise
Custom Pricing
Cloud
Entry-level set up fee?
- Setup fee optional
For the latest information on pricing, visithttps://www.zeroheight.com/pricing
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Product Demos
EF5 Demo Day - zeroheight
YouTube
Product Details
- About
- Integrations
- Competitors
- Tech Details
What is zeroheight?
zeroheight helps teams create, manage and maintain their design systems. Using zeroheight, designers, engineers, and product teams can collaborate and build design systems that can be shared across teams.
It is used to creates a centralized repository of styles, tokens, guidelines, code, components, and patterns, integrated and synced between tools already use. zeroheight aims to make maintaining consistency across different products easier and reduces the time and effort needed to stand up new brands and products confidently. It offers features that suit teams from startup to enterprise, from governance to analytics to automation.
zeroheight Features
- Supported: Design Integrations: Brings in design assets from other tools including Figma, Sketch, and Adobe XD. Ensures proper usage with annotations, do’s and don’ts, and usage guidelines.
- Supported: Code Integrations: Displays live code blocks from ten different languages, including React, Angular, and Vue. Stories can be embedded with the Storybook integration and markdowns sync from GitHub.
- Supported: Analytics: In-app analytics measure design system adoption. Offers integrations with Google Analytics and Hotjar to include events for viewing styleguides, downloading assets, and copying code.
- Supported: No-Code Editor: A WYSIWYG editor eases keeping documentation up to date, and is used to create tables and callouts.
- Supported: Governance: Feedback can be shared on pages before they’re published with in-line commenting. Reviewer seats can be used to solicit ideas from multiple stakeholders. And Releases are used to launch styleguides.
- Supported: Security: A variety of options for styleguide security to ensure work remains safe, including SSO, password protection, and trusted IP range.
zeroheight Video
Product Demonstration
zeroheight Technical Details
| Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
Comparisons
Compare with
Reviews and Ratings
(4)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Pros
- Cons
Zeroheight is a versatile design system that has proven to be invaluable for users in various ways. It serves as a centralized space for showcasing complete pages, molecules, or atoms to the business, allowing users to easily share and access design information. Reviewers have praised its ability to provide developers with necessary specifications and assets, making it a convenient reference for their work. The platform's one-stop-shop approach eliminates the clunkiness of using multiple internal systems, simplifying the process for designers and developers alike. This has been particularly beneficial when onboarding new teams, contractors, and vendors as it provides a single place for design documentation and downloadable assets. Additionally, UX Engineers have found it helpful in maintaining and developing component libraries based on the information provided by Zeroheight's Design System. Collaboration between developers and designers is enhanced through the platform's features that facilitate feedback and improve accessibility and usability. Overall, Zeroheight has successfully met the need for a comprehensive design system that streamlines workflows and enhances cross-functional collaboration.
User-Friendly Interface: Many users have praised the tool for its user-friendly interface, stating that it is easy to learn and use. They appreciate the great connectors to design software like Figma and Sketch, which make it super easy for them to keep their designs up to date.
Efficient Navigation: Several reviewers have appreciated the system's ability to automatically add navigation when adding new pages. This feature has saved them time and effort in creating and organizing their designs.
Design Tokens Functionality: Developers have expressed their satisfaction with the design tokens functionality of the tool. They find it convenient as it allows them to easily access and utilize design specifications in their projects.
Cons:
- Limited customization options: Some users have expressed a desire for more hands-on control over the appearance of their designs. They would like to have more flexibility in customizing spacing, padding, and even specific element colors to better suit their individual needs and preferences.
- Difficulty switching between boards: Users find it cumbersome and unintuitive to navigate between different zeroheight boards within the software's interface. This suggests that there may be usability issues with the board-switching functionality that need improvement.
- Performance issues with syncing and refreshing files: Several users have reported experiencing delays when updating design files. The slow syncing and refreshing process indicates potential performance issues within the software that should be addressed to improve efficiency and productivity for users.
Reviews
(1-1 of 1)Companies can't remove reviews or game the system. Here's why
As UX Engineer I am responsible for maintaining and developing a component library as well as aiding other users in using the component library and contributing to it. The basis for the development of components is our Design System which is showcased in Zeroheight, so any work we do directly correlates to the information we get from Zeroheight. Zeroheight is filled with information by our Designers and not within my realm of work, however I am able to give feedback to our Designers from the viewpoint of a developer to improve Zeroheight and make it's contents more accessible for the contributors and UX Engineers that we have.
- showcasing components and other topics
- ease of seeing detailed information on components (colors, paddings, sizes etc.)
- ease of finding information
- possibility of going to previous versions of the design guideline
- when opening a component image (which opens a new page where the detailed information like paddings and colors are shown), the zoom can only be done by buttons, I'd prefer to be able to use my mouse scroll and for vertical / horizontal scrolling to do ctrl+scroll or ctrl+shift+scroll or something like that
- communication between designer, developer and ux engineer
- documentation
- a single source of truth, so that no discrepancies or misunderstandings can occur
- increased quality, as less misunderstandings or communication problems occur
- increased speed of development, as it is a single source of truth for us. The developer can rely on the information in Zeroheight being correct so that he doesn't have to iterate his code again and again.
I have used and still use Sketch and Zeplin too, but they serve other purposes for us. Sketch is used to design the components themselves and they are then exported to Zeroheight where they are showcased and enriched with textual information. Zeplin is used to design application pages, and again the components are exported to Zeplin from Sketch. But Zeroheight is mainly used for the development of the components themselves as well as a documentation for our design guideline in general. It is also used by us for design tokens and patterns, as well as other information on the design guideline, so if someone wants to understand the "why" of a design decision, the explanation can be usually found in Zeroheight too.