The UI/UX is Severely Lacking

I’m probably crossing multiple threads here and apologise (kind of) for doing so.

But…Generally the UI/UX is severely lacking.
A lack of an Alphabetical jump list is crazy…
…but it doesn’t even come close to…
Playing a show from continue watching and not being able to navigate to the root of that show. Every season should be accessible and navigable from there. (There are thousands of shows that don’t require a strict play order)

Cast lists for an episode of a show. Infuse has the same ten (and only ten) faces despite them not being in the last three or four seasons. No guest stars? Plex & Emby show an up to date cast list of 20+ (Again a navigational failing in Infuse).

But…neither of those come even close to the nonsense of the top row of the Home Screen.
What on earth is that all about? Perhaps I’m the only person who uses Infuse who has more than a single part watched movie or episode? If I’m not, then hopefully someone else agrees that scrolling through six or ten (possibly the maximum) space wasting horizontal thumbs just to get to recently added (and to then encounter yet more horizontal thumbs.)
Heaven help you if you have more than one currently running show.

Then finally we have trailers. More importantly we now have an even more requested option to turn them off.

I’m sorry be be that guy, and again, though a lot of what I bring up here is not related to this topic, it’s an ever growing theme in multiples threads of a UI/UX that verges between flawed and unusable.

@james Can we please stop implementing new features for a while and actually implement some of the requests regarding navigation and usability?

Infuse seems to now be going down the Plex route of implementing nonsense(however much it was requested.) It takes less than 10 seconds on any device to find a trailer for those who really want them. It takes several weeks to disable/hide the same feature (and revert those UI changes)that took up so much time to implement.

If this post has to be split/moved/merged (it really shouldn’t be as it’s as valid here as it would be in all the other UI/UX fail posts) then so be it.

Bottom line is it’s really nice knowing that once my media is playing it’s gonna be flawless.
It’s just a pity that actually finding something I want to watch is extremely painful…cos yeah I actually forgot all about multiple filters.
It gets to a point that everything Plex fails at is usurped in Infuse by what Plex can do.


Maybe we can just turn off the forum for a week so Firecore can stop being distracted by the latest obscure codec bug and get to uninterrupted work fixing the UI.

Think of it as “infrastructure week”.


Definitely agree, this request has been on the list now for MORE than one year. It’s past time to put aside all the new cool stuff, and concentrate strictly on fixing the UI.


So, I’ve been thinking about one way Firecore might have organized Infuse’s code, if conceived in a modular fashion.

Using somewhere between 2 and 4 key modules (depending on the degree of entanglement between them) …

My thought is you’d first begin with a module that includes all the code designed to access content on the large and growing variety of Infuse-supported local and remote servers and cloud services. This module would deal exclusively with reaching out from the Apple TV and establishing read-privileges to users’ content, wherever it lives, and the management of users’ shared folders.


Next you’d have a module that exclusively builds and manages Infuse’s database cache. This would apply to all items in users’ shared folders that are included in Infuse’s library. This module would scrape the filenames of users’ video files to determine content type (TV / Movie) and appropriate search terms with which to query TMDB for identification of the files and the downloading of all supported metadata for each title from TMDB’s own massive database.

Essentially, this database should be a matrix of datapoints for each file; including links to the users’ video files, file accessed, created, and modified dates, tagged data fields for all the textual metadata downloaded from TMDB, links to all of the relevant image files on TMDB, and links to all the users’ local image files (stored alongside the video content).

Ideally among the tagged data fields for video files listed above should be links to all cast and crew information derived from TMDB (and links to their headshot images), that would be available to be pulled on demand when a user request the complete list through the UI.

It feels as if Infuse does build its own cast & crew database independent of the users’ video files database — which Infuse populates as it processes new video files — with the entries for the video files each containing tagged fields linking to cast and crew entries in this database — which appears to either be made up of links to the persons’ headshot photos plus Infuse generated links to other collection items in which that person appears …

… Or else it’s all simply a dataset created anew each time, on demand, by querying the entire video metadata database (which seems less efficient).

Because Infuse is able to return search entries for collection titles in which an actor/crew member is credited but not displayed as being a cast/crew member of when viewing that title’s cast/crew bar; it doesn’t seem Infuse’s internal cast/crew database is artificially limited to only the number of entries per title that the UI is currently capable of displaying.

The above would seem to indicate that the UI has room to grow to improve display of cast and crew without necessarily requiring changes to Infuse’s underlying database structure.


When Infuse added support for override of TMDB-derived cast and crew data via local .nfo, it became obvious to me that Infuse did this by creating an entirely separate (.nfo-derived) cast and crew database to the default (TMDB-derived) one.

These two databases fail to “play nicely” together in many instances — such as when doing a manual cast member search from the Home Screen. Even when local .nfo is sourced from the same provider as TMDB, and links to the same actor/crew entries at TMDB, Infuse does not combine the duplicated entries. You’ll therefore have duplicated entries in all search results.

