Specifications will help the developer to transfer the ideas of the designer e.g. After completing and reviewing the wireframes, the specifications were created describing the application interface in detail. Afterwards these ideas were transferred into wireframes (using Balsamiq and AXURE) and the wireframes were implemented into prototypes. Then paper and pen were used for the first drawings. These give us stepwise perspectives to the project. Starting the wireframing processįor a schematic view, flowcharts were created. It is the pivot language that developers, customers and project managers can understand. The main advantage’s about wireframing is to reify the UI concretely avoiding misleading and wrong interpretations. These functions and/or interface elements can be represented as outlines or detailed images. Planned functions of the applications can thus be made tangible and visualized, as well as how they can be used and accessed.
#Wireframe axure rp software#
They can be drawn with pen on paper or software tools. Wireframing is done during conceptual design of an application (before starting the real development phase). This blog posts presents two tools we’re using for this purpose: Axure RP and Balsamiq. To support us during those development, we have looked into tools satisfying our needs (quick development, support all the possible interactions, understandable results) as well as our customer’s needs. Those prototypes are developed early in the development process, and so open discussion about the final UI. To avoid too late changes, we propose, to our customers, prototypes of applications, tangible regarding interactions and UI design. Indeed, UI changes do not only impact the UI layer, but may also require not planned features and architectural changes.
Changing UI is expensive in term of time and resources. One of the main goals of agile development is to improve the reaction to changes.
0 kommentar(er)
