Information architecture

In order to decide the place in which every component makes sense, simple skeletons are incrementally built to structure the information in the application.

Goals

• Decide what should be shown in each screen

• Choose aproppriate position for the elements

• Think a little bit ahead so interaction will be ok with the architecture

• Rethink if the result is the expected one

Steps

  • Wireframes

    Step 1

    What

    Because designing is about what to have, but moreover what not to have. Thinking what is really needed and why. Discussing with the rest of the team and reaching consensus.

  • Mockups

    Step 2

    Where

    Given the decision to design a mobile application for Android system, usual constraints in cellphones such as different screen sizes (from tiny to huge), extremely glossy screens, etc have to be taken into account along with some design patterns for Android to define the structure of the system and organize the information.

  • Step 3

    Thinking in the next step

    In this design process it is necessary to think in the next step, the visual design. That is due to the fact that they are highly coupled. A extremely good information architecture could result in some constraints that could make a poor visual design.