Simeonov wrote:Ver. 8.2
Bugs:
1. On History screen, the buttons Upload and OK don't work.
2. Pencil-mode does not work on a already filled field. Is that behavior intentional?
Flaws:
1. When there is a started puzzle, which can be opened with the button Load Last, clicking (or misclicking) over a button starting a new puzzle should open a popup "Do you really want to start a new puzzle?" with buttons Cancel(closes the message) and OK(opens a new puzzle).
2. Can you open the ads in internal browser? Example: observe the app The Globe And Mail how it opens the Ads. However I am not sure how easy is to code such a library.
UI suggestions:
1. The difficulty and timer to be moved to the empty area between the puzzle and the banner.
2. After 1. an extra space will be free in the header, and thus, extra buttons can be put there. Example: an Undo button which might ease the Bug2.
3. Add to History and a diagram of the games with (+) Something like a local submit. The result will be something like a Gaussian with a line/mark where the average time is. I personally don't care of my one-time-best-time-which-I-have-submitted, because I got lucky with that particular puzzle, but I would care for my general performance. And taking the average time instead of the one-time-best time is much more accurate factor for a user's performance.
Bug 1 is fixed, Bug 2 is not a bug - it's a feature 
Flaw 1 is on our TO DO list, Flaw 2 - this is how it currently works on iPhone (for the most part), however, not all the ad providers support this yet (this is mostly true for Android, but also for some providers on iPhone).
Suggestion 1 - not all devices have room for what you are suggesting, we are looking for ways to accommodate all without having to maintain multiple versions of the app, but this is also on our TO DO list.
Suggestion 2 - just want to comment that you don't have to use "Undo" to clear a field - you could use the "Eraser" for that.
Suggestion 3 - for your general performance I'd recommend uploading and visiting the site to view the progress graph(s). To implement this in the app seems to be too much work for something that is a "nice-to-have" to only a handful of people. Unless, of course, we get requests for this from many more users. Then we'd consider including this...
Regarding your suggestion for the "big" / "small" number entry - it is also on our TO DO list. We are planning to include this as an option.
