<p>Decentralized applications (DApps) are applications running on a blockchain and enable what has been coined Blockchain 3.0. They represent an evolution in digital technology, offering transparent, secure, and unmediated solutions. However, despite their considerable potential, the adoption of DApps remains limited. With this article, we aim to identify the main obstacles to DApps adoption, and propose recommendations for DApps developers, including recommendations about improving the User Experience (UX) and facilitating onboarding within these applications. Through qualitative interviews with experts, followed by the analysis of 25 DApps, we elicit and analyze the necessary requirements to address these issues. This paper has both practical and theoretical implications. Specifically, the resulting requirements will guide developers and entrepreneurs when designing a DApp by highlighting the various functional and non-functional requirements to take into account to increase the likelihood of user adoption. Furthermore, the findings contribute to the body of knowledge pertaining to the software engineering of DApps, a field that has been recognized as important by the research community. Notably, we discuss requirements engineering- and UX-related challenges, as well as best practices to implement for better DApp adoption.</p>

错误:搜索内容不能为空,请输入英文关键词
错误:关键词超出字数限制,请精简
高级检索

Decentralized applications: a requirements engineering perspective

  • Justin Compère,
  • Sarah Bouraga

摘要

Decentralized applications (DApps) are applications running on a blockchain and enable what has been coined Blockchain 3.0. They represent an evolution in digital technology, offering transparent, secure, and unmediated solutions. However, despite their considerable potential, the adoption of DApps remains limited. With this article, we aim to identify the main obstacles to DApps adoption, and propose recommendations for DApps developers, including recommendations about improving the User Experience (UX) and facilitating onboarding within these applications. Through qualitative interviews with experts, followed by the analysis of 25 DApps, we elicit and analyze the necessary requirements to address these issues. This paper has both practical and theoretical implications. Specifically, the resulting requirements will guide developers and entrepreneurs when designing a DApp by highlighting the various functional and non-functional requirements to take into account to increase the likelihood of user adoption. Furthermore, the findings contribute to the body of knowledge pertaining to the software engineering of DApps, a field that has been recognized as important by the research community. Notably, we discuss requirements engineering- and UX-related challenges, as well as best practices to implement for better DApp adoption.