![]() Let us consider an example, to understand this better. A particular interaction can be a constitution of multiple cases. ![]() Following are some examples of Object or Widget Level Events.Īs discussed in the previous chapter, in the page properties section, a particular widget interaction can be designed. Now, for interacting with this button widget, maybe by touch (on mobile prototype) or a mouse click. Let us consider, we have created a page and a particular button widget on the page. Following are some examples of Page and Master Level Events. As these events take place during the initial page load, you can consider that these events will be repetitive on every page load. When a page loads, there is a plethora of events happening to fetch the design information, content, and hence, the alignment of every single element on the screen. The events in Axure can be of two types, triggered by two types of events. Let us consider the page loading when the browser loads the page you can simply select a particular slideshow to begin or have an image grow bigger when entered on the screen. It can be a simple screen element such as a rectangle, which we want to turn into a clickable button for the purpose of a menu (example shown later).įinally, there is the description of What is happening in the interaction. Then comes the question, Where on the screen the interaction is taking place. For instance, when the page is loaded in the browser, when the user clicks on one of the elements, etc. Typically, the interactions will begin with When the interaction is happening. This acts as a catalyst to show the intended design and interactions on the page. While generating HTML prototype, Axure RP converts the interactions into the real code (HTML, CSS and JavaScript). To make it a simple approach towards interactions, Axure eliminates the need to code the prototype by providing an interface for defining structures and logics. Interactions is the term coined for the functional elements that transform a static wireframe into a clickable interactive prototype. This is the reason why, it makes sense to start with single important interactions at a time, in order to sprint through the rest of the available pages. ![]() Now, when it comes to making the interactive prototypes, there is always a caveat of creating an overly interactive prototype. The purpose of Axure RP is to allow interactive prototypes. This chapter will take you through the basic interactions set provided by Axure when designing a screen.
0 Comments
Leave a Reply. |