Thanks for the detailed comments. Some comments might be caused by our lack of detailed helps.
Basically the complaints come from three parts:
1. Quick input of stones.
2. Variations.
3. Image recognition.
For customizing the moves per page, check settings/book mode section.
For indication of variations, you can also toggle auto show variation in settings.
For some quick help and discussion about image recognition, besides the one in our web site. Please see the introduction for image recognition, etc. in:
http://www.go4go.net/go/GoEye.
Some suggestions are good and we will adopt in future release. And many of the input issues are small cases to fix. e.g., sticking to black/white stone input mode. The original intention of the author is to insert a stone. But it seems that the user assumes that it is for consecutive inputs. This is good suggestion.
Our app seems to be the only one full fledge SGF viewer/editor for continuous pinch zoom (not counting sente which doesn't support SGF). Pinch is the most intuitive way. This is a technically hard part for other rivals to compete. Double pinch to zoom is an approximation solution introduced by some other apps. This is easily adopted by using similar way to Safari (double pinch to toggle zoom to max/min). So we accept this suggestion while keeping our leading technology for pinch.
Variation display seems to be the hardest part that lobotommy can accept. Please let us know after trying the indiction on first move that having variants. Thanks. For showing thumbnails for variation, we think this is the most intuitive way. You can even long touch the thumbnails to remove one variation like iOS desktop apps (Check out the effect)! Variation will be better with good navigation or labels. Thanks for the comments for us to fix this part in higher priority.
The slider is used fo approximately approach a stage in the game (like 5%, 30%, 89%, 100%), then you can use the +/- button to step to the detailed move you want. Our design is good (except a bug when having no effect when finger is outside. Will fix it).
Image recognition is hard technology and it actually cannot fit many board images. But we keep improving this. The stretching of image doesn't affect the final result. That is just a preview feedback to the user. Usually some boards having special patterns or background may defeat the algorithms. So you may find that a same set of similar images cannot get correct result. Please send us the images for improvements if you are willing to.
The review assumption that "the author has not tested or used their own apps" are not true. Actually the author uses it every day, as a great go fan, and tries to make every detail shine.
The next release will be a big jump to 1.2.0 and many great detailed fixes, e.g., like persisting the web page status, game groups, etc., and MANY others (Keeping more as secrets now). And the price will rise to compete with Smartgo and others, given that we think this is the best app for Go.
