mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-25 23:11:02 +08:00
[translated]31 - The history of Android
This commit is contained in:
alim0x
parent
4e6bf12797
commit
31dbdb4bd2
@ -1,230 +0,0 @@
|
|||||||
alim0x translating
|
|
||||||
|
|
||||||
### Android 6.0 Marshmallow
|
|
||||||
|
|
||||||
In October 2015, Google brought Android 6.0 Marshmallow into the world. For the OS's launch, Google commissioned two new Nexus devices: the [Huawei Nexus 6P and LG Nexus 5X][39]. Rather than just the usual speed increase, the new phones also included a key piece of hardware: a fingerprint reader for Marshmallow's new fingerprint API. Marshmallow was also packing a crazy new search feature called "Google Now on Tap," user controlled app permissions, a new data backup system, and plenty of other refinements.
|
|
||||||
|
|
||||||
#### The new Google App
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
* [
|
|
||||||
|
|
||||||
][3]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][4]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][5]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][6]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][7]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][8]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][9]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][10]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][11]
|
|
||||||
|
|
||||||
Marshmallow was the first version of Android after [Google's big logo redesign][40]. The OS was updated accordingly, mainly with a new Google app that added a colorful logo to the search widget, search page, and the app icon.
|
|
||||||
|
|
||||||
Google reverted the app drawer from a paginated horizontal layout back to the single, vertically scrolling sheet. The earliest versions of Android all had vertically scrolling sheets until Google changed to a horizontal page system in Honeycomb. The scrolling single sheet made finding things in a large selection of apps much faster. A "quick scroll" feature, which let you drag on the scroll bar to bring up letter indexing, helped too. This new app drawer layout also carried over to the widget drawer. Given that the old system could easily grow to 15+ pages, this was a big improvement.
|
|
||||||
|
|
||||||
The "suggested apps" bar at the top of Marshmallow's app drawer made finding apps faster, too.
|
|
||||||
This bar changed from time to time and tried to surface the apps you needed when you needed them. It used an algorithm that took into account app usage, apps that are normally launched together, and time of day.
|
|
||||||
|
|
||||||
#### Google Now on Tap—a feature that didn't quite work out
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
* [
|
|
||||||
|
|
||||||
][12]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][13]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][14]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][15]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][16]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][17]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][18]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][19]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][20]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][21]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][22]
|
|
||||||
|
|
||||||
One of Marshmallow's headline features was "Google Now on Tap." With Now on Tap, you could hold down the home button on any screen and Android would send the entire screen to Google for processing. Google would then try to figure out what the screen was about, and a special list of search results would pop up from the bottom of the screen.
|
|
||||||
|
|
||||||
Results yielded by Now on Tap weren't the usual 10 blue links—though there was always a link to a Google Search. Now on Tap could also deep link into other apps using Google's App Indexing feature. The idea was you could call up Now on Tap for a YouTube music video and get a link to the Google Play or Amazon "buy" page. Now on Tapping (am I allowed to verb that?) a news article about an actor could link to his page inside the IMDb app.
|
|
||||||
|
|
||||||
Rather than make this a proprietary feature, Google built a whole new "Assistant API" into Android. The user could pick an "Assist App" which would be granted scads of information upon long-pressing the home button. The Assist app would get all the text that was currently loaded by the app—not just what was immediately on screen—along with all the images and any special metadata the developer wanted to include. This API powered Google Now on Tap, and it also allowed third parties to make Now on Tap rivals if they wished.
|
|
||||||
|
|
||||||
Google hyped Now on Tap during Marshmallow's initial presentation, but in practice, the feature wasn't very useful. Google Search is worthwhile because you're asking it an exact question—you type in whatever you want, and it scours the entire Internet looking for the answer or web page. Now on Tap made things infinitely harder because it didn't even know what question you were asking. You opened Now on Tap with a very specific intent, but you sent Google the very unspecific query of "everything on your screen." Google had to guess what your query was and then tried to deliver useful search results or actions based on that.
|
|
||||||
|
|
||||||
Behind the scenes, Google was probably processing like crazy to brute-force out the result you wanted from an entire page of text and images. But more often than not, Now on Tap yielded what felt like a list of search results for every proper noun on the page. Sifting through the list of results for multiple queries was like being trapped in one of those Bing "[Search Overload][41]" commercials. The lack of any kind of query targeting made Now on Tap feel like you were asking Google to read your mind, and it never could. Google eventually patched in an "Assist" button to the text selection menu, giving Now on Tap some of the query targeting that it desperately needed.
|
|
||||||
|
|
||||||
Calling Now on Tap anything other than a failure is hard. The shortcut to access Now on Tap—long pressing on the home button—basically made it a hidden, hard-to-discover feature that was easy to forget about. We speculate the feature had extremely low usage numbers. Even when users did discover Now on Tap, it failed to read your mind so often that, after a few attempts, most users probably gave up on it.
|
|
||||||
|
|
||||||
With the launch of the Google Pixels in 2016, the company seemingly admitted defeat. It renamed Now on Tap "Screen Search" and demoted it in favor of the Google Assistant. The Assistant—Google's new voice command system—took over On Tap's home button gesture and related it to a second gesture once the voice system was activated. Google also seems to have learned from Now on Tap's poor discoverability. With the Assistant, Google added a set of animated colored dots to the home button that helped users discover and be reminded about the feature.
|
|
||||||
|
|
||||||
#### Permissions
|
|
||||||
|
|
||||||
|
|
||||||
* [
|
|
||||||
|
|
||||||
][23]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][24]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][25]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][26]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][27]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][28]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][29]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][30]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][31]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][32]
|
|
||||||
|
|
||||||
Android 6.0 finally introduced an app permissions system that gave users granular control over what data apps had access to.
|
|
||||||
|
|
||||||
Apps no longer gave you a huge list of permissions at install. With Marshmallow, apps installed without asking for any permissions at all. When apps needed a permission—like access to your location, camera, microphone, or contact list—they asked at the exact time they needed it. During your usage of an app, an "Allow or Deny" dialog popped up anytime the app wanted a new permission. Some app setup flow tackled this by asking for a few key permissions at startup, and everything else popped up as the app needed it. This better communicated to the user what the permissions are for—this app needs camera access because you just tapped on the camera button.
|
|
||||||
|
|
||||||
Besides the in-the-moment "Allow or Deny" dialogs, Marshmallow also added a permissions setting screen. This big list of checkboxes allowed data-conscious users to browse which apps have access to what permissions. They can browse not only by app, but also by permission. For instance, you could see every app that has access to the microphone.
|
|
||||||
|
|
||||||
Google had been experimenting with app permissions for some time, and these screens were basically the rebirth of the hidden "[App Ops][42]" system that was accidentally introduced in Android 4.3 and quickly removed.
|
|
||||||
|
|
||||||
While Google experimented in previous versions, the big difference with Marshmallow's permissions system was that it represented an orderly transition to a permission OS. Android 4.3's App Ops was never meant to be exposed to users, so developers didn't know about it. The result of denying an app a permission in 4.3 was often a weird error message or an outright crash. Marshmallow's system was opt-in for developers—the new permission system only applied to apps that were targeting the Marshmallow SDK, which Google used as a signal that the developer was ready for permission handling. The system also allowed for communication to users when a feature didn't work because of a denied permission. Apps were told when they were denied a permission, and they could instruct the user to turn the permission back on if you wanted to use a feature.
|
|
||||||
|
|
||||||
#### The Fingerprint API
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
* [
|
|
||||||
|
|
||||||
][33]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][34]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][35]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][36]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][37]
|
|
||||||
* [
|
|
||||||
|
|
||||||
][38]
|
|
||||||
|
|
||||||
Before Marshmallow, few OEMs had come up with their own fingerprint solution in response to [Apple's Touch ID][43]. But with Marshmallow, Google finally came up with an ecosystem-wide API for fingerprint recognition. The new system included UI for registering fingerprints, a fingerprint-guarded lock screen, and APIs that allowed apps to protect content behind a fingerprint scan or lock-screen challenge.
|
|
||||||
|
|
||||||
The Play Store was one of the first apps to support the API. Instead of having to enter your password to purchase an app, you could just use your fingerprint. The Nexus 5X and 6P were the first phones to support the fingerprint API with an actual hardware fingerprint reader on the back.
|
|
||||||
|
|
||||||
Later the fingerprint API became one of the rare examples of the Android ecosystem actually cooperating and working together. Every phone with a fingerprint reader uses Google's API, and most banking and purchasing apps are pretty good about supporting it.
|
|
||||||
|
|
||||||
--------------------------------------------------------------------------------
|
|
||||||
|
|
||||||
作者简介：
|
|
||||||
|
|
||||||
Ron is the Reviews Editor at Ars Technica, where he specializes in Android OS and Google products. He is always on the hunt for a new gadget and loves to rip things apart to see how they work.
|
|
||||||
|
|
||||||
--------------------------------------------------------------------------------
|
|
||||||
|
|
||||||
via: http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/
|
|
||||||
|
|
||||||
作者：[RON AMADEO][a]
|
|
||||||
译者：[译者ID](https://github.com/译者ID)
|
|
||||||
校对：[校对者ID](https://github.com/校对者ID)
|
|
||||||
|
|
||||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
|
||||||
|
|
||||||
[a]:http://arstechnica.com/author/ronamadeo
|
|
||||||
[1]:https://www.youtube.com/watch?v=f17qe9vZ8RM
|
|
||||||
[2]:https://www.youtube.com/watch?v=VOn7VrTRlA4&list=PLOU2XLYxmsIJDPXCTt5TLDu67271PruEk&index=11
|
|
||||||
[3]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[4]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[5]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[6]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[7]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[8]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[9]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[10]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[11]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[12]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[13]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[14]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[15]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[16]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[17]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[18]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[19]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[20]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[21]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[22]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[23]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[24]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[25]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[26]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[27]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[28]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[29]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[30]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[31]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[32]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[33]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[34]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[35]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[36]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[37]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[38]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
|
||||||
[39]:http://arstechnica.com/gadgets/2015/10/nexus-5x-and-nexus-6p-review-the-true-flagships-of-the-android-ecosystem/
|
|
||||||
[40]:http://arstechnica.com/gadgets/2015/09/google-gets-a-new-logo/
|
|
||||||
[41]:https://www.youtube.com/watch?v=9yfMVbaehOE
|
|
||||||
[42]:http://www.androidpolice.com/2013/07/25/app-ops-android-4-3s-hidden-app-permission-manager-control-permissions-for-individual-apps/
|
|
||||||
[43]:http://arstechnica.com/apple/2014/09/ios-8-thoroughly-reviewed/10/#h3
|
|
||||||
@ -0,0 +1,229 @@
|
|||||||
|
安卓编年史
|
||||||
|
|
||||||
|
### 安卓 6.0 棉花糖
|
||||||
|
|
||||||
|
2015 年 10 月，谷歌给世界带来了安卓 6.0 棉花糖。配合这个版本的发布，谷歌委托生产了两部新的 Nexus 设备：[华为 Nexus 6P 和 LG Nexus 5X][39]。除了常规的性能升级，新手机还带有一套关键硬件：为棉花糖的新指纹 API 准备的指纹识别器。棉花糖还引入了一个疯狂的全新搜索特性，被称作“Google Now on Tap”，用户控制的应用权限，一个全新的数据备份系统，以及许多其它的改良。
|
||||||
|
|
||||||
|
#### 新谷歌应用
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
* [
|
||||||
|
|
||||||
|
][3]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][4]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][5]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][6]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][7]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][8]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][9]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][10]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][11]
|
||||||
|
|
||||||
|
棉花糖是[谷歌大标志重新设计][40]后的第一个安卓版本。系统也随之升级，主要是一个新的谷歌应用，给搜索小部件，搜索页面以及应用图标添加了一个多彩的标志。
|
||||||
|
|
||||||
|
谷歌将应用抽屉从页面导航的横向布局还原回了单页竖直滚动表的形式。早期版本的安卓用的都是竖直滚动表的形式，直到谷歌在蜂巢中改成了横向页面系统。滚动单页面让人更容易从很多应用中找到目标。一项“快速滚动”的特性同样好用，它可以让你拖动滚动条来激活字母索引。新的应用抽屉布局也用到了小部件抽屉上。考虑到旧系统中小部件轻松就超过了 15 页，这是个大改进。
|
||||||
|
|
||||||
|
棉花糖应用抽屉顶部的“建议应用”栏也让查找应用变得更快。该栏显示的内容一直在变化，试图在你需要的时候为你提供你需要的应用。它使用了算法来统计应用使用，经常一起打开的应用以及每天的打开次数。
|
||||||
|
|
||||||
|
#### Google Now on Tap——一个没有完美实现的特性
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
* [
|
||||||
|
|
||||||
|
][12]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][13]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][14]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][15]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][16]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][17]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][18]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][19]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][20]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][21]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][22]
|
||||||
|
|
||||||
|
棉花糖的头等新特性之一就是“Google Now on Tap”。有了 Now on Tap，你可以在安卓的任意界面长按 home 键，安卓会将整个屏幕发送给谷歌进行处理。谷歌会试着分析页面上的内容，并从屏幕底部弹出显示一个特殊的搜索结果列表。
|
||||||
|
|
||||||
|
Now on Tap 产生的结果不是通常的 10 个蓝色链接——即便那必定有一个通往谷歌搜索的链接。Now on Tap 还可以深度连接到其它使用了谷歌的应用索引功能的应用。他们的想法是你可以在 Youtube 音乐视频那里唤出 Now on tap，然后获得一个到谷歌 Play 或亚马逊“购买”页面的链接。在演员新闻文章处唤出 Now on Tap 可以链接到 IMDb 应用中该演员的页面上。
|
||||||
|
|
||||||
|
谷歌没有让这成为私有特性，而是给安卓创建了一个全新的“Assistant API（助理 API）”。用户可以挑选一个“助理应用”，它可以在长按 home 键的时候获取很多信息。助理应用会获取所有由当前应用加载的数据——不仅是直接从屏幕获取到的——连同所有这些图片还有任何开发者想要包含的元数据。这个 API 驱动了谷歌 Now on Tap，如果愿意的话，它还允许第三方打造 Now on Tap 的竞争对手。
|
||||||
|
|
||||||
|
谷歌在棉花糖的发布会上炒作了 Now on Tap，但实际上，这项特性不是很实用。谷歌搜索的价值在于你可以问它准确的问题——你输入你想要的内容，它搜索整个互联网寻找答案或网页。Now on Tap 让事情变得无限困难，因为它甚至不知道你要问的是什么。你带着特定意图打开了 Now on Tap，但你发送给谷歌的查询是很不准确的“屏幕上的所有内容”。谷歌需要猜测你查询的内容然后试着基于它给出有用的结果或操作。
|
||||||
|
|
||||||
|
在这背后，谷歌可能在疯狂处理整个页面文字和图片来强行获得你想要的结果。但往往 Now on Tap 给出的结果像是页面每个合适的名词的搜索结果列表。从结果列表中筛选多个查询就像是陷入必应的“[搜索结果过载][41]”广告里那样的情形。查询目标的缺失让 Now on Tap 感觉像是让谷歌给你读心，而它永远做不到。谷歌最终给文本选中菜单打了补丁，添加了一个“助理”按钮，给 Now on Tap 提供一些它极度需要的搜索目标。
|
||||||
|
|
||||||
|
不得不说 Now on Tap 是个失败的产物。Now on Tap 的快捷方式——长按 home 键——基本上让它成为了一个隐藏，难以发现的特性，很容易就被遗忘了。我们推测这个特性的使用率非常低。即便用户发现了 Now on Tap，它经常没法读取你的想法，在几次尝试之后，大多数用户可能会选择放弃。
|
||||||
|
|
||||||
|
随着 2016 年 Google Pixels 的发布，谷歌似乎承认了失败。它把 Now on Tap 改名成了“屏幕搜索”并把它降级成了谷歌助手的支援。谷歌助理——谷歌的新语音命令系统——接管了 Now on Tap 的 home 键手势并将它关联到了语音系统激活后的二次手势。谷歌似乎还从 Now on Tap 差劲的可发现性中学到了教训。谷歌给助理给 home 键添加了一组带动画的彩点，帮助用户发现并记住这个特性。
|
||||||
|
|
||||||
|
#### 权限
|
||||||
|
|
||||||
|
|
||||||
|
* [
|
||||||
|
|
||||||
|
][23]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][24]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][25]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][26]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][27]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][28]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][29]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][30]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][31]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][32]
|
||||||
|
|
||||||
|
安卓 6.0 终于引入了应用权限系统，让用户可以细粒度地控制应用可以访问的数据。
|
||||||
|
|
||||||
|
应用在安装的时候不再给你一份长长的权限列表。在棉花糖中，应用安装根本不询问任何权限。当应用需要一个权限的时候——比如访问你的位置、摄像头、麦克风，或联系人列表的时候——它们会在需要用到的时候询问。在你使用应用的时候，如果需要新权限时会弹出一个“允许或拒绝”的对话框。一些应用的设置流程这么处理：在启动的时候询问获取一些关键权限，其它的等到需要用到的时候再弹出提示。这样更好地与用户沟通了需要权限是为了做什么——应用需要摄像头权限，因为你刚刚点击了摄像头按钮。
|
||||||
|
|
||||||
|
除了及时的“允许或拒绝”对话框，棉花糖还添加了一个权限设置界面。这个复选框大列表让数据敏感用户可以浏览应用拥有的权限。他们不仅可以通过应用来查询，也可以通过权限来查询。举个例子，你可以查看所有拥有访问麦克风权限的应用。
|
||||||
|
|
||||||
|
谷歌试验应用权限已经有一段时间了，这些设置界面基本就是隐藏的“[App Ops][42]”系统的重生，它是在安卓 4.3 中不小心引入并很快被移除的权限管理系统。
|
||||||
|
|
||||||
|
尽管谷歌在之前版本就试验过了，棉花糖的权限系统最大的不同是它代表了一个向权限系统的有序过渡。安卓 4.3 的 App Ops 从没有计划暴露给用户，所以开发者不了解它。在 4.3 中拒绝一个应用需要的一个权限经常导致奇怪的错误信息或一个彻底的崩溃。棉花糖的系统对开发者是缺省的——新的权限系统只适用于针对棉花糖 SDK 开发的应用，谷歌将它作为开发者已经为权限处理做好准备的信号。权限系统还允许在一项功能由于权限被拒绝无法正常工作时与用户进行沟通。应用会被告知它们的权限请求被拒绝，它们可以指导用户在需要该功能的时候去打开该权限访问。
|
||||||
|
|
||||||
|
#### 指纹 API
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
* [
|
||||||
|
|
||||||
|
][33]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][34]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][35]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][36]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][37]
|
||||||
|
* [
|
||||||
|
|
||||||
|
][38]
|
||||||
|
|
||||||
|
在棉花糖出现之前，少数厂商推出了他们自己的指纹解决方案以作为对[苹果的 Touch ID][43] 的回应。但在棉花糖中，谷歌终于带来了生态级别的指纹识别 API。新系统包含了指纹注册界面，指纹验证锁屏以及允许应用将内容保护在一个指纹扫描或锁屏验证之后的 API。
|
||||||
|
|
||||||
|
Play 商店是最先支持该 API 的应用之一。你可以使用你的指纹来购买应用，而不用输入你的密码。Nexus 5X 和 6P 是最先支持指纹 API 的手机，手机背面带有指纹读取硬件。
|
||||||
|
|
||||||
|
指纹 API 推出不久后时间，是罕见的安卓生态合作例子之一。所有带有指纹识别的手机都使用谷歌的 API，并且大多数银行和购物应用都很好地支持了它。
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
作者简介：
|
||||||
|
|
||||||
|
Ron 是 Ars Technica 的评论编缉，专注于安卓系统和谷歌产品。他总是在追寻新鲜事物，还喜欢拆解事物看看它们到底是怎么运作的。
|
||||||
|
|
||||||
|
--------------------------------------------------------------------------------
|
||||||
|
|
||||||
|
via: http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/
|
||||||
|
|
||||||
|
作者：[RON AMADEO][a]
|
||||||
|
译者：[alim0x](https://github.com/alim0x)
|
||||||
|
校对：[校对者ID](https://github.com/校对者ID)
|
||||||
|
|
||||||
|
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||||
|
|
||||||
|
[a]:http://arstechnica.com/author/ronamadeo
|
||||||
|
[1]:https://www.youtube.com/watch?v=f17qe9vZ8RM
|
||||||
|
[2]:https://www.youtube.com/watch?v=VOn7VrTRlA4&list=PLOU2XLYxmsIJDPXCTt5TLDu67271PruEk&index=11
|
||||||
|
[3]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[4]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[5]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[6]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[7]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[8]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[9]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[10]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[11]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[12]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[13]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[14]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[15]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[16]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[17]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[18]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[19]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[20]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[21]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[22]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[23]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[24]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[25]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[26]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[27]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[28]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[29]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[30]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[31]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[32]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[33]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[34]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[35]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[36]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[37]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[38]:http://arstechnica.com/gadgets/2016/10/building-android-a-40000-word-history-of-googles-mobile-os/31/#
|
||||||
|
[39]:http://arstechnica.com/gadgets/2015/10/nexus-5x-and-nexus-6p-review-the-true-flagships-of-the-android-ecosystem/
|
||||||
|
[40]:http://arstechnica.com/gadgets/2015/09/google-gets-a-new-logo/
|
||||||
|
[41]:https://www.youtube.com/watch?v=9yfMVbaehOE
|
||||||
|
[42]:http://www.androidpolice.com/2013/07/25/app-ops-android-4-3s-hidden-app-permission-manager-control-permissions-for-individual-apps/
|
||||||
|
[43]:http://arstechnica.com/apple/2014/09/ios-8-thoroughly-reviewed/10/#h3
|
||||||
Loading…
Reference in New Issue
Block a user