Android was written for 32 bit. It couldn't run 64-bit before Lollipop. Currently there's about 2% of 64-bit Android devices (https://web.archive.org/web/20170808222202/http://hwstats.un...). I agree with performance argument, especially on battery-powered devices. But in this case there's nothing to be gained because LuaJIT is written for 32-bit CPU. Compiling for 64 bits won't do anything. Besides, hardly anything can squeeze more performance out of CPU than LuaJIT.
I'm complaining different issue, though. I researched the platform requirements before investing time into android development. I shared my work for free because Google doesn't allow developers in my country to charge money for their work. I kept updating the app following the user feedback. I will lose the product because of this. This feels like rug being swept under my feet :(
Why are you using an internet archive link from 2 years ago to support a claim about "currently"? It also seems to be misclassifying everything ARM into one bucket (probably because the stats were being collected from 32-bit code...).
It looks to me like for the past 3 years every single mobile ARM CPU released has been 64-bit, and even for 2 years before that roughly half of them, the market share of these must be much larger https://dev1.notebook-check.com/index.php?id=149513&sort=&ty...
I'm complaining different issue, though. I researched the platform requirements before investing time into android development. I shared my work for free because Google doesn't allow developers in my country to charge money for their work. I kept updating the app following the user feedback. I will lose the product because of this. This feels like rug being swept under my feet :(