Thanks for the feedback @light!
Is the idea that the client would get launched in the user’s Web2 browser but loaded / authenticated via Frame’s IPFS/ENS integrations?
Yes and we plan to leverage our browser extension to make this feel really seamless. Also the ability to launch the client bundle from a shortcut and an optional
--app windowed ux in the future.
Will this notification mechanism be extendable to other dapps as well? So users could e.g. get a notification of a CDP liquidation, or a 0x order fill. My thinking is that a notifications feature should either be generalizable at the Frame layer, or should be left to individual dapps to offer to their users at the dapp layer (e.g. the Aragon client now has email notifications built-in).
We agree and yes in the future notifications could be created for any dapp but for now the focus will only be on Aragon DAOs.
My personal preference is to keep Frame as thin, lean, and mean of an application as possible. I have always loved Frame for its simplicity and laser focus on being a great interface between private keys and dapps. I would encourage Frame to stay this course and avoid straying into competing with dapp browsers or wallets, or getting too involved in the ux of dapps that Frame users are interacting with. There are great teams working at the dapp layer who know what their specific users need but will never be on Frame’s level. I think this creates a great place in the stack for Frame to fit into and own.
We’re still laser focused on connecting users, their accounts (private keys) and dapps. Our goal with this initiative is to make this connection even more clear and strong, especially for new users that have no prior knowledge of Frame’s position in the stack, or even that there is a stack. The majority of features here will be invisible to current users that already know how to setup and use their accounts with dapps, but we think it’s important to fill some of the initial gaps in understanding for new users.
There’s an ecosystem wide issue with onboarding and we feel like we can make a big difference here. If we want tools like Aragon to be adopted by large organizations and communities we think taking steps in this direction is necessary. A goal of Frame has always been that you should be able to tell someone to try it without feeling you also need to give them a tutorial on how to use it. We’re not there yet, especially for users that are new to the space, but we’re working hard to get there.
With Frame + Aragon you have everything you need to onboard a new user, even if they have no experience or prior knowledge of crypto. We think that’s a special relationship and we should capitalize on it.
Aragon currently doesn’t have any plans for a native mobile client. How do you see a mobile integration with Aragon working?
Our goal here is to make all of the integrations we create for Aragon available on all the platforms Aragon supports. This means being able to use your Aragon smart accounts even when you’re on mobile. We will be experimenting with how best to implement this functionality on mobile and gathering feedback from the community.