Is up on Play now (https://play.google.com/apps/testing/com.pleco.chinesesystem to sign up for betas).
Main feature - and the reason we're drawing attention to it - is that we've finally added 64-bit support. This may result in modest performance improvements in a few areas - e.g. New OCR - but probably won't make the app feel very different overall; however, it's a Google Play requirement as of August, so we had to hurry up and get it supported now instead of waiting for 4.0. But it's good future-proofing at least - you can now be confident that in 2020 or 2021 when Android OEMs start shipping devices that no longer support 32-bit code Pleco will continue to work for you
We also updated our TTS engines, and that may be more noticeable - big update on their end and hopefully some accuracy/performance benefits on the user side. And we bumped the system requirement to Android 5.0, since there are a whole lot of modern Android things that were proving very awkward to support in Android 4.x (in fact Google Play was giving us lots of warnings because things that were required to make our app work on Android 4 - and even used by Google themselves - were forbidden in Android 10).
Main feature - and the reason we're drawing attention to it - is that we've finally added 64-bit support. This may result in modest performance improvements in a few areas - e.g. New OCR - but probably won't make the app feel very different overall; however, it's a Google Play requirement as of August, so we had to hurry up and get it supported now instead of waiting for 4.0. But it's good future-proofing at least - you can now be confident that in 2020 or 2021 when Android OEMs start shipping devices that no longer support 32-bit code Pleco will continue to work for you
We also updated our TTS engines, and that may be more noticeable - big update on their end and hopefully some accuracy/performance benefits on the user side. And we bumped the system requirement to Android 5.0, since there are a whole lot of modern Android things that were proving very awkward to support in Android 4.x (in fact Google Play was giving us lots of warnings because things that were required to make our app work on Android 4 - and even used by Google themselves - were forbidden in Android 10).