Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wallet - Collectibles - Community Asset Segregation in Collectibles Tab #19896

Open
4 tasks
Tracked by #19500
FFFra opened this issue May 3, 2024 · 0 comments
Open
4 tasks
Tracked by #19500

Wallet - Collectibles - Community Asset Segregation in Collectibles Tab #19896

FFFra opened this issue May 3, 2024 · 0 comments
Labels
E:Mobile Wallet Collectibles Page MVP all issues for the collectibles page of the wallet feature feature requests

Comments

@FFFra
Copy link
Contributor

FFFra commented May 3, 2024

Figma Design

User Story

As a user, I want a distinct separation between "Community Assets" and other assets within the app, enabling easier identification and management of my collectibles.

Description

This feature involves the implementation of a new section within the Collectibles tab, specifically designated for displaying Community Collectibles. This will help users clearly distinguish between community-owned assets and personal assets.

Visual Reference

Community Collectibles Section Mockup

Acceptance Criteria

  • Adherence to the layout and design specifications as detailed in the provided Figma designs.
  • A new section for Community Collectibles must be distinct and separate from other sections.
  • Ensure compatibility with various file formats as outlined in the requirements.
  • Add dark theme support
@FFFra FFFra added feature feature requests E:Mobile Wallet Collectibles Page MVP all issues for the collectibles page of the wallet labels May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
E:Mobile Wallet Collectibles Page MVP all issues for the collectibles page of the wallet feature feature requests
Development

No branches or pull requests

1 participant