Thank you for your input. Most of those aren't done that way for technical reasons. They would either slow the game down or complicate it or both. As for depth, some time ago I did a prototype of this game with 3D graphics (screenshot attached). I think it's an actual screenshot from N900, it ran at about 40 fps. Gameplay would still be 2D, but the view would tilt a bit when you moved, so you could see the depth. But it was done using Qt (no Android compatibility at the time) and a bit impractical overall, so I scrached it and much later started this iteration. It was a bit painful to achieve 60 fps in this version, but I think it was worth it (if only I could enable damn v-sync...). Importing your own blocks would be to complicated, both for me and for the end-user, and I'm already struggling with texture memory on Androids. There's not much room left for me adding blocks either, at least the way things are set up now. Level editing is another major factor here. I decided I wanted that early on, so all gameplay elements needed to be simple enough that anyone could use them while making their own levels. Editor souldn't be significantly harder to use than the game itself. Also - it's easy to abuse. If only I made the levels, I'd put more stuff in, add more shiny animations and whatnot. But with everyone editing, I had to make the cost of each tile more-or-less constant. And those "advanced tiles" are limited in quantity (stars and portals). I wanted to make something for mass-consumption, an that means it has to be idiot-proof. I don't want to be explaining why is the game running slow on one level, and not on another, especially if I'm going to ask some money for my games at some point in the future. As for the instructions, I thought the best way would be a narrated tutorial video, but it just hasn't happened yet