Temenos Quantum vs. Zeplin

Improve performance while the app is in production. The init app development in planning, the testing stage is not an ideal scenario to use KDC yet.

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

• Cross-platform mobile development - we used this for developing the app on a native platform (which could be iOS, Android). Kony offers tools that are useful because they decrease costs and increase the speed at which apps are developed. In addition, cross-platform mobile development tools are generally quite simple to use as they are based off of the common languages for scripting, including CSS, HTML, and JavaScript. It has become easy to find resources with the skill set especially because this is based out of common languages.
• In Kony mobility platform Visualizer makes app development quick and easy. Tons of documentation online.
• Used Kony to develop an amazing app that serves our customers well. WYSIWYG interface is great for building interfaces quickly. Build and test quickly for many different targets.

Incentivized

• Ease in automatically building design style guides, saving time that might be spent on building style guides in another tool (such as InDesign).
• Users can use Mac, PC, or web versions of this app to collaborate on a single project, enabling us to work with a wider pool of contractors.
• Accelerates the design-to-development workflow, as it’s very easy to import Sketch or Photoshop files through plug-ins, and HTML/CSS codes are automatically created based on designs.
• Provides cross-platform specifications for web, iOS, and Android, which can save developers time in figuring out specifications beyond the “main platform" on their own.

Incentivized

• Manuals or instructions need to be streamlined with its high pricing.
• It's a very intricate platform. It only performs moderately while the app is currently in operation.

Incentivized

• The uploading and syncing of assets is great for sketch and photoshop but we use illustrator and that can be cumbersome/tedious at times.
• There are certain elements that have been a bit confusing to navigate at times, but for the most part, it's pretty user-friendly
• More integrations

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

We evaluated variety of platforms like Xamarin, Sencha, PhoneGap. When we were initially evaluating Xamarin, it was not Microsoft and so the releases and features were not very streamlined. Also licensing was a issue with that. Sencha was a very attractive cross mobile platform but was expensive. Just for handful of developers price was high. Ours is big enterprise so licensing costs became huge. PhoneGap is based out of open source Apache Cordova project and is completely free to use, which goes some way to explain its popularity. The enterprise version boasts marketing features via Adobe’s Marketing Cloud, so when it launches it will probably be monetized. Comparing with the features platform has to offer and the price tag attached to it, we narrowed down to using Kony.

Incentivized

Zeplin is great to inspect and share user interfaces, specifications and assets, perfect for developers. Tools like InVision and Marvel are much better to create prototypes for both developers, coworkers and even stakeholders, but they don't have this kind of feature (inspection) as Zeplin does. So each of them can be used for different purposes, offering different approaches to share and interact with layouts for apps and websites.

Incentivized

• Positive on ROI. I'm constantly utilizing Kony since it's a robust tool capable of publishing.
• It also shares prototype creations of apps in a highly intuitive and customizable environment. It provides a preview of apps in real-time. Collaboration is seamless. Important functionality includes smartphone features (without any written code involved) and accessibility to a browser, maps, and SMS.
• Trying to understand the user manual can be challenging since there are way too many features available. All of them aren't really necessary for beginners. And they've yet to offer them in a "phased" approach.

Incentivized

• Development time has reduced as the design updates are communicated in real time to developers and they don't have to write the boilerplate code as it's already generated.
• Employee engagement has improved as every stakeholder is aware about the design changes from the beginning and can give their inputs.
• Designers save a lot of time as they don't to explicitly communicate when the update or publish their designs and also it just takes a couple of clicks to publish their designs. Also, lot of rework is saved as every stakeholder is involved right from the beginning.

Incentivized