With the brand-new auto-update feature came a bunch of broken savestates for users with no warning whatsoever. 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.Īn unfortunate series of events lead to some deserved negative reviews on the Appstore and other mediums. Unfortunately, trying to bring the desktop experience to phones has caused some confusion that would seem like second nature to desktop users.
Just this year, we've seen important features like INI support, INI configuration, auto-update support, and even statistics reporting.
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.Īs a part of that, a lot of the major GUI features from the desktop version of Dolphin have been ported over. 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.
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.
