Minitunes design
Here are a few design decisions in random order. These are just quick notes, but may be useful to understand why things are the way they are.
Minitunes will not store data that cannot be reobtained from the internet at any moment.
Don’t put usage data such as “rating”, “play count” or “last played” in the database. Don’t use them at all.
No rating and no tagging. People want to listen to music not do data entry.
Do not assume the player is used by a single person. In a lot of cases this is not true.
No overly complex query tools. Again, we’re not doing data mining. We’re enjoying music.
No settings. People expect to quickly browse their music collection and just listen. Put “option switches” in the status bar.
Minitunes will work on your existing music collection. No imports, file duplication or reorganization. Total respect for the user data. Shame on media players that pretend to make a copy of your media, just to lock you in.
But how do you want to browse your music collection and information about the tracks if there is no tagging? You have to tag it with another music player?
TomBous, I didn’t mean tagging as in “metadata editing”, but tagging them with arbitrary labels as they do on last.fm, for example. Metadata editing is not a priority, because there are specialized tools, but I’m not against it.
Ahhhh ok excuse me for misunderstanding :)
Hope it is going to be a release soon.
Thx