Since the Dolphin 5.0 release, Dolphin has had opt-in usage statistics reporting to help us determine what hardware and builds users are using. Recently, this feature was also added to Dolphin Android, letting us see that around 10% of our users on development builds are using the Android version of Dolphin. Obviously, Dolphin on Android isn't going to be a perfect experience for quite some time, but in the meantime we will continue to add features and try to make the Android experience as clean as possible, even if the hardware is going to struggle with emulating GameCube and Wii games.
As a part of that, a lot of the major GUI features from the desktop version of Dolphin have been ported over. Just this year, we've seen important features like INI support, INI configuration, auto-update support, and even statistics reporting. Unfortunately, trying to bring the desktop experience to phones has caused some confusion that would seem like second nature to desktop users. Savestates in Dolphin are not compatible between builds and a lot of phone users that had been solely relying on savestates were in for a rude awakening during the next auto-update.
An unfortunate series of events lead to some deserved negative reviews on the Appstore and other mediums. With the brand-new auto-update feature came a bunch of broken savestates for users with no warning whatsoever. Unlike the desktop builds, savestates are immediately available directly from the context menu during emulation without any warnings or other information. Regardless of auto-update, relying solely on savestates for your progress is a risky proposition and we highly recommend using in-game saves as a more permanent way to save your game.
"Updated without warning and my save states were completely lost. The game's save function broke, so those were the only saves I had. For a GameCube emulator on Android it was working really well, but losing all my progress because they couldn't make old save states work with the update was really disappointing." -- User review on the Dolphin App within the Google Play Store
Dolphin's design doesn't really allow for savestates to work between different builds safely, so we were left with a difficult decision. Users randomly losing their save data is not acceptable, but removing savestates on Android would be awful. So as a compromise, we've added an option to enable savestates in the configuration menu, with an explanation of how they are intended to be used so users can understand the risks. We're sorry to anyone who ran into issues in the meantime, but as Dolphin on Android becomes a more legitimate option in the future, we're likely to run into more of these growing pains. All we can do is ask users to be patient and continue to report issues as we go forward.
Now that we've got that out of the way, there's plenty of other notable changes to get through this month so let's start chewing through them!
Fortsæt med at læse