Andrew, given how much you love the use AI across Android devices I'm surprised that you didn't give the new APIs a mention! ;-)
Google has added some cosmetic changes to the second beta of this year's version of Android to go with the plumbing it introduced in the first beta. Android Q Beta 2 introduces a basic interprocess communication (IPC) UI that platforms, including Google itself, have toyed with. Last year Google called them "slices", but now …
"Android Q has also rushed in support for foldable phones, which is important to keep developers from getting too dependent on Samsung and Huawei APIs, resulting in further fragmentation"
I can't believe idiots are still mentioning (and falling for) the fragmentation horseshit in 2019. As usual, this idiot doesn't back up any of his claims of rushed in support, with any supporting citation...
Yep. Although what struck me most isn't so much the fragmentation as the statement that phones of (X size, Y folded size) are supported. Android supports all 'flat' screen sizes, they don't need to be specifically listed and there isn't any customisation needed to support a 4.5" phone vs a 6.5" one. So surely for the foldable screen, what should be supported is the different types of folding (in/out, external screen switch if fold in, fold along long/short axis).
The article seems to imply that folding support is only for teh specific sizes of Samsung and Xiaomi's foldies, but that doesn't make too much sense to me.
If you could be bothered to watch the video you might understand what's meant. Whenever a manufacturer introduces a feature that is not provided by the OS, developers must follow the manufacturers API. Both Samsung and Huawei allow multiple app windows on their devices and for developers to take advantage of this in their own apps, they may have to work with different APIs. The speed with which the change has gone into Q suggests that this isn't rocket science and was also presumably done in conjunction with the manufacturers (means they have less of their own code to maintain, document and support).
LG made the first Android phones that could playback 24bit 193khz audio files natively, and they then gave that work to the AOSP. Similarly, Sony have given their LDAC Bluetooth codec to the AOSP, though I don't know if can be used by 3rd party headphone vendors without licence.
I'm currently stuck on Android 6, and disabling notifications selectively sends me into a warren of setting menus in many places. Or the stupider apps turn them back on if updated. And of course what I really want to stop are the endless Google Assistant nags.
In theory the type and timing of notifications can be fine tuned. In practice life is far too short.
Is the exact argument made for smart phones. Yes, it took around 20 years to get it right, but they did (battery vs processing vs screen vs internet coverage+speed, etc etc).
Thing is, everyone is expecting these folding phones to work day one. When in reality, it's investing in the early adopters, fashionable and easy marks for paying for the next 20 years of development before we get a "good enough" or "amazing" folding solution.
Biting the hand that feeds IT © 1998–2021