Landing Page for Library

[PenkethBoy 2068]

Is the Landing Screens for a library implemented in ATV?

 

Just tried changing in the web app which works - settings not carried across to ATV??

[CBers 7450]

It's in the TABBED VIEW settings per library.

 

Not in the app settings.

[PenkethBoy 2068]

This app needs some reconfig.

 

Why have settings in three places - madness

 

1. For the app as a whole

2. One on the page screen as a gear icon - but not for all library types or pages??

3. and then as an added bonus we have a settings menu item "hidden" away as the last tab - which actually does what i am after on the library type its supported on!!!!!!!!!!

 

Why are the landing screen options not in the same place as the web app (consistency would be nice) - i.e. in the app settings under "Home Screen Layout"

 

Why have settings for some specific pages but not others - e.g. Music>suggestions or Genres - cant change the icon sizes so i can see more music on one screen - can only see one row 

 

Why are settings in the web not carried across to the ATV app - it appears this is selective - or because the settings are all over the place - its hard to tell

 

Grrrr

[CBers 7450]

Perhaps if there was a User Guide for each app, it would be easier to see what options and settings were available.

[ebr 16172]

We put the settings inside the actual libraries because that puts them right there where you should be looking for them and contextually ties them to what they do.  We are working towards doing that kind of thing across the apps but haven't gotten completely there yet.

 

Also, we figured you might actually want different landing pages in different apps/platforms which is why they are not shared right now.

[PenkethBoy 2068]

Sorry but you missed the point

 

let me try again

 

Why have a settings tab separate from the main app settings page - for just the landing page option - makes it hard to find and frustrating

 

Oh and "we figured" is why you guys are getting a lot of blow back on changes lately - No documentation on apps so you have to "feel the force" to understand them, changes only you and Luke think are a good idea - with no option to choose a change or not ... i could go on

[CBers 7450]

I've never understood the need to have server-side settings duplicated in the clients.

[ebr 16172]

I've never understood the need to have server-side settings duplicated in the clients.

 

Because they affect the display on the client so it makes sense to be able to modify them there too.

[Luke 42077]

One example is the audio and subtitle settings. Anytime we add them to another app, many users act like it's a whole new feature. There are people who don't use the web app after initial setup so we need to design for that as well.

[CBers 7450]

Because they affect the display on the client so it makes sense to be able to modify them there too.

So you're saying that they don't change the setting on the server then?

[Luke 42077]

They do.

[CBers 7450]

They do.

So changing a server setting in one client, affects all clients.

[Luke 42077]

In this case yes.

[ebr 16172]

The landing pages are unique to this app in case you want them different and they can be selected for every library, not just certain ones.

[Jdiesel 1431]

I think many users don't know the server side settings exist and even fewer know they are applied globally, in some cases to all apps. A good example is the Roku client where there are no in apps settings for the library but the web app settings affect things like the homescreen layout.

Edited March 26, 2018 by Jdiesel

[Luke 42077]

Yea and that's why our ideal is to get those settings into all apps. We're just not there  yet.

[PenkethBoy 2068]

The landing pages are unique to this app in case you want them different and they can be selected for every library, not just certain ones.

The point is not that the settings exist - its that 1) they are on a separate page per library and 2) they are not in the same place as the web app when they clearly could be

[ebr 16172]

The point is not that the settings exist - its that 1) they are on a separate page per library and 2) they are not in the same place as the web app when they clearly could be

 

They appear at the point where they have an effect.  This makes it easier to understand what they affect.

 

For instance, you wouldn't expect to go change your filter settings for a particular screen in some central settings area, right?  You expect a filter button on the screen where it has an effect.  This is the same concept.  These settings only affect that specific library so they appear only when  you are in that library instead of having to go out to a central settings area and then find the library you are interested in and then set the setting there.

 

I understand it may not have been obvious they were there due to having to scroll the tabs (there is an indicator there trying to show there is more content to the right) but, now that you know they are there, doesn't it make more sense to access them that way instead of in a disconnected, central area?

[PenkethBoy 2068]

Sorry if this logic applied the the web app would have them in the libraries as well - it does not it has a central location

 

The thing you dont get is that some of us have more than two libraries and the way the web app does the landing page is 10 times easier than scrolling to the right for xx number of libraries in the ATV app

[Deathsquirrel 745]

Library-specific settings should absolutely be accessible in the library.  @@ebr is correct, that only makes sense.  If you want a global control for the same setting that could be fine too as long as the UI clearly says it's global for all libraries and that it will or will not, whichever is correct, override contrary settings in the individual libraries.

[PenkethBoy 2068]

How many libraries do you have - even 10 is a major PIA to adjust to your prefered landing page

 

Not saying to remove them just put them in the same place as the web app so you can see a simple list of library landing page as it is in the web app. If its such a difficult thing to do (it not) then when you click on the settings tab get it to take you to the App central page in ATV

 

does not make any sense to me as it currently is - its inconsistent coding of the UI's that we have across Embyas a whole - if it was consistent then we would be discussing something else - there is a long list.

[ebr 16172]

I think the difference here is a centralized administration mindset vs. an end user one.  An end user doesn't usually think about going somewhere else to hunt down settings but, if there are settings right in front of what they want to change, they will sometimes investigate those.