We will see whether our renewed testing will help us to determine what causes the crash. You said that the crashes started happening after you researched the last level of advertising, and that you had researched all the other areas before that. We'll see where that leads us.

I would like to say though, that we didn't just let it go. It might help at this point if I explain a bit about the process of bug-fixing. The most successful method of fixing bugs is based on reproducing them in our software development environment using debugging tools, where we can force the bug to happen and locate exactly what part of the code is causing the problem. In that situation, there's pretty much a 100% chance of fixing a bug. The difficulty with fixing a bug that fails only rarely or under a specific set of circumstances is that we can't use that method, since we can't reproduce the bug and force it to occur. The only thing left to do then is to use our eyes and brains to review pertinent parts of the code to see what we can find. It's not nearly as successful, especially for these elusive bugs. Video games have a lot of complex programming.

I am not convinced that these issues are related to the particular brand or model of Android device, but I suppose it's a possibility. The devices that Fish Tycoon was tested on (back in 2010 when the game being prepared for Android) were Android phones running Android 1.6 and 2.2. Today we use a combination of Android phones and tablets. We have a mix of Samsung, Google Nexus and Amazon devices, since those represent the primary app stores where we offer our games.

Like you, we have to use our resources wisely, and those are the devices we settled on after checking out what the majority of our customers are using to run our games.