Advency quick access

Go to :

Creating dAPP Web 3

The web 2.0

To understand what Web 3.0 is, we will first look at Web 2.0.

Web 2.0 is the internet that we know and use today: users who go to an application (web, mobile, software, etc.) will go there to access it.In other words, all users who visit an application (web, mobile, software, etc.) will go there to consume information, but they will also interact on these applications (messaging, online purchases, etc.) via one or more servers belonging to the owner entities. In other words, all exchanges between users and applications are centralized.

Everything that users publish is data that belongs to the entities that own the application, and they can do whatever they want with it. Today, this system is therefore largely involved in the privacy of users and consumers of the Internet;

The web 3.0

The objective of Web 3.0 is to decentralize this data by using a "Peer to Peer" system: data no longer passes through servers that belong to brands and entities, but is shared among all users who browse the Internet, and each one stores bits of information. This data is then reconstructed with a string of encrypted characters;

The published information is therefore no longer collected, analyzed and processed by third party companies. Users regain control of their data and reclaim the internet.

The DApp

A DApp is a decentralized application. It is therefore clear that DApps are opposed to the centralized applications that we know and use most of today. To function, they are made up of :

  • One (or more) strong contracts (better known as Smart Contracts): this is the structure of the dApp. The contracts are built on the Peer to Peer protocol which does not depend on a trusted third party;
  • A user interface
  • A distributed data storage model

In concrete terms, how does it work?

In an ordinary contract, there are (at least) two parties, and a third entity that manages the contract and arbitrates the rules. We will therefore address this third party for any interaction concerning the contract.

Smart contracts are built on the Web 3.0 model: the parties establish a contract that is coded and encrypted, and decentralized between all internet users: there is no longer any need to address a third party.

dApps are therefore applications (web, mobile, etc.) that use the properties of the blockchain to function :

  • Distributed and transparent: contracts are validated by all internet users, and all interactions with autonomous contracts are publicly recorded. One person cannot get hold of the contract and falsify its code, because the other users, who also have this coded contract, will invalidate it. Anyone can check the code of a dApps, which guarantees its security.
  • Immutable: once created and inserted in the blockchain, the contract cannot be changed. No one can take control of the contract.
  • Resilient : dApps are managed on hundreds of thousands of computers around the world. They therefore have a very high availability rate as they never stop working 
  • Protected data: the data is only held by the users of the dApps, which changes the relationship to data protection policies;

The Advency team is particularly interested in Web 3.0. and offers its expertise in the development of decentralized applications, in particular (but not exclusively) with Ethereum or Binance Chain, decentralized networks written in the "Solidity" language, whose code is close to that of Javascript.

The steps to create a dApp.

  • 1
    Understanding the need, framing
    • Kick-off workshop
    • Validation of needs and advice/advice
  • 02
    Graphic design (UX/UI Design)
    • Co-design workshops
    • Tree definition
    • Creation of mock-ups (clickable prototypes of the project), iterations until satisfaction
  • 03
    Technical design
    • Resume the need
    • Description of the functionalities
    • Writing of technical and functional specifications
  • 04
    Choice of blockchain
    • Ethereum, Binance Chain or other network
  • 05
    Creation of one (or more) stand-alone contracts
    • Definition of the actions to be performed automatically: whether it is a simple transaction, a chain of algorithmic calculations or something else, all of these auto-execution functionalities will have to reside in stand-alone contracts.
  • 06
    Creation of a centralized backend
    • In the case of massive data storage or the expression of a need for functionality that does not fall within the scope of blockchain transactions. The DApp then becomes a Semi-DApp.
  • 07
    Front-end development

    The part visible to the user with which he can interact;

  • 08
    Extensive testing and recipe
    • With a thorough quality assurance process
  • 09
    On line
  • 10
    Maintenance
    • Preventive (maintaining proper functioning, updates)
    • Corrective (handling requests via a special tool made available)
    • Evolutive (new functionalities, evolutions of the platform)

How about we discuss your project?

The first step is to listen and understand the need.
On the basis of a specification or directly in an exchange session (meeting or video), we listen to each creation or redesign project

Make an appointment

Accessibility