Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Docs: Update Auth section of API Overview am: 480b523c8e

Browse Source 
am: 773ad4f422

Change-Id: Iad796f9112ee003559ccfab899be75b0ab1734f4
This commit is contained in:
Bert McMeen
2016-06-23 17:31:45 +00:00
committed by android-build-merger
parent 7aac630f8e 773ad4f422
commit f829cb954a
1 changed files with 24 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

52
docs/html/wear/preview/api-overview.jd
View File

@@ -4,9 +4,6 @@ page.tags="wear"
page.image=images/cards/card-n-apis_2x.png page.image=images/cards/card-n-apis_2x.png
@jd:body @jd:body
<div id="qv-wrapper"> <div id="qv-wrapper">
<div id="qv"> <div id="qv">
<h2>Key developer features</h2> <h2>Key developer features</h2>
@@ -298,36 +295,35 @@ Multiple Network Connections</a>
authentication capabilities will be more powerful; apps will have new ways to authentication capabilities will be more powerful; apps will have new ways to
authenticate.</p> authenticate.</p>
<h4> Authentication tokens can be passed over the Wearable Data Layer </h4>
<p>For Android-paired watches (only), the phone will securely transfer authentication
data to a watch app via the
<a href="{@docRoot}training/wearables/data-layer/index.html">
Wearable Data Layer API</a>. The data can be transferred as
Messages or Data Items. </p>
<p>If your watch app needs to determine if your phone app is installed, you can
advertise a capability on the phone app and retrieve the capability on the watch.
For more information, see following sections of
<a href="{@docRoot}training/wearables/data-layer/messages.html">
Sending and Receiving Messages</a>:
<ul>
<li>Advertise Capabilities</li>
<li>Retrieve the Nodes with the Required Capabilities</li>
</ul>
<h4>Users can enter a username and password on a watch</h4> <h4>Users can enter a username and password on a watch</h4>
<p>Google Keyboard will be standard on Android Wear, allowing for direct text entry. <p>Google Keyboard will be standard on Android Wear, allowing for direct text
This feature will work as expected with standard entry. This feature will work as expected with standard
<a href="{@docRoot}reference/android/widget/EditText.html"> <a href="{@docRoot}reference/android/widget/EditText.html">EditText widgets</a>.
EditText widgets</a>. For passwords, the {@code textPassword} attribute will be For passwords, the {@code textPassword} attribute will be used.</p>
used.
<h4>Utilizing Account Manager</h4> <h4>Utilizing Account Manager</h4>
Android Wear will include the <a href="{@docRoot}reference/android/accounts/AccountManager.html">
<p>Android Wear will include the
<a href="{@docRoot}reference/android/accounts/AccountManager.html">
AccountManager</a>, which will be accessible for syncing and storing account AccountManager</a>, which will be accessible for syncing and storing account
data, as it is on an Android phone. data, as it is on an Android phone.</p>
</p>
<h4>Authentication tokens can be passed over the Wearable Data Layer</h4>
<p>For Android-paired watches (only), a phone securely
transfers authentication credentials to a watch app via the
<a href="{@docRoot}training/wearables/data-layer/index.html">
Wearable Data Layer API</a>. The credentials can be transferred as
messages or data items.</p>
<p>If your watch app needs to determine if your phone app is installed, you can
advertise a capability on the phone app and retrieve the capability on the
watch. For more information, see the following sections of
<a href="{@docRoot}training/wearables/data-layer/messages.html">
Sending and Receiving Messages</a>:</p>
<ul>
<li>Advertise Capabilities</li>
<li>Retrieve the Nodes with the Required Capabilities</li>
</ul>