Google’s past failures were on full display at I/O 2022
arstechnica.com
arstechnica.com
I took one of the best photos that I took in the last ten years on a Fire tablet: that's a combination of the camera being "good enough" (though nowhere near as good as my iPad's camera) and being at the right place at the right time.
There was that time I was walking down the road and ran into a woman who had a huge dog that put its paws up on my shoulders and tried to push me down (in a friendly way.) She invited me into her trailer and I saw that a Fire tablet was her only computer. Although she'd never heard of Android and didn't seem so sure that Amazon had anything to do with it she was reading email, sharing photos, watching videos and doing most of what people do in their digital life.
Fire will be hard to beat for a few reasons: (1) Amazon subsidizes the devices and can afford to do so because the device sucks people into the Amazon ecosystem, and (2) Amazon makes smart choices about what features to include and which not to.
I used to have a Nexus 7 and I liked it a lot but it was packed with sensors that pushed up the BOM. Amazon is able to make tough decisions that Google somehow just can't do.
> Android apps can be written using Kotlin, Java, and C++ languages.
https://developer.android.com/guide/components/fundamentals
JetPack Compose introduction was clearly a reaction to Flutter's existence.
That alone should tell the answer about Flutter's future regarding Android.
Note that at IO, Flutter usually has its own track.
What would that be according to you?
Specially after Kotlin Native matures its JetPack Compose implementation in iOS.
The official Android framework ported to iOS, with its main language, versus a framework that belongs to an external team with no vote on either platforms.
I'm tempted to just drop it in the app since so few people used it on the web (compared to Apple Pay) and since Google doesn't care it's hard for me to care.