> For the complete documentation index, see [llms.txt](https://wp.lovely.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp.lovely.finance/defi-as-the-moment-is-facing-some-challenges/user-friendliness.md).

# User-friendliness

Most Decentralized Applications, otherwise called dApps, are not friendly to the general users. We believe that if we must import people from Web2 to Web3, then create seamless onboarding solutions.

Not a UX-deficient product, which will leave them with no other option than to return to their Web2 apps. We made this huge discovery after some thorough and candid product surveys and feedback.

While many projects are so heavy on the technical and development side of things, we have built interest equally in building intuitive designs of market-fit products.

From the survey, we also discovered many users do not care to know intricate details about nonces, hashes, smart contract events, and some other technical jargon.  Quoting an anonymous potential user, "I simply wanna send money. That's all. Save me the jargon."

This is one of the current problems with Web3 products and we are ready to do the hard work of breaking those barriers.

Our engineers, designers, and product managers work hand-in-hand to ensure our products are simple. This aligns with the current wave of Account Abstraction in Web3.

We want to simplify DeFi for everyone, and handle all the heavy technicalities from behind. Thus, lack of user-friendliness is our first problem in Web3.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wp.lovely.finance/defi-as-the-moment-is-facing-some-challenges/user-friendliness.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.