A dApp has its backend code running on a decentralized peer-to-peer network. ... Contrast this with an app where the backend code is running on centralized servers. A dApp can have its frontend code written in any programming language that makes API calls to its backend.
A dApp
has its backend code running on a decentralized peer-to-peer network. Contrast
this with an app where the backend code is running on centralized servers. A
dApp can have its frontend code written in any programming language that makes
API calls to its backend. Furthermore, its frontend can be hosted on
decentralized storage such as IPFS.
The
Key Difference Between Traditional App Development and dApp Development
The
biggest difference between dApp development and traditional app development is
the level of rigor by which code must be scrutinized before it’s pushed to
production. dApp development is more like hardware development than software
development in that respect. In hardware development, rigorous testing and
prototyping need to be done before the product is offered to the public. A
hardware recall costs lots of money, takes a long time to fix, and tarnishes
the reputation of the manufacturer. Likewise, in dApp development, a smart
contract can’t be changed once it’s launched on the main net. A bug in the
smart contract loses users’ funds and tarnishes the reputation of the dApp
developers.
Traditional
app development, in contrast, tends to emphasize fast iteration cycles as best
practice. As a developer, you want to build a minimum viable product, get
people testing the product, and release updated versions as quickly as
possible. Traditional apps like Facebook have the motto of “move fast and break
things,” which isn’t exactly the best motto for dApp development.
We
hope you have found this article informative and interesting. For more
information or queries contact us to know more about this technology.
Comments
Post a Comment