Learning library / Software foundations
What is an application?
An application is software people use to accomplish a task. It might run in a browser, on a phone, on a desktop, or on a device you never see.
Explore this guideA job, a set of rules, and a useful result.
A grocery list that remembers staples, a roster that coordinates shifts, and a booking tool that confirms an appointment are all applications. Each accepts an input, applies rules, and gives someone a result they can act on. The interface might be a screen, a voice prompt, an email, or an interaction with physical hardware.
A brochure website primarily explains and presents information. An application lets people do something with that information. The boundary is not rigid: a website can gradually gain search, accounts, saved preferences, forms and workflows until it behaves like an application.
Ask what changes after the person acts. If they submit a request and the system checks a rule, saves a record, alerts someone or shows a different state to another user, you are describing application behaviour. A simple site can contain one application feature without every page becoming an app.
The same job can be delivered in different ways.
A web app opens through a URL; a native app is built for a device platform; a desktop app runs on a computer. Some tools work offline, some depend on a connection, and some combine a physical product with a digital service. These are delivery choices, not measures of quality.
For an early product, ask where and when the task happens. A field worker may need limited-connectivity support. A public catalogue may benefit from shareable URLs. A team operations tool may need permissions, audit history and reliable integrations. The answer can also be a simple website or a physical service rather than new software.
Make the smallest complete promise.
A first release should let a defined group complete one meaningful job end to end. A grocery product might begin with adding, grouping and checking off items before it attempts provider deals, stock forecasts or social recommendations. This makes the product testable without pretending the wider roadmap is finished.
A team roster is another example: a useful first release needs a dependable way to collect availability, propose shifts and show an approved plan. An attractive calendar alone would not resolve who can approve a change or what happens when two people edit at once.
Write down the intended user, the situation they are in, the action they need to take, what success looks like, and what would make them stop using the product. Those answers become a brief for the interface, data model, release plan and measurement.
A launch creates an operating responsibility.
Software needs someone to handle feedback, defects, changes, accounts, security updates and support. The people who operate the product need access to its source, hosting, documentation and decision history in the form agreed for the project.
Before commissioning a build, decide who will own the product, who can approve changes, who receives incidents, and what happens when the original team hands over. A technically working app can still fail its users when no one owns these everyday decisions.
Use this in a project
Questions worth answering together.
These make the idea concrete before the team commits to a design or release plan.
- 01
Who has the problem, and how do they solve it today?
- 02
What must a person be able to complete in the first release?
- 03
What data, devices or places does the task depend on?
- 04
Who will operate and improve the product after launch?
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.