I hope you didn't misinterpret my earlier statements: I'm in no way defending the solution Matthaeus offered, I'm merely stating it's an interesting "concept" (not a finished interface), considering that my experiences with these car interfaces (which are little and I'm aware of that ;) ) are that there is no real intelligent evolution to any kind of digital touch interface.
And I agree wholeheartedly with the sentiment that most 'designers' you see on here have said problem with "meaningless visual design", but I'm not too concerned about that ;)
Concerning the car interfaces only a quick remark: I still think that there should be a different kind of UI for driving and for parking. The Tesla interface can be a great thing when you're in your car and not moving (having a browser and whatnot), but when you're the one driving, there should only be a limited amount of options you can actually perform. I think this is a very important thing: reduction. Knowing what to remove, knowing what to leave. Once we establish this we can move on how to implement an interface that's not only usable, but also secure.
I hope I made myself clear and you see my point: I'm just trying to figure out how one can approach problems like this, or how others approach them. I am only a layman and don't know another thing about cars except how to drive them ;)
I hope you didn't misinterpret my earlier statements: I'm in no way defending the solution Matthaeus offered, I'm merely stating it's an interesting "concept" (not a finished interface), considering that my experiences with these car interfaces (which are little and I'm aware of that ;) ) are that there is no real intelligent evolution to any kind of digital touch interface.
And I agree wholeheartedly with the sentiment that most 'designers' you see on here have said problem with "meaningless visual design", but I'm not too concerned about that ;)
Concerning the car interfaces only a quick remark: I still think that there should be a different kind of UI for driving and for parking. The Tesla interface can be a great thing when you're in your car and not moving (having a browser and whatnot), but when you're the one driving, there should only be a limited amount of options you can actually perform. I think this is a very important thing: reduction. Knowing what to remove, knowing what to leave. Once we establish this we can move on how to implement an interface that's not only usable, but also secure.
I hope I made myself clear and you see my point: I'm just trying to figure out how one can approach problems like this, or how others approach them. I am only a layman and don't know another thing about cars except how to drive them ;)
Cheers