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
Making Mobile & Frontend Tags and Platforms Consistent #513
Comments
Hi, here are the age restriction options for mobile for now:
The platform options:
The tags, predecessors and successors are not restricted to options, user can define anything. |
For the frontend, platforms:
Age restrictions:
Tags:
For age restrictions; I searched for the pegi options on the Internet. I think using PEGI would be suitable because the games are also coming with this information, it is easy to assign this way. For tags; I think we should have some predefined tags but we should expand the current ones. Users may be able create custom tags but handling these may be overwhelming for the search functionality; so I prefer having predefined options to users for tag selection. For platforms, we can merge our platform options, that would be better. For successors & predescessors; we also didnt retrict the user. What do you think? |
Platforms:
Ages:
For tags, I found these options on Internet. But I think it is too much. We should have ~15 options for better experience in my opinion.
|
I think these are okay, even if they are many they are all related to games. We can get feedback from customers as well. Thank you for your time ❤️ |
Both mobile and frontend team arranged their contents so this issue can be closed after review @haticerk . |
Thank you for your efforts, girls! These tags and platforms are sufficient right now. |
Issue Description
In our create game forums, there is an inconsistency between the tag and platform choosing. We will resolve this issue and make the frontend and mobile application compatible.
Tasks
Parts of the task:
Extra Comments
No response
Final Step
No response
Deadline of the Issue
27.11.2023 21.59
Reviewer
@haticerk
Deadline for the Review
27.11.2023 23.59
The text was updated successfully, but these errors were encountered: