قالب وردپرس درنا توس
Home / IOS Development / The Quest for Q: What's New in Android

The Quest for Q: What's New in Android



Later this year, Android Q will appear on some of the 2.5 billion devices running on Android.
The announcement for Android Q is not entirely new to Google I / O – it has been a public beta since March – but Google has provided us with more information about what's in store in version 10.0 of the Android operating system, and the Android platform as a whole.

New features in Q

My personal favorite feature that comes into Q is live captioning.
Google announced that it has developed a way to completely voice-to-text processing on the device, without ever leaving the device.
Users with hearing loss or who are in an environment where they cannot hear the phone will be able to activate live texts in Android Q (this feature is not enabled in Beta 3).
Any sound that contains speech played on the device ̵

1; no matter which app plays it – is transcribed into text and displayed on the screen.
This works across the entire operating system, and app developers don't have to do anything to support live lyrics in their app.

Another feature that users have asked for a while is OS support for dark mode.
Dark mode allows developers to change bright white backgrounds for darker backgrounds.
Not only does this increase night-time ease of use, accidentally blocking users, but also saving battery power on many Android devices because OLED display technology uses less power for pixels on the screen that are dark or completely black.
Many first-party apps from Google already support dark mode on existing versions of Android, but there is a system-friendly switch in Q.
You can start designing and implementing night mode right now.

There are also so many other subtle changes to things like permissions, alerts and privacy that are likely to be unnoticed by many users, but enhance the security and overall user experience of the operating system.
For example, there are some new changes in alerts that give AI-powered suggested actions to some alerts, and also change to priority and user controls for how messages are displayed.
Google has a blog post that describes all of these features in more detail.

What's New for Developers

As an Android developer, I'm even more excited about what Google has announced for Android Jetpack and their developer tools. [19659004] An exciting change this year is Google's push toward making Android a Kotlin first platform.
This means that if you use Kotlin in your app, you will have access to new and concise APIs that take advantage of Kotl's language features.
And if you've just started with a new app, Google suggests that you use Kotlin instead of Java.
This Kotlin first paradigm manifests itself in many of Google's Jetpack libraries.
For example, coroutines are now supported by Room, LiveData and ViewModel – which were some of the first Android architecture components announced two years ago on I / O.

Google also introduces new libraries designed for – and sometimes written i – Kotlin.
There are a number of new libraries that Google is working on, including View Bindings, CameraX, Benchmark, Security, and most of all, Jetpack Compose.

Jetpack Compose is a brand new user interface built entirely in Kotlin.
It is completely disconnected from existing API APIs and is not built by See at all.
Instead, it provides an API reminiscent of Flutter, React and Anko.
These APIs allow you to create a declarative user interface that responds responsively to changes in the app's state to update what's on the screen.
Here's an example of what this might look like – the following code is from one of the slides on I / O, and lets you implement a list in 6 code lines instead of breaking out a RecyclerView : [19659011] ] @Composable
funny newsfeed ( stories : LiveData < List < StoryData >>) [19659023] {
ScrollingList (. historier observere ()] { history ->
StoryWidget ( ]
]
}

Jetpack Compose is fully compatible with existing layouts and impressions, allowing you to transfer to it gradually – much like how you can gradually introduce Kotlin into a Java project.
The library is still very early in development, and it is not yet an alpha version you can use yet.
Meanwhile, you can see Jetpack Compose being developed in AOSP.
You can also read more about the new Jetpack libraries on Google's blog.

These libraries have seen much faster changes than the APIs that were built into the OS itself recently, and that is an extremely good thing for developers.
Even the brand new alpha versions of Jetpack libraries that have been announced or released this week on I / O support API levels as low as 14, representing more than 99% of active devices in the Play Store.
You do not have to wait for the users to be on Q to use these new APIs that you have had before.

Google I / O marks a continuation of a trend from Google.
As Android is maturing, each version gives more Polish and fewer overhauls than the last.
These changes will ultimately benefit users, but nothing that comes in the Q edition of Android is as drastic as features like runtime permissions, material designs, or previous versions multi-window.
Many new features that will affect users the most – such as Google Lens, machine learning from a machine, and updates to Google apps such as the assistant – are distributed in Google Play or are exclusive exclusions rather than ending up in the open source portion of the Android operating system.

However, as a platform, Google pays more attention to what developers are doing and continues to strengthen them with libraries based on what developers are asking for.
These libraries decouple the APIs that developers use from the framework itself, helping to fix device-specific errors, and allowing developers to use more efficient APIs much faster than before.
It's a welcome ideology, and I'm looking forward to seeing where it takes us in the future.


Source link