canoe icon indicating copy to clipboard operation
canoe copied to clipboard

Cannot load in the older Android version (4.4.2)

Open gokr opened this issue 6 years ago • 3 comments

Reported on reddit, "Just stuck on the first screen (where the Canoe logo is shown). "

gokr avatar Mar 29 '18 17:03 gokr

I have the same issue on an Android 6.0 and a 4.4.4 device.

BWagener avatar Mar 31 '18 09:03 BWagener

I'm going to chime in a "request OS" legacy support. In general, android features (at least built with native SDK), are possible to suppport going back as early as Android api 8, with the ability to use progressive enhancement and introspect api versions to ensure it's possible to use the latest and greatest api while keeping backward compatibility. Many people in developing countries are on older 4.0-4.4 Android versions. After 5.0, it was much trickier for a hardware manufacturer to avoid working directly with Google and sustain an AOSP development branch. Google got a lot more serious about making hardware vendors come directly to Google to license key pieces (mainly app store and apps), and therefore you are starting to see entire generations of devices that don't get updates to 5.x and beyond. Now the pitch for legacy devices: if Cryptocurrency is to be the "disruptor" it should be so for that next billion people coming online for the first time, not just the people that can afford modern smart phones. Remember, if you can target a $25 device as easily as a $250 device, you will reach a wider audience for the app.

Kudos for supporting an apk direct download for people who don't build themselves and don't have access to Google Play store.

Now for the personal pitch: API 18 is supported on all BB OS10 (Blackberry) devices, and it would be nice to have a version of the app that runs on these devices. I'll look into the Cordova base to see what it might take to get a version building natively for BB OS 10 as an additional platform, since it sounds like API 19 might be the current min SDK.

truedat101 avatar Oct 30 '18 06:10 truedat101

Also - I have access to a handful of legacy devices so I can test. I suppose the first thing is to grasp the nature of the issue reported. Since @BWagener reported on a 6.0 device, this is actually not what I would consider legacy, although it is not the latest, it's definitely a generational leap above the 4.x devices.

truedat101 avatar Oct 30 '18 19:10 truedat101