I think this points out one of our goals with Emby clients and, probably, a source of some people's discomfort with some of the interfaces in Kodi (not bashing, just making an observation).
In our interfaces, we are trying very hard to be intuitive and simple and not operate like a "computer program". I think many interfaces designed by programmers end up looking too much like computer programs - which makes perfect sense to the developer - but not necessarily to an end user.
This operation is a case-in-point. Where Kodi's solution is: [nested down already a few levels of menus]->Settings->Add User to Session The Emby solution is [click user icon]->Also here.
While the functions are identical, the former looks like a computer program and the latter is more user-oriented (IMO). What is a session...? Why do I want to add a user to one?
Again, not bashing anything here and Kodi is a great solution for a large population. I just wanted to point this out so as we are all designing our interfaces for Emby, we can try to concentrate on simplicity and the user perspective . I know I have been guilty of this myself many times.
"Here endeth the lesson" (bonus points for the film reference...)
I understand the need for simplicity. I don't think Kodi feels like a computer program. But again, I've been using it for many years.
In Kodi, it's just a matter of creating shortcuts to the content or function you want. You can remove menus and only keep what you find appropriate. No other interface will give you this kind of flexibility and will most likely always force you to use a cookie cutter layout.
The appeal to Kodi is the fact that I can tailor it the way I want it.
Now, ebr what you said regarding Kodi solution is pretty inaccurate, but I can understand since you don't use it. The fact of the matter is, we have an add-on and we have no control over the interface. All we can do is provide already built library sections and functions. Then, it's up to the user to create home menu shortcuts to what they actually want to use. So in day to day usage, if you are accessing nested menus, you are doing it wrong. It's that simple.
Setting up your interface is not complicated, but it does require you to sit down for 15-20min to do so. Kodi has a limited out of the box setup to begin with, but it leaves the user in control for the most part. The developers provide functionality and leave it up to the user to decide what's simple for them.
I personally hate cookie cutter layouts because there will always be something I'm unhappy with. Simplest example: the order of tabs in the webclient. Hate that it can't be changed. I don't have this issue with Kodi and I think it fills the need for users, like me, that like to be in control.
Kodi works a lot off feature requests and the many settings available are a direct result of it. I don't think it's a bad thing, because that's what advanced users want. More control and less leaving it up to the developers to decide what they think is right for their users.
In the end, kodi fills the need for the millions of people who like to control how their items are presented and played and there will always be a need for that kind of flexibility. Cookie cutter layout won't always cut it, there will always be feature requests from users asking to make their setup, their own and that's when Kodi steps in.
[currently working on a quick tutorial to easily get setup in Kodi and make the learning curve easier, for emby users coming to Kodi with our add-on.]
Sent from my iPhone using Tapatalk
Edited by Angelblue05, 29 September 2015 - 03:15 PM.