Using the Nokia 2 on Android 8.1 with Chrome 80, the app freezes after a while with
'This page uses soo much memory, so Chrome removed some content'.
This combination of hardware, platform and browser version has been verified to support ShapeDetection API.
Note that Google distributed this phone model to developers at some point with the indication it would be a prototypical example of low-power smartphone often found in developing countries.
So for QR snapper to be useful to the next billion users, the app and/or Google Chrome needs some serious performance work.
Note that merely switching exclusively to the browser's ShapeDetection API will not work in general, since on too many devices this may not work (needs cooperation with Google Play Services, has been observed to fail in the field even with up-to-date Services). Hence an unaccelerated software fallback like what is used in QR snapper is still needed, greatly reducing the benefit of ShapeDetection API .
Please fix this.
Using the Nokia 2 on Android 8.1 with Chrome 80, the app freezes after a while with
'This page uses soo much memory, so Chrome removed some content'.
This combination of hardware, platform and browser version has been verified to support ShapeDetection API.
Note that Google distributed this phone model to developers at some point with the indication it would be a prototypical example of low-power smartphone often found in developing countries.
So for QR snapper to be useful to the next billion users, the app and/or Google Chrome needs some serious performance work.
Note that merely switching exclusively to the browser's ShapeDetection API will not work in general, since on too many devices this may not work (needs cooperation with Google Play Services, has been observed to fail in the field even with up-to-date Services). Hence an unaccelerated software fallback like what is used in QR snapper is still needed, greatly reducing the benefit of ShapeDetection API .
Please fix this.