翻譯頻道，平時會翻譯一些英文文章，來源不固定
Posted by Dave Burke, VP of Engineering
今天，我們給大家帶來了Android12 的第四個beta版本，已經進入了正式版本發佈的最後階段。擁有新的UI，性能提升，增強隱私和安全性，等等。我們現在集中精神專注於打磨，性能和穩定性。感謝你們的反饋，幫助我們把系統做的更好。
對於開發者，beta4帶來了穩定性，這意味着Android12的api和應用層面的行爲已經確定下來。對於應用，首要問題是兼容性和質量。應該着手準備你的應用更新，及時應對今年年底的正式系統發佈。
今天你可以在pixel的設備上通過更新使用beta 4。你也可以在一下設備上使用：ASUS, OnePlus, Oppo, Realme, Sharp, and ZTE -想要了解更多請到 android.com/beta. 瀏覽Android 12 developer site 獲得詳細步驟。
Platform Stability
Android 12 Beta 4 已經來到了 Platform Stability, 這是一個里程碑，意味着所有的在Android12中的app-facing surfaces and 行爲已經最終確定. 不只包括 official SDK and NDK APIs, but also final app-facing system behaviors and restrictions on non-SDK interfaces that may affect apps. So from Beta 4, you can confidently release your compatibility updates knowing that the platform won’t change.接下來給大家介紹timeline。
Android 12 timeline
We’re asking all app and game developers to start your final compatibility testing now and prepare to publish your compatibility updates as soon as possible ahead of the final release.
For all SDK, library, tools, and game engine developers, it’s even more important to start testing now and release your compatible updates as soon as possible -- your downstream app and game developers may be blocked until they receive your updates. When you’ve released a compatible update, be vocal and let developers know!
App compatibility
For Android, App compatibility means that your app runs as intended on a new version of the platform. You can check your app’s compatibility just by installing the production version of your app on a device or emulator and testing it - if the app looks good and runs properly, then you’re done, it’s compatible!
Testing your app for compatibility is important because with each release, we make integral changes to the platform that improve privacy and security and the overall user experience across the OS. These can affect your apps, so you should take a look at the behavior changes and test against them, then publish a compatible update to your users. It’s a basic but critical level of quality that ensures users have a good app experience.
As people update their devices to Android 12, they want to explore the latest version of Android, and experience it with their favorite apps. If those apps don’t work properly, it’s a major issue, ultimately resulting in uninstalls.
So while there are a ton of new APIs and capabilities to explore, start by testing your current app and releasing a compatible update first.
Get your apps ready
To test your app for compatibility with Android 12, just install your production app from Google Play or other source onto a device running Android 12 Beta 4. Work through all of the app’s flows and watch for functional or UI issues. Review the Android 12 behavior changes for all apps to focus your testing. Here are some changes to watch for:
Privacy dashboard - A new dashboard in Settings lets users see which apps are accessing which type of data and when. Users can adjust permissions if needed, and they can request details from your app on the reason for access. More here.
Microphone & camera indicators - Android 12 shows an indicator in the status bar when an app is using the camera or microphone. More here.
Microphone & camera toggles - New toggles in Quick Settings let users instantly disable microphone and camera access for all apps. More here.
Clipboard read notification - A toast alerts users when an app reads data from the clipboard unexpectedly. More here.
Stretch overscroll - A new “stretch” overscroll effect replaces the previous “glow” overscroll effect systemwide. More here.
App splash screens - Android 12 launches apps with a new splash screen animation. More here.
Keygen changes - Several deprecated BouncyCastle cryptographic algorithms are removed in favor of Conscrypt versions. If your app uses a 512-bit key with AES, you’ll need to use one of the standard sizes supported by Conscrypt. More here.
Remember to test the libraries and SDKs in your app for compatibility. If you find any SDK issues, try updating to the latest version of the SDK or reaching out to the developer for help.
Once you’ve published the