Adding insult to injury, the two entries won’t be linked to identical lists of the person’s body of work among a users’ entire collection:

While the TMDB-derived Cast and Crew database eventually builds to completion in the background; that is not the case for the .nfo-derived version. The .nfo-derived Cast and Crew database is only added to when a user actually browses to the folders containing videos for which .nfo data is provided. To force Infuse to fully complete the .nfo-derived database, a user must tediously navigate manually to every collection folder.

This could definitely stand to be investigated and improved.

An even easier solution might match the one that was recently implemented for the Trailers button — give a user the option to Opt Out of managing their own Cast & Crew via .nfo. I formally used .nfo to customize the displayed titles of my movie and TV series (as a way to better control sequential sorting among franchise titles, for example, or chronological sorting for a musical artists’ or comedians’ body of work, for two more). I’m not longer able to do that because of the breaking of Cast and Crew representation.


Third, you’d also need a module dedicated simply playing back all of a users’ files, regardless of their specific encoding and quality standards. This module would simply begin streaming video files from links already established by the above two modules (as directed by the user via the next-to-be-discussed UI module); identifying the file-type and encoding via file headers or deeper examination of the file itself, choosing the correct decoder and decoder parameters with which to process the streamed file, and pushing the decoded audio/video file to the playback UI.

This module, and the one that reaches out from the AppleTV to users’ intranets or the internet to gain access to the files in the first place, seem to be the two elements most effected by updates to Apple’s operating systems, remote networking protocols, and technological advances in video and audio encoding techniques.

These modules also seems most susceptible to being broken by users who utilize non-standard or poorly encoded content or improperly utilized cloud storage options — yet regardless of fault, Firecore still seems to invest a large percentage of their efforts into frequently updating their grabbers and decoders to support even poorly sourced and poorly encoded content.


Finally, you’ve got to have an attractive, intuitive, feature-rich UI module: the code which governs the user-facing interactive elements that visually represents various matrices of playback links to all of a users’ indexed content, as organized per users’ various preferences, and accompanied by attractively presented metadata that assist a user in browsing and locating specific files and viewing information about those files to help the user decide what they want to watch at any given time.

For Library included content, those various matrices should be customizable and sortable based on the widest possible selection of specific metadata fields as is collected in Infuse’s internal metadata cache — data ingested during Infuse’s original content import process and periodic Library updates.

Assuming the cached metadata database is structurally sound, a lot of unrealized potential still exist within the Infuse UI; with some new or enhanced features governed by options modified or added to an updated configuration settings dialog.

Some such features would require the coding or recoding of various onscreen elements or “pages” of elements (including the Infuse Homescreen; the Movie and TV specific versions of the poster wall and list views; the movie and episode specific versions of the details page views, and perhaps the Library Menu page itself.

Many features would merely require the modification or addition to options in the settings menu; or modification or addition to various long-press options already widely present in the UI.

Currently missing features such as the enabling of per-folder (or per-filtered view) sorting options should presumably only require the code necessary to save and read back specific user-defined sort options to folders and views that already exist in the UI. If Infuse creates those views dynamically, brand-new each time, it will of course need to start recording their various view states and preserving these in Infuse’s allocated persistent memory register.


I’ve got to say, I’d really love to get access to the source code governing Infuse’s metadata database(s) and UI, and poke around, and see how I might contribute.

Couldn’t care less to see how the content is accessed, streamed, decoded, or played back — I feel Firecore has got that well under control.

Very much looking forward to this list of long-anticipated upcoming UI enhancements — especially one surprisingly added item very dear to me; seemingly present to address a long-ranted-about pet-peeve of mine.

This is a fantastic to-do list. I very much can’t wait to see how improved the Infuse experience will be afterwards.

7.5.5 (May)

7.5.x (in progress)

7.5.x (pending)


:point_up_2:t3: TL:DR


1 Like

Here is another great example of why there should a concentrated effort put forth to clean up the UI and the accompanying documentation. How to set it all up for a newbie


I agree that the UI clearly needs work.
I appreciate things can take 12 months+ to implement sometimes, but basic UI features such as alphabet listing next to content is a very basic requirement which is currently lacking on Infuse.
It’s been requested for at least the last 6 years.

Infuse is a great app for what it can do - it plays 99% of files without issue.
But the looks/UI of the app have been neglected.

As above, with the comments about the home screen in the app it’s not user friendly.
Adding 2 folders for example - movies and TV shows, ends up listing multiple folders for the same things such as library, movies, TV shows - whereas this needs to streamlined and made user friendly.

You can have the best working app in the world, but if it looks rubbish and isn’t user friendly - then either people won’t join it, or will stop using it.

Spending a good chunk of time to seriously work on and improve the User Interface will make Infuse THE best media app, and will draw in a lot of new users, therefore increasing revenue.

You don’t see the same influx of increased user revenue for adding features such as movie trailers.

“If you build it, they will come”