Upgrade the Subcategories for Feature Request

When it comes to having access to Roblox features or products, we take an interest in understanding their purpose and benefits for Roblox creators. We also like to provide our feedback on how they can be improved for a better user experience, related to the game engine as well as the Roblox application as a whole. On the Roblox Developer Forum, we have a category called #feature-requests, which allows users to create topics to provide feedback on Roblox features. This helps Roblox receive feedback and improve its features.

The #feature-requests provides a few subcategories such as:

However, as Roblox expands its technology and the new ways to entertain and provide accessibility for its community, it comes to a certain point where more and more feedback arrives. For instance: Roblox on Playstation. As of 2024, we don’t have any categories for this particular case… The subcategories are outdated with the newest products Roblox has shared with us since the latest Roblox Developer Conference (RDC).

As a Roblox developer, it is currently too hard to provide feedback for new products when there aren’t enough subcategories on #feature-requests. We always need to turn to topics made at #updates:announcements and we don’t receive proper answers from the team behind the feedback.

The viable solution would be updating the structure of specific subcategories. For example:

  • #feature-requests:platform-features → Within this subcategory, users would create a topic for a feature request regarding the X device they are considering, for instance, on Meta Quest, Amazon Fire Tablet, etc.
  • #feature-requests:creator-hub-features → Within this subcategory, users would create topics regarding the products from the main project of the Creator Services Team called Creator Hub, such as Creator Store, Talent Hub, Creator Documentation, etc.
  • #feature-requests:other-features → Within this subcategory, the intention is that users would create topics about products that they believe are underrated and do not fit into any of the previous subcategories. By doing so, it will prevent confusion in the other subcategories and allow the product team to better address these topics. Its scope is similar to #bug-reports:other-bugs.

If Roblox is able to address this issue, it would improve our experience using the forum because it would enable us to share deeper insights while maintaining organization and visual clarity. This means we can better discuss both major and minor Roblox products.

Thank you!

10 Likes

What is the problem here exactly? Is your thought that the way the categories are structured currently is preventing certain issues from being addressed?

I don’t believe that is correct based on my experience. Internally the feature request category is not being used at all for routing currently. This post reads more like a proposed solution.

In general, we’re moving away from “vertical” categories like “xbox”, “playstation”, etc. and more on “horizontal” categories like “audio”, “graphics”, etc. The latter aligns better to how Roblox teams are set up internally.

For the time being just pick whatever is closest to your feature request. If it’s Creator Hub related you can put it in #feature-requests:website-features and if it’s anything engine-related that doesn’t have a specific category, just put it in #feature-requests:engine-features.

It really doesn’t matter that much currently because it all comes in as a single feed internally anyway.

Some time in the future we’ll redo the layout of feature requests (see also the post you quoted; btw not sure how the quote is relevant to your request?) for more information.

2 Likes

Couldn’t tags work instead? Also discourse (the forum service) does not allow sub-subcategories.

1 Like

Hey @Hooksmith! How are you doing today?

If you didn’t understand properly, let me explain again better:

My whole point is that we should have standardized sub-categories for the #feature-requests when it comes to providing feedback from a product and there isn’t a specific category for them. Examples are the cross platforms. If I want to provide feedback regarding Roblox on Meta Quest, I won’t be able to do so because there are no sub-categories for it…

I understand that the insights come together into one pinned place, but I believe it would be better if we could have a standardization for the subcategories of #feature-requests. That way, not only it will be visually organized, but the user can also search rightly for the topic they are looking for.

2 Likes

are you sure about that?

image

2 Likes

Hey @Hooksmith!

It has been a while since our last discussion about the feature requests. It seems that some users are interested in having better organization for the subcategories of #feature-requests. There is a suggestion to create a subcategory specifically for consoles, as mentioned in recent posts within #forum-help:forum-features. The image attached to my previous message illustrates the proposed restructuring. I apologize if my explanations were unclear, but I believe the image will help clarify my point.

As an active user in the Developer Forum, I’ve noticed that it’s not possible to create feature requests for certain situations. For example, there is no subcategory for Meta Quest/PlayStation, only #feature-requests:xbox-features. This creates barriers for creators who want to share insights for Roblox products. While everything is in one feed, having proper organization is essential for sharing and internal transfer of insights.

What are your thoughts on the proposed restructuring in the image? Are there possibilities to improve internal organization for the forum?

1 Like