What I mean is that if it takes more than a glance at the screen to be able to read it or find the control you are looking for, then it is not simple.
As far as configurable, the app itself should be the core that controls it's look and feel while plugins add the actual functionality. This lets the end user decide what things they what loaded which has two benefits. First it doesn't force the user to wade through functionality they don't want/need and secondly it reduces the overall resources the app uses.
No offense to NBB as it is now and you can go look back at all the times i've poked Jirka for the same thing . It should "feel" like the platform it is running on. What this means is that it's UI elements (both look and placement) should reflect the UI of the underlying OS. To me, if a Mac user can't look at the front end and say "That looks like a Mac!", then there is no point to using a Mac over a Windows box for this.How would it look/function?
The App should offer support options for both. Ideally most of us would not like to use a TS, but it is the simplest control method.Would you control it with a touch screen or something else?
I think Music is the #1 for everyone. Beyond that, that is where making the functions plugins comes in handy. I personally will never load videos or images in my car, so why should I have them taking up UI space and resources (HDD space & memory)?What functions would it have (ie. music, movies, games...)?
I would guess the #2 feature most want is Navigation, but outside of what Jirka is doing that appears to be the holy grail on a Mac at this time.
A well developed and documented API will allow others to build the plugins for their special needs to that may not be practical for the core developers to spend time on.
Being able to skin the front end could also be a nice touch too as it gives users and developers that much more flexibility.