DCL Closet - Advanced Backpack Features
Proposal Details
Grant size
Tier
Beneficiary
Description
I seek to create a web application that will enable advanced backpack features to simplify and enhance the backpack experience and also reduce the need for backpack features inside of the current clients. Many of the features proposed by the community can be achieved including outfit saving, sorting and filtering, previewing multiple marketplace wearables at once and more. Why not create this as an addition to the current backpack? My main concern when designing this was that any additions to the current backpack would still run into existing issues with the backpack loading slow and not loading in high traffic scenes and at seemingly random times. The goal of this project is twofold: add additional features but also ease some frustration with the existing backpack reliability. I also like the idea that someone looking to build a new client can potentially leverage the closet app for their backpack functionality instead of building their own and can focus on the core client functionality. In addition, the majority of the new features require some external service to be built, to save outfits etc., which can be integrated faster and easier into the current backpack after they are built.
Voting Power
DCL Closet - Advanced Backpack Features This proposal has been ENACTED by a DAO Committee Member (0xbef99f5f55cf7cdb3a70998c57061b7e1386a9b0) Vesting Contract Address: 0x64f50Cf02f79416f6bc0675E31f7601A15B1ea92
DCL Closet - Advanced Backpack Features This proposal has been ENACTED by a DAO Committee Member (0xbef99f5f55cf7cdb3a70998c57061b7e1386a9b0) Vesting Contract Address: 0x8078195b4cab84500ef021198aa90b1d4333571e
DCL Closet - Advanced Backpack Features This proposal is now in status: PASSED. Voting Results: * Yes 99% 3,486,902 VP (106 votes) * No 1% 13 VP (2 votes)
Easy yes for me. Now, will you please help organize my real-life closet!!!
Having actively tested the prototype and then sent feedback on the proposal before it was posted (and hopefully contributed some good ideas heh) I can rightfully say this is a YES vote for me!
This is probably something I've been wanting and/or needing for a long time! I look forward to seeing what you do with this and would be cool to see something like this eventually develop into something integrated directly into DCL.
Thank you! My non-coder brain can understand this! :joy: I look forward to seeing what you will create!
I am voting YES. Mattimus is more that capable of making this happen. His skillset and organization is remarkable and I think this proposed project will add a dynamic that helps to further inspire more growth and provide a more immersive experience!
I know first hand Mattimus has the skills and knowledge to make this happen. He is an active DCL community member and is always willing to help anyone no matter who it is. YES vote coming in HOT!!!!
This proposal is exemplary of how we can improve DCL and grow the user base with the thoughtful dedication of the organization’s resources. Many of us know about the slow loading backpack at a party with auto-dance running. Solving that frustration is enough to get my attention. This proposal goes further and considers future extensions of DCL in as yet, unmade 3rd party clients. It creates opportunities for us all to talk with each other and interact more around things we are excited by and passionate about. It drives more sales to creators and thus helps sustain the DAO and DCL. I’ve experienced the early version of this application at the MVFW Summer Gala. This proto-version worked quite well and excited my imagination of where this app can offer next. Voting: YES
Thank you @dax , I agree that it is going to be much smoother as a standalone app and kept the scope of this proposal to just that. You are exactly right, for the final version with catalyst sync, the user will need to sign some message to be able to push updates via catalyst api. It will follow the same process w/ catalyst client using AuthIdentity and authChain setup as seen here: https://github.com/decentraland/marketplace/blob/48d15bcc20fb196eb860e9847e19a0f170ea65eb/webapp/src/modules/store/utils.ts#L132
Thank you for the support @Canessa , the idea was inspired by listening to many of the communities concerns. To be clear, this will live in a separate website outside of the DCL application with the following reasoning: [quote="dao, post:1, topic:14370"] Why not create this as an addition to the current backpack? My main concern when designing this was that any additions to the current backpack would still run into existing issues with the backpack loading slow and not loading in high traffic scenes and at seemingly random times. [/quote] Ideally, once the features are built out, it will be easier to integrate them into the existing explorer app and will have a lot more momentum with demonstrated community usage. However, it will require a separate chunk of work and some coordination with foundation team to see how feasible it will be and who will be responsible for hosting the backend services etc.
> The project will consist of a single “front-end” web application, created using next.js, and a server application and database to store outfits and any user related content. Additionally, existing decentraland foundation services (lambdas + catalyst apis) are used to fetch avatar and wearable data. I think it's a good idea to just make a standalone app for this, trying to integrate into the existing explorer is probably not worth the time or effort. >To use the app, paste in your wallet address under “Avatar Address” and your current avatar and backpack will load. To preview your avatar with someone else’s backpack, you can paste a different address into “Backpack Address” just to be clear though, you'd need to sign in via metamask to be able to sync your avatar with the catalyst servers, or is there another way to authenticate?
Mattimus this idea is GOLD. It's an easy yes for me. I know I'm one of the people with way too many wearables in my backpack, and I am in favor of anything that streamlines this process. I have my usual "go-to" items that I wish would be kept easily accessible. My only questions would be: Are all of these options above feasible? I'm not a coder and I have no idea what it takes to make changes to the existing backpack system, but it seems complicated and that you'll need to work closely with the Foundation to execute these changes. Will these changes be automatically written into the DCL backpack code once created? Or open source code that everyone can access individually? Sooo...can you break it down for us non-coders to understand it fully? I will try my best to understand it! Lol, :laughing: Thank you!
14 Comments