Inspired by the long search for various prototyping systems and the desire to share this experience. In this post, there are no complex systems such as iRise or IBM Rational Rose, since they are not only and not only simple prototyping systems, and the cost of these solutions suits enterprises of considerable scale. This post is about something more earthly.
A bit of theory. Experienced data: ')
Each project has its own customer. This could be a director of a large campaign, a developer, a digital agency manager, a designer ... but who many. In each case, this imposes certain restrictions on how much the prototype should be worked out. I mean the following things:
The number of prototypes and evidence (on click, visually schematically) transitions between them
Presence of states of one type (example: a block of contacts that looks differently depending on whether the owner of this list is looking at him or a guest)
The presence of comments on the elements
Banal "beautiful" in the prototype - beautiful forms, ikonochki, pictures and stuff. By experience - one of the most useful things to convince the customer that the idea will work
Efforts for each project / task must meet their complexity. If your project is a small, internal subsystem in the backend, and you are given one developer to help, then to find a common language with it in the framework of this project for a few weeks is enough of the most basic capabilities of a particular system. There is no need to buy something expensive and complicated.
Below I will give a list of tools that I somehow found, and, some of them, I used.