Yeah that'd be good for easy recognition of different fields
Seriously though, the UI is main thing people see and can critisize easily
The 'behind the UI' stuff is pretty darned solid - used defined database fields, easy searching and amazing smartlist support
There's always a 'but' though
There are a few areas that crop up so often that maybe they should be looked at a bit more
They may be minor display quirks (what do we want "Stars!, when do we want them "Now!") or gramatical quirks like useing 'Delete' for removing a track from playing now
In the priority list of things to do I shouldn't imagine they are high on the list, but as a user they affect me every time I use MC
I don't want to select a number from a combobox and clicking on 'delete' makes me cringe every time
The 'delete' irritation is probably what confuses me the most - it's just changing a word ('Remove from playlist' would be better), but apparently not worth spending the time on
These little things are probably a lot more of an issue for the users than the developers - I know that I've written some programs that work like I'd expect and gotten really negative feedback from the users
Most of the time, the fixes were easy but I'm so busy with other complicated parts that I had neglected them
After changing my priorities to fixing the simple things first, I had much better user satisfaction
It is a choice that each team must make by themselves though and the temptation to work on the bits you
want to do, as opposed to doing something uninteresting has a really strong attraction