Redwood Reporting : Report2Web vs. zeroheight

The tool is very powerful for obtaining and scheduling reports; however, I believe that if the cost were lower, more companies could obtain it

Incentivized

For creating and maintaining a component library, it is a fantastic tool that creates an interface between Developers, UX Engineers and Designers. It is easy to get both general information about a component, but also incredibly detailed information when looking at the component on a pixel-level, where information on paddings, margins, colors, fonts etc. can be easily accessed.

Incentivized

• [It] has [a] default report.
• [It] has a section where you can create reports by making queries in SQL.
• It has a Dashboard window where you can schedule reports in real time of the executions of the jobs or chains.

Incentivized

• 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

Incentivized

• It has a positive impact for the different managements since they can obtain their reports on a daily basis and in case any job fails on a recurring basis they can make decisions.

Incentivized

• 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

Incentivized

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.

Incentivized

• The Redwood system by itself is a very good tool that can pay off the investment in a very short time.
• It has a positive impact for the different managements since they can obtain their reports on a daily basis and in case any job fails on a recurring basis they can make decisions.

Incentivized

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

Incentivized