The managment selected Marvel, the users selected Figma. Thus, we work on Marvel and we have issues with the UX of our apps because of that. Figma enable to zoom out and easily design across several screens. It enables component that have a behaviour in one screen. Figma is a …
In some works, I prefer to use InVision than Marvel for high fidelity prototypes, as there is a wide variety of interactions and micro-interactions available, but still, I use marvel a lot for quick prototyping. It also uses Figma a lot for high-fidelity prototypes. The …
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 …
Ultimately, InVision was just a better fit for our company's needs. It's probably faster to create prototypes using Marvel, but InVision's collaboration features (comments, notes, etc.) are much more robust, which was helpful for our large team spread across multiple …
Marvel creates prototypes much faster than InVision. Both tools use global hotspots---a global hotspot is a linked area which is visible on multiple screens. Marvel has a better UX for setting up new hotspots. Marvel asks only necessary questions, does not interrupt the flow, …
Marvel has replaces InVision for me in terms of quick prototyping for high-fidelity mockups. There is a greater variety of interactions, especially between screens, and overall it seems to just have a sleeker feels. I still use Principle over Marvel for more detailed …
Marvel is a very competitive product as compare to all these other products, but the products I have mentioned, mostly are paid application except for Vectr. Considering the amount of features you get and quality of the application for free is awesome and that is why I …
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.
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.
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.