On this page
Scott
Scott

Published on Sep 24, 2024, updated on Nov 02, 2026

Web app design defines how someone completes a task in a browser: finding a record, changing data, understanding the result and recovering from an error. That means designing states, permissions and return paths alongside the arrangement of elements on the page.

Consider an invoice editor: a team member changes a due date and needs to know that the saved record is the one their colleague will see. Use a web design workspace in Pixso to map those screens and discuss the behavior before implementation. The five examples below offer layout ideas; the worked invoice scenario shows the decisions a polished first screen cannot explain.

web app design

How a web app differs from an informational website

An informational website primarily helps people read and find material. A web app supports stateful actions such as creating a record, changing access, saving a form or collaborating. One service can do both; the distinction helps you design a particular task rather than assign the whole site a rigid category.

The historical interfaces below illustrate parameter editing and animation controls. They are useful examples of tool-like screens, not a modern development recipe or proof that every web app began in one year. For a new application, the important question is which changes persist and how a person knows their action succeeded.

java applet

Historical Java applet example; the retained illustration is attributed to Wikipedia.

future splash animator

Historical FutureSplash Animator interface; the retained example is attributed to Web Design Museum.

Must-follow Principles of Web App Design

Simplicity

Simplicity is the best approach when it comes to the user experience and usability of your web app. Here are some strategies for designing for simplicity.

Color

Give colors roles: primary action, text, border, warning and success. A small palette is easier to maintain, but there is no universal five-color limit. Keep important states understandable through text or shape as well as color.

Type

Choose readable typography and a clear hierarchy for page titles, field labels, help text and data. A short, consistent type scale is more useful than a universal limit on font families. Test long values, small labels and browser text enlargement.

Imagery

Use imagery when it helps explain an object or decision: a product photograph in a catalogue, a chart for a comparison, or a preview of the selected file. Decorative images should not compete with field labels, saved values or important warnings.

Navigation

Web apps use navigation as their wayfinding system so that users may interact and find what they're looking for. Maintaining visitors on a website requires good navigation. If a website or web application's navigation is difficult, users will give up and look elsewhere for the information they need. The goal is to keep navigation clear, easy to use, and constant throughout each page.

F-shaped Pattern Reading

People scan different screens in different ways. An F-shaped reading pattern can describe some text-heavy pages, but it is not a mandatory layout for an application. On an invoice editor, the total, due date and save result should be easy to locate because they matter to the task. Use hierarchy and meaningful labels, then observe whether readers find them.

f shaped pattern reading

Visual Hierarchy

The grouping of items according to importance is known as a visual hierarchy. Size, color, images, contrast, font, whitespace, texture, and style are some ways to do this. Creating a focal point, which directs viewers to the location of the most crucial information, is one of the visual hierarchy's most critical roles.

Content

Content in an application includes field labels, empty states, validation, permissions and confirmations. “Saved” is different from “Saving…”; “You can view this invoice” is different from a disabled button with no explanation. Write these messages while designing the screen.

Grid-based Layout

Grids support design organization and content organization. The grid makes the page look neat and aligns the elements on the page. The grid-based layout produces a web app with a nice appearance, which organizes content into a fantastic, rigid grid structure with columns and sections that feel balanced and impose order.

grid based layout

Friendly for Mobile

At a narrow width, preserve the task rather than squeezing every desktop column into view. Put the record identity and primary action within reach, allow supporting fields to follow, and test the form with the on-screen keyboard open. Keep entered values when moving between layouts.

Worked example: edit an invoice without losing changes

In this instructional example, a team member opens a draft invoice, changes its due date and saves it. An editor can make changes, a viewer can only read, and an already-paid invoice cannot be edited through the same action. These are rules for the example application, not a built-in invoicing feature in Pixso.

Define the outcome first: the person knows which invoice changed, which date was saved and whether anything remains to do. Then map the states that could prevent that outcome.

