2023-10-24, 05:42 PM
You have to realize that Kodi has been around for more than 20 years, so I'm not sure I'd say this has been ignored, more that Kodi is a very mature open source project with a cult following and lots of contributors. Plus, plenty of inventive capitalists have leveraged Kodi into their own pre-configured pirate products labeled as alternative streaming devices and likely contributed at least a little bit to the code base in the process.
Endless scrolling sounds like a pretty hefty re-design of the UI and is highly client dependent. For example, on Roku, endless scrolling is already a thing -- keep pressing down and new "pages" are loaded dynamically.
Your other issue with display type is, again, client specific, and depends on CSS for some clients but a full re-write of how you interact with the client on others. Using Roku as an example again, there's not even an action available to change display type so it's a UX + display framework project.
These are both QoL improvements that would take significant resources to develop and implement, likely need to be developed for each client individually, decrease any existing UX parity, and not really address any outstanding needs/issues. Display options is where I'm inclined to agree that more choice would be good, but again it's QoL in my opinion.
Not attacking the ideas, as I think both are valid as feature requests, but I don't agree with the premise that anything is "ignored" when a product that has 15 years' additional development time is the only example of a better experience. Open source software moves at its own pace and the only way to speed it up is to add more contributors. Sometimes the only way to get what *you* want is to develop it yourself and share with the community.
Endless scrolling sounds like a pretty hefty re-design of the UI and is highly client dependent. For example, on Roku, endless scrolling is already a thing -- keep pressing down and new "pages" are loaded dynamically.
Your other issue with display type is, again, client specific, and depends on CSS for some clients but a full re-write of how you interact with the client on others. Using Roku as an example again, there's not even an action available to change display type so it's a UX + display framework project.
These are both QoL improvements that would take significant resources to develop and implement, likely need to be developed for each client individually, decrease any existing UX parity, and not really address any outstanding needs/issues. Display options is where I'm inclined to agree that more choice would be good, but again it's QoL in my opinion.
Not attacking the ideas, as I think both are valid as feature requests, but I don't agree with the premise that anything is "ignored" when a product that has 15 years' additional development time is the only example of a better experience. Open source software moves at its own pace and the only way to speed it up is to add more contributors. Sometimes the only way to get what *you* want is to develop it yourself and share with the community.
Jellyfin 10.10.0 LSIO Docker | Ubuntu 24.04 LTS | i7-13700K | Arc A380 6 GB | 64 GB RAM | 79 TB Storage