Google's user faced architecture often just seems like an unmanaged jumbled up bunch of code that they throw at you, good luck have fun.
That's a little bit like saying that Chez Panisse doesn't even deliver sewage to your table, and that if you want to pour it over your food you need to bring your own chamber pot with you.
Java is not a great language to program in, but if there's any language it is clearly better than, then that language is JavaScript. Why would one want to program an Android app in JavaScript rather than in Java?
There's only one reason to use JavaScript: because one is deploying in a browser, and JavaScript is the only language supported by the vast, vast majority of browsers. In every other way, it's a misbegotten mistake of a language.
But I've found some peace using Android without the mothership. That's CopperheadOS with F-droid:
https://guardianproject.info/2016/03/28/copperhead-guardian-...
It's simple and it works well.
But yeah, things are a bit messy from a development perspective. Too much fragmentation I guess.
FTFY ;)
Basically pair featurephone with smartphone or tablet, and then tell the smartphone or tablet to use the featurephone as their internet connection.
Mind you this is all on Android, and i am not American so i do not have to deal with carriers mucking up my featurephone firmware.
Edit: Just reminded myself that the term used is tethering. If i can't find a wifi hotspot to use, i tether smart device to the featurephone over bluetooth and thus use the phones mobile connection as the net connection for the smart device.
I wish the big 4 would get their act together and stop pissing on each others legs.
FB is the most recent entry into this clusterfuck. They should be ashamed of the Oculus/GearVR developer experience, it was the determining factor in my abandoning Oculus.
It is the developer that pays the cost in the end.
Yep and I think too many have that same feeling. Not sure if they can afford that but we will see.
I'm not saying that iOS is better. Don't really know. I've played with Swift and a few of the Apple tutorials.
In general, I'm against the current incarnation of mobile. After years of having an Android (and now having an iPhone due to work), I switched to a Samsung Juke. That's right, a feature phone! The Android just got slower and slower. No updates, not improvements. Finally it screeched in my ears while working. I picked it up and slammed it on the desk (felt great for a week). Both iOS and Android are slow, overly wrought operating systems.
That being said, unlike the author, I'll still use Android and iOS for my products. I have products that need to be mobile. They have to target the machines my customers have now. That also means that I'll have two native app code bases. I'll have to keep track of native app UX/UI standards. I'll have to keep such hardware around ('cause Android's emulator is still sucks when I've got an VM running).