I don’t understand the years and years of ignoring this request. I guess it must be because people aren’t canceling subscriptions over it. It really does feel like you don’t care one whit about what your users actually want.
Infuse is great at its core feature of playing videos, but in most other ways QOL is lacking. Extras aren’t supported, if I change a file name I have to go back and manually change all playlists containing that title, there doesn’t seem to be a way to do any realtime filtering, I turned off syncing because all of my collections and playlists got messed up once and I didn’t want to go back and do all that work yet again. I could go on about having user profiles, etc, but what’s the point. It’s a slap in the face that Vision Pro support was prioritized over a million other features.
The Vision Pro development is likely to pull in new subscribers and nothing else, it wouldn’t make much sense otherwise. It is thus purely a business decision, and not an end-user decision.
I’m completely speculating here, but it seems likely that Infuse’s development process has an impact on its features.
My guess is that Firecore outsources most of the development work, which was indeed true at the beginning (as seen on MercDev’s portfolio).
The company appears to have a very small team - possibly just 1-2 people, according to their LinkedIn page - and I know only of James Abeler as the
Director of Business Development.
Given this, it’s probable that development is still outsourced. If so, each new feature would require an additional financial investment, which might explain why some features aren’t considered a priority.
Thanks for the feedback. People use Infuse in many different ways, and with regard to this feature it seems people will either have a lot of extras or they will have zero extras. Implementing a feature like this has a number of considerations as it would need to work not only with local extras people may have, but also extras provided by Emby, Jellyfin, and Plex servers.
I don’t have an exact ETA on when this feature may be added, but it could be something that makes an appearance in 2025.
Firecore started in 2007 and currently has a core group of full time technical staff. Over the years there certainly have been some contract based positions while others have been more traditional roles. Over half of the current group has been with Firecore since the early days of Infuse (some even as far back as aTV Flash if you’ve been around long enough to remember that) and having that level of familiarity with a project is quite invaluable.
Due to the user base size and inherent challenges of creating and maintaining a video player app work tends to be split up between features, improvements, and fixes. Often times work in the latter 2 categories can command more time than the former, but it is necessary to keep things working smoothly. There are certainly a few features we would have liked to have in place by this point, but maintaining the core stability and performance levels tends to take priority.
The development path shouldn’t have to be ‘all-up’. Surely starting with the core functions looking for local directories ( ./extras or ./featurettes ) before attempting to integrate with Jellyfin, Plex or Emby APIs.
Also, my coding speed in lines-per-day has quadrupled since I adopted AI assistance. Once it has learned your codebase, the AI can greatly enhance the quality and efficiency of new code.
The questions have been asked and answered but if you’d like to continue this discussion please feel free to start a new thread in the Lounge area.
That way we don’t keep sending notifications to all of the other users that are subscribed to, and are following this thread for updates strictly concerning this feature.