Web Applications (General-Purpose)

2.10.1Definition & Purpose

A general-purpose web application is any browser-based product built around user interaction and state — creating, editing, and manipulating data — that doesn't fit neatly into a more specific category like e-commerce or SaaS. Tools, calculators, converters, and single-purpose utilities commonly fall here.

2.10.2Architecture Priorities

State management — tracking what the user has done within a session and, where relevant, persisting it — is the central technical concern. Whether state lives client-side only, or is synced to a server, is a foundational early decision that shapes everything downstream, directly connected to the static/dynamic classification in Chapter 1.4.

2.10.3UX Priorities

• Immediate, responsive feedback to user actions — the interactive core of the product is the entire value proposition.
• Clear handling of unsaved state, especially where data could be lost on navigation or a closed tab.
• Progressive disclosure of complexity, so simple use cases stay simple even if the tool supports advanced ones.

2.10.4Common Mistakes

• Losing user work silently on navigation, refresh, or connectivity loss with no warning or recovery.
• Building for the most advanced use case first, making the common, simple case unnecessarily complicated.

2.10.5Best Practices

• Persist meaningful in-progress state automatically wherever feasible, rather than relying on the user to manually save.
• Design for the most common use case first; layer advanced functionality on top without cluttering the default experience.