Home | History | Annotate | Download | only in design-navigation

Lines Matching full:application

25 <p>Most apps have an inherent information model that can be expressed as a tree or graph of object types. In more obvious terms, you can draw a diagram of different kinds of information that represents the types of things users interact with in your app. Software engineers and data architects often use entity-relationship diagrams (ERDs) to describe an application's information model.</p>
27 <p>Let's consider an example application that allows users to browse through a set of categorized news stories and photos. One possible model for such an app is shown below in the form of an ERD.</p>
31 alt="Entity-relationship diagram for the example news application" id="figure-erd">
33 <p class="img-caption"><strong>Figure 1.</strong> Entity-relationship diagram for the example news application.</p>
38 <p>Once you define the information model, you can begin to define the contexts necessary to enable users to effectively discover, view, and act upon the data in your application. In practice, one way to do this is to <em>determine the exhaustive set of screens</em> needed to allow users to navigate to and interact with the data. The set of screens we actually expose should generally vary depending on the target device; it's important to consider this early in the design process to ensure that the application can adapt to its environment.</p>
40 <p>In our example application, we want to enable users to <strong>view</strong>, <strong>save</strong>, and <strong>share</strong> <em>categorized</em> <strong>stories</strong> and <strong>photos</strong>. Below is an exhaustive list of screens that covers these use cases.</p>
61 alt="Exhaustive screen map for the example news application" id="figure-exhaustive-map">
63 <p class="img-caption"><strong>Figure 2.</strong> Exhaustive screen map for the example news application.</p>
70 <p>At this point, it's possible to design a completely functional application from this exhaustive screen map. A simplistic user interface could consist of lists and buttons leading to child screens:</p>