Sencha vs. Zeplin

Sencha is suited for:

• Enterprise applications that are really huge
• Development happens on huge teams, on-shore an offshore model, one can divide and conquer by splitting in modules easily
• Budget is not a constraint

It's not uited for:

• Small budget applications
• Not too many components are needed
• Static or less dynamic content based websites
• Turnaround time is shorter and developers have to spin something around in a short duration of time

Incentivized

I still have some issues, especially with color integration between the style guide and also project. When we update the colors, it's not automatically sync to every project. Aside from that, zeplin solves my problem for hand-off design from design to developer. I set zeplin is source of truth design file

Incentivized

• It's a complete solution that has a vast array of pre built components, charts and a data-grid based solution.
• Security comes out of the box.
• It's mobile and tablet ready.
• It has a lot of support from the community so solutions are easily available
• You can add your own flavor via theme customizations and built in component extension.

Incentivized

• Provides dimensions across iOS, Android and Web which saves developers from a lot of guess and check when implementing designs
• Allows for easy download of digital design assets for developers to easily organize and implement
• Great user experience in terms of the product itself and a great value for your money
• Automatically generates CSS for web designs which is AMAZING!

Incentivized

• More default themes
• Biggest community

Incentivized

• It would be better if it has a dedicated web application
• It's not the easiest tool to learn and start working with
• It would be awesome if it had more features turning it into an all-around tool for mockups and prototypes

Incentivized

Great tool

Incentivized

Zeplin's component management and style guide help us to be consistent across whole product and it so easy to use for non-technical person. It is now easy to collaboration for designes between different teams like stackholders, product owner, UI/UX, developers and testers. Now there is only one point of reference is Zeplin so it is so easy to get details without asking designer or developer again and again.

Incentivized

Zeplin has classic support with a chat from the website. It's working fine, and we're also getting the support needed when needed. However, Zeplin is very good at closing the incidents and moving on. It was a while ago we had a case with their support so that it might have improved since then.

Incentivized

The main reason we chose Sencha is it’s full stack solution. We have an integrated backend that solves a lot of the infrastructure issues and Sencha was the only tool in the market that has only one library full of components. It is not fashionable to use it, as developers always love new technologies, but Sencha is the best for business applications and has a lot of useful tools.

Incentivized

Out of all of the products that I have used to support design-to-development handoffs, Zeplin is my favorite. It’s pretty lightweight and easy to use (once you get the hang of it). Zeplin also has a smooth interface and is, generally, clearer to use than other tools, such as InVision. Plus, all of the plug-ins that you can use with Zeplin have supported the design-development relationship and workflows in which I’ve been involved in more efficient, clear, and effective ways than I’ve seen with any other product.

Incentivized

• Excellent applications
• Very good performance
• Not very used, and developers don't like it at the beginning

Incentivized

• We're using the free plan, so it fits in our needs, although we're limited to create only one project at a time
• Sketch has some plugins that offers exactly what Zeplin does, for free
• The integration with design apps (Sketch, Photoshop, XD) and collaboration (Slack and Trello) helps our team to better communicate and be notified on every update

Incentivized