Sure, I would expect that the menu button (whether a hard menu button or a soft one, either way, I believe that's the 'proper' / formal name for the 3 horizontal line button) is what should be used for pulling up settings (equivalent to clicking the sheep to pull up login / register, scores, and prizes), and the back button should always back out from wherever you currently are (which it appears to do when navigating settings, what's missing is integration in the actual game to use it to back out from when starting a game as well as using it to exit the actual app). Hope this helps in regards to clarifying what I was thinking.
In regards to the full-version unlock, there's two ways of doing it that I see:
1. Separate key-unlock app - see applications such as
BubbleUPnP (and its
unlocker) to see what I mean by this. It's just a separate app altogether and avoids having to put additional permissions in your main app to be able to make purchases though I suppose you could potentially run into people that stupidly buy the key without making sure the main app works on their device first, etc.
The likelihood of them downrating your main app as a result probably isn't that high though, and AFAICT this seems to be a relatively popular way of doing demo / full versions of quite a few Android apps.
2. In-app purchase - just a single app that comes as a demo and you buy the unlock key from within it (this is the method you're currently looking at). It almost definitely makes accidental purchases, etc., a non-issue, but on the negative side (besides it possibly being a PITA to implement) is the additional permissions that will be needed to actually make this possible. For better or worse (probably for the better to be honest
), there are quite a lot of Android users out there that are paranoid of apps that have what they interpret as excessive permissions (i.e., "OMG, why does a simple game need to be able to read my contact list?!?? I refuse to install until you remove this!!!"
)
Since I'm not an Android dev myself, I can't really say which is the better method to go with in terms difficulty implementing it (though I'd imagine #1 is easier to implement), end-user experience, what will ultimately mean more $$$ for you when you factor in which will sell more copies, etc., but there you go.
