Touch optimized and customizable Webfronmtend

[splitti]

Is your feature request related to a problem? Please describe. I really like IRIS! I try to create a Box for my small kids. One is not able to read, so it would be perfect, if he gets an album view and play view only.

Describe the solution you'd like It would be nice to disable some entrys on the bar (no search, no this and that...)

I just want a few points in the bar, Settings, my Albums, my Artists and my Playlists from Spotify. Maybe you have an idea, how to port IRIS for that, like a second IRIS sandbox...

[jaedb]

The first port of call would be to visualise how you anticipate this working, and to better understand the wider use case. Some key considerations I would also suggest exploring:

1. Who is it for (beyond your specific use case)
2. How would you describe it's purpose to a new user
3. What features must it have (as opposed to 'nice to haves')

The reality is that every feature request requires a balance between effort required and benefit it provides. Unfortunately many requests just can't be justified. It is important that my personal time spent developing Iris is on functionality that delivers as much value to as many users as possible.

Basically: propose how this would work and what it would feel like, and we can go from there :-)

[Chaphasilor]

Could be as "simple" as allowing users to load their own CSS.
They could take the current CSS and modify it to their needs, simply hiding some elements or making certain parts of the UI larger.

That should require too much work on your part, just a way to specify a path to the custom CSS file(s), copying/loading that file on start and a bit of documentation.
This would allow users to implement their own fixes or workarounds for issues until they're resolved (padding issues, access to settings and hiding or showing buttons are all open issues here and easy to "fix" this way).