I think that we should have a place for beta app features.
With the Beta App coming along, I feel as if we should have a place to request features for it specificly.
Currently, there’s really nowhere for them to go, other than website features, and engine but that still doesn’t really fit, and there’s no direct way for them to get to the correct team.
I think that TL1 members should be able to reply to topics in here, also.
Rather than creating one channel for bug reports, the App beta should follow the footsteps of every other major beta that users have tested and have a entire category dedicated to it. Of course this could probably happen once the team is more than ready to accept user feedback.
It seems like we’re close to that happening, as there have been some pretty huge changes to it, and some leaks that are huge
Forgot to mention in the request, but also a place ofr bugs in the beta app would be nice.
You’re not really directing the request to the right team by posting in one category or the other, since the categories are way too broad. There’s not one team listening to engine features or one team listening to website features, there’s like 20+ different teams that could fall in each category and some own multiple domains.
Roblox has a bug triaging team (those people you see respond to bug reports all the time) that seem to direct it to the right team internally regardless of what forum category you posted it in.
The reason to have separate categories on the forum is more for user organization if anything. It’s easier to find existing requests if you can filter by website/engine/etc while searching on the forum.
It would be nice to have more granular organization in general. Website/engine/mobile/studio categories are way too broad. Maybe they should be using tags instead of categories to improve users being able to sort through existing feedback topics.
I dont think that somebody working on the Talent Hub is going to be looking in Mobile Features, though.
I think a possible solution, is keeping the subcategories we have, but say if you have a bug with logging in or 2step, you can add the tag #2-setp-verification, and put it into the #bug-reports:website-bugs. category.
The only thing is the Beta App doesn’t really fall into any of these.
I can see where more subcategories come in, but instead, for now tags exist and are useful for this.
If you want to suggest something for the Beta App though, you cant really pit it anywhere that’s perfect. Engine features isn’t exact, and it isn;t the website.
Sure, I could add the tag #beta-app, but it still wouldn’t be perfect, although I could and probably get away with it.
I do support the idea fo a lot more subcategories though
No, there shouldn’t be more subcategories. Discourse’s design doesn’t work well with many subcategories in a category. They should just get rid of subcategories and only have specific tags that you can only use in that category, one for each surface area of the product.
Maybe then the solution is to allow #uncategorized again? They stopped allowing those posts in all categories a while ago, this could be the solution.
As above, they just need to use tags better. I don’t know what #uncategorized would solve. There should still be a #bug-reports and #feature-requests category.
I didn’t mean gettign rid of the the categories in favor of #uncategorized, I meant #feature-requests:uncategorized, as that could make sense.
That would likely just become a dump for any feature requests that someone remotely is unsure about where they should go, plus creating an uncategorized category doesn’t solve the problem of ‘too many subcategories is bad’ as you are still adding another subcategory which is even more broad and unhelpful.
I think a better solution is just for engineers to clarify which category these requests belong to rather than creating a new category