Maybe that’ll be enough votes to get this to happen?
Maybe that’ll be enough votes to get this to happen?
Liking the first post is the way to vote for a feature.
+1 I need this to have a special library for my kids!!
Welcome to the forum!
Don’t forget that you need to click the like button on the first post in this thread to show your support for this suggestion!
As presented in Support multiple users in your tvOS app - WWDC20 - Videos - Apple Developer the Infuse app could provide multiple-user support on tvOS 14 and above without any code changes by enabling the “Run as Current User” entitlement in Xcode. Each user setup on an Apple TV device would use his/her own credentials and iCloud sync data. Perfect if you are already using Infuse on macOS or iOS because view data etc. is in sync.
The newer SDK features added in tvOS 16 which were presented at Support multiple users in tvOS apps - WWDC22 - Videos - Apple Developer are not needed. So maybe you could provide a TestFlight version with the “Run as Current User” entitlement enabled and collect feedback from Beta testers. I would really like to test it.
FYI if you use something like jellyfin/Plex for a backend for metadata you can make the user there and just limit those files.
I find this a nice workaround since I like having a separate app to pull metadata anyways.
any news regarding this topic?
Multi User would be awesome for the Apple TV.
Right now 7.5 is consuming all the time introducing support for two of the top three requests that are 4+ years old. Im guessing that there will be several versions (7.5.X) to work on any issues that come up. Perhaps after that we will see support for another major feature. You can follow the thread tag or upcoming features. Besides that, I don’t expect any update from infuse team until they are actively working in the feature. I expect this to be the same for any other thread right now. Upcoming Features (updated 2/20/23)
From all the suggestions that haven’t been integrated yet, this is the second most liked one. But still, priority is being given to less liked suggestions so what is the point of all the users in this forum to like a suggestion/request if it’s not taken into account for planning the next additions to the app?
I understand developing an app like this it is not easy but examples have been given in this thread where to find the code to implement this feature, examples of other apps using this feature, etc.
The community in this forum is clearly giving an indication this is the priority for them. Maybe this is a good time to listen to their feedback. They are the ones who you develop the app to.
Sorry for the rant and thank you.
Hence both trailers and multiple versions of movies, both which have been voted for more than user profiles. Don’t get me wrong I will NEVER use trailers and whilst there is no user profiles I can never move away from Plex completely so I want user profiles as much as you.
But your statement doesn’t stack up.
Is there a particular reason why this isn’t really looked at for so long? It feels like a pretty obvious feature that is missing, that many users would benefit from. It‘s the main reason why i can’t fully switch to Infuse
Please get to this before 2024.
Because this feature requires a redesign of of the UI and the library database. It’s a structual change.
Which in itself is another heavily requested (and very much needed) feature.
As I have already tried to explain above: Infuse multiuser support on Apple TV could probably be achieved without code changes.
Just by developers enabling the “Run as Current User” entitlement in Xcode, the Apple TV operating system would provide separated application data spaces to Infuse for the different users based on their Apple ID. So the user-data related behavior of the Infuse application on Apple TV would be more equal to that of the multi-user macOS than that of single-user iOS - no changes to the app UI needed.
For further reference related to the user perspective, please see Share Apple TV with multiple users in the Apple TV User Guide or just try out the behavior of the Apple Music app which switches content based on the currently active user.
There’s also this: Supporting Multiple Users in Your tvOS App which might be very helpful for the devs has it contains all the information they need to incorporate this feature in their app.
This feature is available since tvOS 14 and we are already on tvOS 16. All the information needed to implement this has been available since 2020.
How do you fix the feature parity issue between platforms?
There are features only available on tvOS. This could be another one of those.
To be honest I don’t see the point of having this feature on macOS or iOS since those are typically devices not shared between users.
The media collection of our family is on a Jellyfin server. Everyone has their own account there. We use Infuse as a player frontend on multiple Apple devices, each with their own Apple ID.
The iDevices with iOS or iPadOS are not shared between us. We share two Macs with separate user accounts, each connected to the same personal Apple ID as on the iDevices and so with access to their own Infuse and Jellyfin profiles.
The Apple TV is shared by the whole family, but once again setup with our individual personal Apple IDs. In Gaming Center and Apple Music, the different user profiles are taken into account and everyone can access their personal content. However, Infuse always uses the default user’s Apple ID instead of that of the currently selected user. So Keep it all in sync, as described on the Infuse homepage, works for just one of the Apple TV users:
Use iCloud to keep metadata, library settings, and playback progress in sync between all your devices. Start a video on iPhone, and easily jump back in where you left off on Apple TV.
From a user perspective, no tvOS specific Infuse feature is needed, but rather a fix for an incomplete user experience. May we call it a bug?
But switching the Infuse app to the multi-user support available since tvOS 14 primarily means setting a configuration setting when building the app. And this would fix the UX issue entirely without changing the interface.