The impact is moreso engineering efficiency. Every option like that which we add is an additional option that Roblox engineers have to work around and test against when adding new features. This builds up exponentially too, not linearly: If you have three options, that’s not just three things to test, that’s eight combinations of options to test against. This can seriously slow down our ability to add new features.
Backwards compatibility is really valuable to Roblox, but we have to draw the line somewhere. Things like this which are likely to only affect a very small number of devs (or none if things go well) in a way which is relatively easy to work around aren’t worth supporting options for.
Having a million options isn’t ideal for developers using the platform either: That’s more (often irrelevant) info to sift through when they’re trying to find the what they need on the DevHub.
This right here sums it up perfectly. I just wish that newer, more modern devices were opt-in or something of that nature so that we, as developers, didn’t have to abide by all the different limits for lower end users. That’s one of the biggest gripes I have about this platform. The fact that I have to treat almost every player I have as a low end device user and it seriously hurts my ability to create anything past, quite frankly, “childish low poly”.
It seems incredibly hard for no real reason to create experiences for anyone older than… lets say 14 years of age. I wish there was a notice or more appeal to older audiences where the rules were a bit more lenient and a bit less constrained.
Wondering if anything address these gripes both long or short term.