ONE SUBJECT · THREE WAYS IN

Understand dApps at your own pace

What is an application? What does the “d” change? Why decentralise a service? Start with these foundations, then choose how far you want to go.

Free · No wallet connection · 2 explained situations per level

Choose your explanation

Start simply, or go straight to the details. You can switch at any time.

Very simple

Beginner · Applications, decentralisation and its purpose: foundations before examples.

First, what is an application?

An application is software designed to provide a service. It receives information, follows instructions and displays a result. You can use it on a phone, on a computer or in a browser. A dApp is also an application: the “d” describes how part of that service is organised.

1. An application is more than what you see

Buttons, menus and screens make up its interface. Behind them, code processes requests and data is stored. Everything may run on your device. But many online services also use servers: remote computers that respond to users’ requests.

When we compare a dApp with a “traditional” application here, we mean this second case: an online service whose essential programs and data are managed by an operator. Not every ordinary application follows this model.

2. Centralised: an operator holds control

In a centralised application, a company or organisation administers the service: it manages the servers, database and program that applies the rules. Users depend on this operator for that part of the service to work.

“Centralised” does not mean “one computer”. A company can use thousands of servers across several countries while retaining sole control. Having more machines does not automatically distribute decision-making power.

3. The “d” stands for “decentralized”

dApp is short for “decentralized application”. The idea is to distribute some functions and their control among multiple participants rather than entrusting them entirely to a single operator.

In the blockchain dApps discussed here, important service rules are executed and verified by a network. A blockchain maintains a shared record: different participants can check operations against the same rules. A smart contract is a program on that network that applies rules. It is not a contract that thinks or makes decisions on its own.

The screen can look almost identical to a traditional application. The change is behind it: for the operations concerned, you rely on the network’s rules and shared program, rather than asking only one company’s server to decide and record the outcome.

4. Traditional app or dApp: the differences

Compare a centralised online application with a dApp whose important functions rely on a public blockchain.

Who applies the rules?
Traditional application: a program managed by the operator on its infrastructure. dApp: for the on-chain part, programs executed and verified under the network’s rules.
Who maintains the essential data?
Traditional application: the operator administers its database. dApp: on-chain data is kept in a shared record checked by network participants. Other data may still live on ordinary servers.
Who can change how it works?
Traditional application: the team controlling the service can update its programs and database. dApp: it depends on the permissions provided. Some rules are fixed; others can be changed by administrators or a vote. Check the particular project.

5. What is the point of decentralising?

The aim is to reduce dependence on one party for certain operations. This can be useful when several people or organisations want to use common rules and data without giving one of them exclusive control over the whole system.

Being able to verify
On a public blockchain, recorded operations can be examined. A user or another program can check an outcome instead of relying solely on what the website displays.
Sharing rules across applications
Different interfaces can use the same programs accessible on the network. The service does not necessarily have to be tied to a single website.
Reducing dependence on one access point
If a website shuts down, on-chain programs may remain usable through another interface, provided the network operates and the contracts remain accessible. This does not guarantee that the entire dApp will continue without interruption.

6. Why not decentralise everything?

Coordinating a network adds constraints: possible fees, delays and harder error correction. Data placed on a public blockchain is visible; it is not a private vault for personal information.

A traditional application may be easier to maintain, faster and better suited to private data. Decentralisation is an organisational choice that suits some needs, not an automatic mark of quality.

A dApp can still depend on a website, data provider or administrators. It can have bugs. “Decentralised” therefore means neither “nobody is responsible”, “impossible to block” nor “risk-free”. The useful question is: which functions are actually decentralised, and who retains which powers?

Now an example: a directory of names with ENS

A directory links a name to an address. A traditional application could provide this service by keeping the associations in its operator’s database. ENS, a real naming system, relies on Ethereum and its programs to manage these associations. Different compatible applications can look them up. The on-screen result may look similar: the difference lies in how names and permissions are managed behind it.

  1. The service

    Find an address from a readable name.

  2. The shared part

    ENS uses data and rules on Ethereum.

  3. The interfaces

    ENS Manager and other compatible applications use this system.

The directory analogy explains this particular use. Not all dApps are directories. Looking up a name transfers no money and does not certify its owner’s identity.

Check what you understood

Read the clues and explain your choice. Each answer has its own explanation; you can try again or read the full solution directly. These situations are fictional.

SITUATION 1 / 2

A company describes its application as decentralised.

  • It uses 100 servers spread across several countries.
  • It alone controls those servers, the program and the database.

Is that enough to call the service decentralised?

Choose one answer
Read the full explanation

Answer: No: control remains with a single operator.

  • Yes: many servers mean decentralisation.

    The number of machines describes distributed infrastructure. Here, control remains concentrated in one company.

  • No: control remains with a single operator.

    Correct. The key question is who controls and verifies the operation, not just where the computers are located.

  • Yes: having many users is enough.

    The number of users does not automatically give them control over the service’s rules or data.

Remember: Geographically distributed infrastructure can still be centrally controlled.

SITUATION 2 / 2

Several organisations want to use a shared record.

  • They want to be able to verify operations.
  • None wants another to administer the record alone.
  • They must also examine costs and data confidentiality.

What could be the benefit of a decentralised solution here?

Choose one answer
Read the full explanation

Answer: Sharing verification without giving one organisation all the control.

  • Guaranteeing that all data will be private.

    A public blockchain does not guarantee confidentiality. That requirement must be considered separately before choosing an architecture.

  • Removing every cost and risk.

    Network coordination, mistakes and dependencies still matter. Decentralisation does not make them disappear.

  • Sharing verification without giving one organisation all the control.

    Correct. That is the need to examine here. They must then check that the solution really distributes control and meets their cost and confidentiality requirements.

Remember: Choose a decentralised structure to meet a need for shared control, not just because the word sounds modern.

↑ Choose another explanation

Other questions about dApps

What does dApps mean?

dApp stands for “decentralized application”. dApps is simply the plural. This guide uses Ethereum-based applications as examples; dApps can also run on other networks.

Do I have to buy crypto to understand dApps?

No. This guide and its exercises are free, with no account or wallet connection. Using a real service is a separate decision: transactions can incur fees and financial operations can cause losses.

Does every dApp need its own token?

No. Having a token with an application’s name is not what makes it a dApp. Ask which part of its operation relies on a decentralised network. Network fees and any token used by a service are separate questions.

Does disconnecting remove spending permissions?

Not necessarily. Disconnecting the website and revoking an existing token spending approval are different operations. The permissions workshop explains the distinction.

Sources and further reading

Page updated on
Documentation checked on · WhyTheBlockchain · Editorial approach