ABCDEF
1
A Framework for Evaluating DeFi UX
v 0.1
2
by J. Roinevirtaroinevirta.id
3
To edit this file and complete your own DeFi evaluation, click "File" and then "Make a Copy"
4
SectionTopicsHelpful QuestionsNotesTop issuesScore (1-5)
5
User Experience
6
Interfaces & UsabilityClarity and conciseness of the interfaces.Does reality match expectations?; Are the interfaces clear and concise?
7
Legibility factors like font size and contrast.Are the interfaces easily legible (font, contrast)?
8
Use of visual elements and cues.Does the product utilise visual elements and cues to direct the user?; Does the user always feel in control?
9
Consistency and integration of interface components.Does the product work?; Are the interfaces continuous?; Do the components used in the application work together?
10
Error state communication and handling.Are error states handled graciously?
11
Ease of use.Are multiple click user journeys collapsed into as few clicks as possible?; Does the user need to sign unnecessary transactions?; Can you easily exit your positions?
12
User Assistance & DocumentationAvailability and quality of user documentation.Are the documentation easily accessible and well-written for the target audience?
13
Ease of finding details about product mechanisms and security assumptions.How easily can I understand the mechanisms of this product?
14
Use of industry jargon vs. user-friendly language.Does the product use accepted industry lingo or, better, easy to approach explanations?
15
Accessibility of customer support and quality of help available.Does the app suggest adding chains, tokens, or other dependencies to the support applications (e.g. wallet) where necessary?; Can I get help?
16
Onboarding & AccessibilityEase of the onboarding process.How easy is the onboarding process?; Are there unnecessary onboarding steps?
17
Support for account abstraction and transaction minimisation.Is account set up easy when account abstraction is used?; Do I need to fund AA wallets for gas?
18
Multilingual support and its necessity.Is there multilingual support? Is it needed?
19
Accessibility across various devices, screen sizes, and browsers.Does it work on most common user device combinations?
20
Error Management & FeedbackLogging of errors and user notifications.Are errors sufficiently logged?; Is the user sufficiently informed of error states?
21
Handling of product availability issues.When the product is not available, are the users sufficiently informed?
22
Subscription options for security and uptime notifications.Can I subscribe for alerts?; Can I inspect service status in a third service?; Can the users subscribe to security and uptime notifications?
23
Weighted score#DIV/0!
24
Product Quality
25
Performance & CompatibilityApp loading speeds.Does the app load quickly?
26
Support for common wallets and integration of chain dependencies.Does the product support most common wallets, where applicable?
27
Compatibility with different operating systems and browsers.Is the product widely accessible across geographies, screen sizes, input devices, browsers, and operating systems?
28
Is the product available?Does the product load or is there a lot of downtime?
29
Security & ComplianceHistory and outcomes of security audits.Is the product audited? If yes, how? Is this communicated correctly? Does the current version run that version or something else?
30
Communication of security measures and audit results.Are audit outcomes accurately communicated?; How easily can I find details about the security assumptions of this product?
31
Ease of contacting security researchers.Can security researchers easily get in touch with the developers?
32
Transparency of contract addresses and authoritative information.Is important information, such as contract addresses, provided in an authoritative source? Are there discrepancies?
33
Compliance with data privacy rules.Does the product transmit my data before I allow it?; Is my data shared to third-party vendors?
34
Centralisation risks.Can the users utilise secondary interfaces?; Do the users need to rely on a singular front-end? Can a technical user use open-source code to access the application?; Is there an immutable version of the front-end (e.g. IPFS)?
35
Transparency & DocumentationTransparency regarding risks, fees, and expected returns.Are implicit assumptions sufficiently communicated, given the target audience?; Is the product upfront and transparent about risks, fees, and return profiles?; Is the user documentation comprehensive and helpful?
36
Availability of tools for position management and analytics.Is data verifiable?; Are there tools for position management?; Are there analytics tools?
37
Clarity and accuracy of financial data representation like PnL.Are PnL and other financial figures correctly booked and represented?
38
Understandability and documentation of transactions on the blockchain.Are transactions and function calls clearly labelled on the blockchain for future use? Are these documented somewhere?; Do functions use common interaction patterns?; Is the user documentation comprehensive and helpful?
39
Integrations & DependenciesUse of third-party dependencies and data sharing.Are third-party dependencies minimised?
40
Support for multichain interaction and chain switching capabilities.Are priority fees and similar set correctly where applicable?
41
Access to data and metrics without needing wallet connection.Can I access data and metrics without connecting a wallet?
42
Weighted score#DIV/0!
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100