Marvel vs. Visily

The best Marvel scenario is when you have an application that has different navigability options, and it is a long project. Marvel works to design these applications, as well as give a demo in the design to present it to customers and visualize how your application will be on the client side. This is an advantage for the whole team because the client knows what to expect, and the developer know what to develop. I also appreciate the logical order between options and navigation, which allows you to carry everything out very cleanly when working. Now, if there are projects that are short and do not have a level of design that requires you to present your application to a client in a visual way, it is not necessary to work on Marvel, since the ideal use of this application is to really see the scope of a project, to see in a visual way what will be presented and how it will look, and to see functions and features that will be available in some way when the application is developed. That is the great advantage of using marvel.

When building a new product or even a new startup - this tool is priceless, in demonstrating a product's potential without really building it and investing expensive resources before you have users' validation. It's less usable for any backend planning, or when the system behind is too complicated and any user interaction changes the dataset behind the scenes

Incentivized

• Extremely intuitive and clean interface. The design is beautiful and simple to navigate.
• The links are easy to share and allowed our teams to collaborate (leave comments, annotate, etc.) designs.
• It's very fast and easy to create simple prototypes.

Incentivized

• Prototype feature: enables to move from one screen to another as if the buttons are real
• Premade elements: makes it easy to build the mockup and give it a professional look and feel
• Easy to edit and change as we go

Incentivized

• Would never hurt to have a greater range of micro-interactions!
• A greater range of project frames/devices
• I would like to see an easier way to demonstrate responsiveness to clients, rather than having to have separate mockup files

Incentivized

• When navigating on the big board, it's hard to track the different screens when there are a few dozen of them
• Prototype mode: there should be an easier way to track the screen that needs to be connected from a specific element
• I'd like to use a proofreading extension on top of Visiliy, such as Grammarly, so I won't have to look for those typos

Incentivized

Marvel isn’t the most robust prototyping tool, but its simplicity is what makes the tool rise to the top when it comes to creating quick, simple prototypes to elicit feedback on designs and iterate upon them. While tools like InVision and Axure provide many tools to make more realistic, animation-heavy designs, Marvel is a go-to for a simple interface that enables designers to “just design.” Sometimes it is not necessary to have all of the bells and whistles of a stronger tool, particularly when a designer is low on time. Marvel’s simplicity allows designers to quickly design and iterate in time crunches without the distractions of fancy bells and whistles.

Incentivized

The possibility to animate to mockup is very valuable and needed at the product's early stage and validation stage

Incentivized

• Creating prototypes of applications, or sites in marvel, guarantees me a considerable return, as it saves time and effort, because the client is quickly introduced to the various stages of prototyping, which avoids rework.
• Another plus point, it's free!
• No need to download programs, it's all done online.

Incentivized

• Saved us hours of developing the wrong product, since we could enhance validation by demoing a pre-built product by using Visily
• Helped us communicate ideas between Product and Developer roles within our team
• Cost us some extra time in design, because we didn't import the design from Visily to Miro, which created an overlap

Incentivized