Is there anything we can do to bump this or get it revisited/re-evaluated?
Because at some companies, “wishlist” is a euphemism for where features go to die… it just does feel particularly odd because it seems like this is such a simple thing to implement, and such a popular request.
I jump back a lot on MacOS and it is really annoying that if I just want to go back 5 second, I need to rewach another +10 seconds every time. It would be great if I can edit that if I press the arrow key, how much seconds it jumps.
There are a surprisingly large amount of enhancements desired by us “power users” that seem to us to be a simple thing to implement.
Just keep in mind this is an Apple-universe App and Firecore hones to Apple’s design ethos of “keep it simple”. Every simple suggestion implemented is at least one further option added to the settings page.
My impression is Firecore is loathe to add to both settings page bloat, and to possible future instability caused by an increasing diverse user environment (as new and old features might present bugs in certain optional user modes that aren’t present in others) — something which happens a lot in ultra-customizable Windows environments.
I further suspect the Firecore team is a rather small one and the majority of efforts are focused on making sure all possible content plays without issue.
I’ve personally advocated for an “expert” toggle in the settings page under which all our “fringe” UI options and enhancements can be hidden to avoid the resultant menu bloat if all our requests get implemented … but I’ve yet to hear an opinion from Firecore on such a solution.
Perhaps it is indeed just the difficulty of anticipating and keeping track of all the downstream effects varying the user interface and user experience can have on future coding?
Thanks, but there are already tons of settings so it doesn’t seem like they’re trying to minimize that at all. Heck, there’s an entire tab dedicated just to remapping hotkeys.
If this were an obscure, niche feature request then I could understand it not being worth it. But as I said before, this appears to be the #16 most viewed open suggestion… so it absolutely seems like it’s worth adding a setting for.
Maybe on MacOS, but definitely not on iOS or tvOS.
If so, then maybe we’ve got a chance they’ll get to it after they tackle the leading 15 others.
Hey, I’d to see this option (and many others) added, and a few (of what I see as) design bugs squashed. We can always hope!
Just sharing my insight into Firecore’s development philosophy, as I’ve seen it. Ymmv.