Skip to content

improvement on pokedex #44

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

Closed
aerinpatel opened this issue Apr 28, 2025 · 4 comments
Closed

improvement on pokedex #44

aerinpatel opened this issue Apr 28, 2025 · 4 comments

Comments

@aerinpatel
Copy link

Title: Enhance Pokedex UX: Allow Users to Select Pokémon Type and Quantity

Description:

Currently, the Pokedex displays all Pokémon cards upon loading, which can be overwhelming for users.

Proposed Enhancement:

  • Introduce options for users to:
    • Select specific Pokémon types (e.g., Fire, Water, Grass).
    • Specify the number of Pokémon to display.

Benefits:

  • Improves user experience by providing a more manageable and personalized view.
  • Reduces initial load time by fetching only the selected subset of Pokémon.
  • Enhances performance, especially on devices with limited resources.

Implementation Suggestions:

  • Add dropdown menus or checkboxes for type selection.
  • Include an input field or slider to set the desired number of Pokémon.
  • Modify the data fetching logic to retrieve and display only the selected Pokémon.
@aerinpatel
Copy link
Author

@solygambas please assign me this issue

@solygambas
Copy link
Owner

Thanks for the thoughtful suggestion, @aerinpatel — these UX improvements would definitely enhance usability and performance for many users.

That said, since this feature introduces user-specific customization and may not align with the core simplicity of the main project’s scope, we recommend creating a personal fork where you can fully tailor the experience to your needs.

Looking forward to seeing what you build!

@aerinpatel
Copy link
Author

so should i start working on it?

@solygambas
Copy link
Owner

Yes, if you wish to pursue this feature, you should absolutely start working on it in your own fork.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants