[garbear]

That said, in the interest of getting our hands on a fully working RetroPlayer build as soon as possible, it only needs to give us the basic functionality to begin with. All the other bells and whistles (auto-save, auto-load, multiple slots, thumbnails etc) can come later.

I've picked up the habit of API-first development. The key to this is the separation between abstraction and implementation. Creating interfaces is free, implementation takes work. Counter-intuitively, it is far less work to start with an interface full of bells and whistles than trying to hack them in later. Changing implementation is cheap. Changing interfaces sucks.

So to that end, I'd like to gather all the bells and whistles I can before writing code when it's cheap to do so. Name every feature you can, and I'll write an interface to back it. Once implementation begins, then we can start deciding which features are worth keeping and which we drop.