What are dApps, and How Can They Improve Services?

What is a dApp?

  • Open Source. Provided that the code of a dApp is approved in consensus by the members of the network, the source must be available for review. On the contrary, regular apps’ source code is usually kept private and out of reach by the users.
  • Decentralized Consensus. Before cryptocurrencies were developed, the only method of validation available was through a central authority. In a decentralized scheme, most nodes have to approve each transaction to make it valid. Contributors get tokens in return.
  • No Central Authority. Whenever a node in a P2P network fails, only such devices stop working. Therefore, the rest of the system remains operative, and users do not see the disruption. In a centralized architecture, server failure means no service.
  • Integrated Payments. There is seamless integration with cryptocurrency payments by default. dApps based on the blockchain serve of its network to send and receive crypto, such as the Ethereum blockchain — the most popular platform for dApps. In the Woonkly platform, you can make use of our native token, WOONK, to use services.
Photo by Thought Catalog on Unsplash

What are dApps Better For?

  • Fault-Tolerant. It is impossible to have a dApp down due to node failure. Moreover, a hacker cannot vulnerate enough nodes to take control over the consensus due to cryptography — it takes too much time and computing resources.
  • Internet Censorship Prevention. In relation to the previous feature, no entity can govern a dApp due to the nature of decentralization. The service does not depend on a single IP. Thus a distributed network cannot be censored by an authority.
  • Increased Trust on the System. Users can be more confident with a dApp because their data is not prone to be manipulated. This is why sometimes dApps are described as “trustless” because you already know how your data will be used beforehand.

Inconveniences of dApps

  • Fixing bugs is not easy. When you publish an update, you need to distribute updates to each device in the network. That is, not only one server should be updated, but every version of the dApps needs to be in sync to make use of a newer version.
  • KYC is not easy. In centralized apps, KYC is often under the surveillance of one entity. Thus, the process is organized accordingly, but complications arise when you perform the decentralized counterpart. Different approaches are possible to solve this issue, like having a hybrid centralized and decentralized ecosystem.
  • Complex to scale. Scalability is another challenge for dApps due to the complications with protocols used in making the software run distributed. Basically, it would be helpful if you planned in advance to make it possible for your dApp to grow enough while serving users correctly.
  • Undervolved Third-Party dApps. Imagine that your app needs a delivery system, but that is not your niche. In centralized apps, you may use APIs to integrate the service seamlessly. Unfortunately, this is not — always — the case with decentralized apps. Due to dApss immaturity, in most cases, you need to create each service, which demands more resources.
  • Fixing bugs is resource-intense and time-consuming.
  • You may need to build a KYC solution for your dApp.
  • No third-party APIs means you are alone in the dark.

The Future of dApps

Photo by NASA on Unsplash

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store