Learning library / Software foundations

The different parts of an application

A useful app feels like one thing to its user. Behind the screen, several parts coordinate to turn an action into a trustworthy result.

Explore this guide
01 / The visible layer

The interface is where a person meets the system.

Screens, labels, forms, navigation and feedback make the system usable. The browser or device also runs client-side logic: it can validate an input, change a view, or request fresh information. A clear interface tells people what is possible, what has happened and what to do next.

The interface should not be asked to enforce sensitive rules by itself. A browser can be changed by its user; the server must check permissions and validate important actions before saving them.

Read the source: MDN: Client and server roles.

02 / The rules

The back end coordinates decisions and requests.

A server can check who is making a request, apply business rules, read or update records, send an email, or call another service. An API is a defined way for one part of the system to request data or actions from another. Not every small application needs a dedicated server, but any shared or sensitive workflow needs deliberate rules for where authority lives.

For a roster, the rule might be: only an authorised manager can publish a shift change, and a worker must be notified after the change succeeds. If the notification fails, the product still needs a clear record of what was published and what remains to be retried.

Read the source: MDN: Client-server request flow.

03 / The memory

Storage holds what should persist.

A database may hold accounts, lists, relationships and transaction history. Files may live in separate object storage. A browser can also keep local state, but that is not automatically a shared source of truth. The right design depends on what must survive a device change, be shared with others, or be recovered after a failure.

Data structure matters early. If a deal belongs to a provider, a customer and a product, those relationships should be represented clearly so the app can answer questions without duplicating conflicting records.

Read the source: PostgreSQL: Relational concepts.

04 / The running product

Identity, hosting and observation complete the picture.

Authentication identifies a person or service; authorisation determines what that identity may do. Hosting makes the system reachable. Deployment moves a reviewed change into a running environment. Logs and product analytics help the team find errors, understand real usage and decide what to improve.

These are not decorative extras. A product that can accept an order but cannot recover, notify its operator, or stop unauthorised changes is incomplete for that job. The depth of controls should match the sensitivity and scale of the product.

Use this in a project

Questions worth answering together.

These make the idea concrete before the team commits to a design or release plan.

  1. 01

    Which actions need an account or specific permission?

  2. 02

    Which information must persist or be shared across devices?

  3. 03

    What happens if a connected service is unavailable?

  4. 04

    How will the team detect and fix a failed action?

Further reading

Primary references.

Technical references for the concepts in this guide. The project advice and examples are our interpretation.

From concept to delivery

Bring us the question you are working through.

From Melbourne, Paradox Design develops bespoke web applications and operational software. We can help turn a product idea, existing workflow or technical concern into a clear next step.

External project website

Open this project site?

is hosted at . It will open in a new tab.