dappOS connects work behind the screen
dappOS connects work behind the screen The point where Web3 gets stuck is not the functionality, but the execution order. Even if the user decides what they want to do, they have to go through the chain, wallet, fees, movement between chains, and approval steps one by one. The longer this grooming goes on, the more the service feels like a process with a lot of preparation rather than a simple app. In the end, the problem is not the screen, but the adjustment costs behind the scenes. Even if you do the same thing, the rules are different for each chain, so it is difficult to use the method yo…
The excerpt is quoted from a public Telegram channel, which owns its text.