SituationWhat the interface showsWhat must survive
Draft openedInvoice number, recipient, total and current due date; actions appropriate to the roleA clear route back to the list
Unsaved date enteredA recognizable changed state and Save actionThe entered value while another field is corrected
Save in progressSaving feedback; prevent accidental duplicate submissionThe invoice context and proposed date
Save confirmedThe saved date and a clear outcome beside the recordThe same value in the form and list
Connection interruptedDistinguish a known rejection from an unknown outcomeThe draft and a way to check the outcome before retrying
Another editor changed the recordA conflict explanation and a comparison/recovery pathThe local input, so it need not be reconstructed from memory

Cancel before saving restores the original date. Leaving the page with unsaved changes needs a separate decision: preserve a draft or explain the loss before navigation. Deleting an invoice is a different action, so do not make it resemble canceling an edit.

On return to the invoice list, preserve the agreed filter and selected record. If a person loses edit permission mid-task, explain why saving failed and retain useful input where permitted. Permission denial, no records, field validation and a network failure need different messages.

Test the outcome, not just the button

A task could be: “The supplier agreed to payment by November 18. Update this invoice and make sure your colleague will see the new date.” Observe whether the participant finds the record and understands the saved result without a button hint. Then show an error or conflict variant. The question is whether the task can be completed, not whether the screen looks polished.

Build the connected states in Pixso

Place the invoice list, edit form, confirmation, error and conflict states in one file. Make repeated fields and actions reusable components, and use Auto Layout to examine long names and narrower screens. Connect the states in a prototype so the team can walk through the same task.

Beside the screens, explain when the action is available, what counts as a successful save and where the user returns. Comments attached to a specific state keep the discussion concrete. The prototype communicates intended behavior; permission checks, persistence and concurrent edits still need implementation and testing in the application.

Pixso illustration showing interface layouts in the design editor

Technology decisions that change the interface

Do not choose architecture because it appears on a trend list. Agree with developers how each choice affects the task:

  • Navigation without a full reload: what do the page URL, Back action and a direct link to a record do?
  • Unreliable connectivity: can a draft be edited, and how are local changes distinguished from saved data?
  • Concurrent editing: how is a conflict detected, explained and recovered without losing input?
  • AI assistance: where can a person inspect, accept and undo the result?
  • Motion: which state change does it explain, and is that meaning clear without animation?

Five web interface examples

These retained screenshots show earlier versions of the sites. Use them to study visible layout decisions; a static image cannot establish current behavior, accessibility or conversion performance.

Vinted 

Vinted is an online marketplace where you can buy and sell secondhand and vintage clothing and accessories. 

The saved Vinted screen separates starting a listing from browsing products. This makes two different visitor intentions visible near the top of the page. In a similar marketplace, check that those actions lead to distinct, understandable next steps.

Filters and search options help Vinted structure its listings so users can easily browse.

vinted

Reed

The Reed example represents a job-search interface, with vacancies and search conditions presented together.

The saved Reed example places filters beside a job list. The selected location, salary and job type provide context for the results. In your own application, keep applied conditions visible when the list changes and explain an empty result.

reed

Zencastr

With the help of the online podcasting tool Zencastr, users may record and edit podcasts directly on the website.

The Zencastr screenshot separates a recording action from the media area. This suggests where to place the primary action, but it does not show microphone permission, connection failure or a stopped recording; those states need separate design.

zencastr

The Plum Guide 

The Plum Guide example represents accommodation search, with property imagery supporting the choice of a place to stay.

The Plum Guide example puts destination, dates and guests together in a search area. Grouping related input helps communicate one task; field labels and error states still need to work when a value is missing.

Study how property imagery supports browsing without hiding the search task. Once a property is selected, availability, price and conditions must be confirmed in the appropriate next step; the screenshot does not establish those interactions.

plum guide

Skyscanner

The Skyscanner example presents travel-search controls for routes and dates.

skyscanner

The saved Skyscanner screen places the search area prominently beneath the main navigation. This makes the starting task easy to identify. Currency and language controls need clear names and should preserve the search when changed.

For a narrow version, decide which search fields stack and where the submit action remains visible with the keyboard open. Preserve entered dates and destinations across the change in layout.

Start with one complete task: finding a record, confirming a change and recovering from failure. Once those states are clear, the examples above can help you choose a visual structure without substituting decoration for application behavior.

Back to top
Share on X
Share on Facebook