Page status or component? What exactly is the center of interaction?

With the development of the information industry, the development and design of software has been paid more attention, and the prototype design of software has become more important than ever before. We currently use the prototype design tool, the design of the pattern is generally two, one is the page state-centric to set up the interaction, such as Flinto for Mac and principle. Another model is the component-centric, which is also a lot of tools, such as common Axure and Mockplus. So which of these two ways is the best? Let's do a concrete analysis here.

First, the page status as the center

Flinto for Mac and principle such prototyping tools have one thing in common: they have virtually no ability to produce components themselves, basically by using the import of other graphical tools to get components and pages. Flinto sensitive caught a phenomenon, that is the rise of sketch. It decisively developed the version of Flinto for Mac in a way that could be said to be bundled with sketch. By setting up the interaction with the page state as the center, the simple link will automatically animate when the status is listed on the page, and the dynamic effect is realistic. This is a great help for a late development UI demonstration. Principle works the same way as Flinto for Mac.

This is a page state-centric approach that has really been sought after by a lot of people, but the problem does exist. When there is a large number of components in a page that need to be interactive, this way of interacting with different page states is a huge challenge, and that is how to display a large number of States. The methods of flinto and principle are presumably also frustration, and they can only rank each level in some order on the ground.

650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M01/8A/DE/wKioL1g-NIGAwi9gAAEV_S0elM0541.jpg-wh_500x0-wm_3 -wmp_4-s_991351613.jpg "title=" flinto.jpg "alt=" Wkiol1g-nigawi9gaaev_s0elm0541.jpg-wh_50 "/>

Second, the component-centric

Prototype prototyping tools such as Axure, Justinmind, and mockplus are inherently capable of generating components, and it is natural that components become the center of the interaction between software settings for such tools. Most interactions are implemented by changing the properties of the component, making the entire design process flexible. And it is this flexible design method in the software development of the early requirements of the expression can be really fast and effective.

It is believed that many users have not harvested the original expectations after upgrading the new version of Axure, but Axure is still the most user-designed prototype tool. Its design operation mode also provides the reference for many similar tools, even can say, there are many prototype design tools are imitating axure. The mockplus reduces setup steps with high visibility on the settings and can still be agile when faced with a large number of interaction settings.

However, when the interaction is set to a component rather than a page state, the overall length of the project is much smaller. Axure support for interactive features is richer. Mockplus is not to be outdone, especially its grasp of the degree of visualization. It uses a drag-and-drop approach where the design process becomes visible, and the chain is hidden after the setup is over, so even if there are dozens of interactive settings within the page, it does not affect the overall visual effect.

650) this.width=650; "Src=" Http://s5.51cto.com/wyfs02/M02/8A/E2/wKiom1g-NI_ycDKsAADGvHjh55g572.jpg-wh_500x0-wm_3 -wmp_4-s_2645388479.jpg "title=" mockplus.jpg "alt=" Wkiom1g-ni_ycdksaadgvhjh55g572.jpg-wh_50 "/>

Whether it's a page state-centric or component-centric approach, the best way to prototype is to have a relative population. In the early stage of development, axure and Mockplus are obviously dominant in the demand presentation. Flinto for Mac and principle can be more effective in later presentations. The right tools can be selected in combination with requirements.

Page status or component? What exactly is the center of interaction?