Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 56b65fdd authored by David Friedman's avatar David Friedman
Browse files

Docs: Revisions to Wear 2.0 Preview API Overview page 

Bug: 28714669

Change-Id: I2e24fd8ab37cc74e4b8b3828b769b031aa57f863
parent 2015256c

docs/html/wear/preview/api-overview.jd

+118 −131
Original line number Diff line number Diff line
@@ -12,13 +12,6 @@ page.image=images/cards/card-n-apis_2x.png 
  <h2>Key developer features</h2>

  <ol>

      <ul style="list-style-type:none;">

        <li><a href="#stand-alone">Standalone Devices</a>

          <ol>

            <li><a href="#wear-apk">Wear-Specific APKs</a></li>

            <li><a href="#network">Network Access</a></li>

            <li><a href="#auth">Authentication</a></li>

          </ol>

        </li>

        <li><a href="#notify">Notifications and Input</a>

          <ol>

            <li><a href="#expanded">Expanded Notification</a></li>
@@ -30,6 +23,13 @@ page.image=images/cards/card-n-apis_2x.png 
            <li><a href="#imf">Input Method Framework</a></li>

          </ol>

        </li>

        <li><a href="#stand-alone">Standalone Devices</a>

          <ol>

            <li><a href="#wear-apk">Wear-Specific APKs</a></li>

            <li><a href="#network">Network Access</a></li>

            <li><a href="#auth">Authentication</a></li>

          </ol>

        </li>

        <li><a href="#ui">User Interface Improvements</a>

          <ol>

            <li><a href="#complications">Complications</a></li>
@@ -48,100 +48,6 @@ page.image=images/cards/card-n-apis_2x.png 
  highlight some of the new features for Wear developers.

</p>



<h2 id="stand-alone">Standalone Devices</h2>



<p>Standalone watches will enable Android Wear apps to work independently of phone

 apps. This means your app can continue to offer full functionality even if the 

 paired phone is far away or turned off. </p>



<h3 id="wear-apk">Wear-Specific APKs</h3>



<p>For delivery to a watch, an Android Wear app is currently embedded in its corresponding

phone app. This delivery method can result in an increased download size for users,

 regardless of whether they have an Android Wear device.

</p>



<p>This delivery method is planned to change; the

<a href ="{@docRoot}google/play/publishing/multiple-apks.html">Multi-APK</a>

 delivery method will be used. Developers will have the ability to release Android

  Wear apps independently of the corresponding phone apps. Please stay tuned for

   more information about this change.

</p>



<h3 id="network">Network Access</h3>



<p>Since Android Wear apps will work independently of phone apps, Android Wear's

 network access will no longer require the

 <a href="{@docRoot}training/wearables/data-layer/index.html">

 Wearable Data Layer API</a>. Android Wear apps will have the ability to make

 their own network requests. Additionally, they will be able to directly use

 Google Cloud Messaging.

</p>



<p>No APIs for network access or GCM are specific to Android Wear; refer to the

existing documentation about

<a href="{@docRoot}training/basics/network-ops/connecting.html">

Connecting to the Network</a> and

<a href="https://developers.google.com/cloud-messaging/">Cloud Messaging</a>.

</p>



<p>We recommend using the following libraries:</p>

<ul>

<li><a href="{@docRoot}reference/android/app/job/JobScheduler.html">

JobScheduler</a> for asynchronous jobs, including polling at regular intervals

</li>

<li>Multi-networking APIs if you need to connect to specific network types; see

the <a href="{@docRoot}about/versions/android-5.0.html#Wireless">

Multiple Network Connections</a>

</li>

</ul>



<p>You will still be able to use the

<a href="{@docRoot}training/wearables/data-layer/index.html">

 Wearable Data Layer API</a> to communicate with a phone app.

 However, use of this API to connect to a network will be discouraged.

 </p>





<h3 id="auth">Authentication</h3>



<p>Since Android Wear apps will work independently of phone apps, Android Wear's

 authentication capabilities will be more powerful; apps will have new ways to

 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>



<p>Google Keyboard will be standard on Android Wear, allowing for direct text entry.

 This feature will work as expected with standard

 <a href="{@docRoot}reference/android/widget/EditText.html">

  EditText widgets</a>. For passwords, the {@code textPassword} attribute will be

   used.



<h4>Utilizing Account Manager</h4>

Android Wear will include the <a href="{@docRoot}reference/android/accounts/AccountManager.html">

AccountManager</a>; it is planned to be accessible for syncing and storing account

 data, as it is on an Android phone.

</p>







<h2 id="notify">Notifications and Input</h2>



<p>In Wear 2.0, we’ve redesigned the key experiences on the watch to be even more
@@ -149,7 +55,10 @@ AccountManager</a>; it is planned to be accessible for syncing and storing accou 
  are below; for a complete list of changes, see

  <a href="{@docRoot}wear/preview/features/notifications.html">Notification Changes in Wear 2.0</a>.





<img src="{@docRoot}wear/preview/images/expanded_diagram.png" height="240" style="float:right;margin:10px 0 0 40px" />

<h3 id="expanded">Expanded notifications</h3>



<p>When a user taps on a notification that is bridged from the phone to

the watch or that lacks a <a href="{@docRoot}reference/android/support/v4/app/NotificationCompat.Builder.html#setContent

Intent(android.app.PendingIntent)">{@code contentIntent}</a>, the user will be
@@ -158,8 +67,7 @@ taken to the expanded view of that notification. When you 
 content pages</a> and actions for a notification, those are available to the user

  within the expanded notification. Each expanded notification follows <a href="https://google.com/design/wear">Material Design for Android Wear</a>, so the user gets an app-like experience.

</p>

<p><img src="{@docRoot}wear/preview/images/expanded_diagram.png"></p>

<p><b>Figure 1</b>.An expanded notification</p>





<h3 id="messaging">Messaging Style notification</h3>

<p> If you have a chat messaging app, your notifications should use
@@ -173,6 +81,7 @@ expanded notification. 




<h3 id="smart-replies">Smart Reply</h3>



<p>Android Wear 2.0 introduces support for Smart Reply in

<a href="{@docRoot}wear/preview/features/notifications.html#messaging">{@code MessagingStyle}</a>

 notifications. Smart Reply provides the user with contextually relevant,
@@ -180,25 +89,16 @@ expanded notification. 
 <a href="{@docRoot}reference/android/app/RemoteInput.html">{@code RemoteInput}</a>.

</p>



<p><img src="{@docRoot}wear/preview/images/messaging_style.png"></p>

<p><b>Figure 2</b>.Messaging Style notification with smart replies</p>



<p>By enabling Smart Reply for your {@code MessagingStyle} notifications, you provide

users a fast (single tap), discreet (no speaking aloud), and reliable way to respond

 to chat messages they receive.

 </p>





<h3 id="remote-input">Remote Input</h3>

<div style="float:right;">

<img src="{@docRoot}wear/preview/images/remoteinput.png" style="padding-left:1.5em;">



<p class="img-caption" style="padding-left:2em;">

  <strong>Figure 5.</strong> Remote Input.

</p>

<img src="{@docRoot}wear/preview/images/remoteinput.png" height="240" style="float:right;margin:10px 0 0 40px" />



<h3 id="remote-input">Remote Input</h3>



  </div>

<p>Wear 2.0 users can choose between various input options from

<a href="{@docRoot}reference/android/app/RemoteInput.html">Remote Input</a>.

 These options include:
@@ -224,7 +124,7 @@ For messaging notifications with Smart Reply, the system-generated Smart Reply 
<h3 id="bridging"> Bridging Mode </h3>

<p>By default, notifications are

<a href="{@docRoot}training/wearables/notifications/index.html">

bridged</a> (shared) from an app on a companiosubl apin phone

bridged</a> (shared) from an app on a companion phone

to the watch. Since a phone app and a standalone watch app may be sources of the

 same notifications, the Android Wear 2.0 Preview includes a Bridging mode feature.

  Developers can begin planning to change the behavior of notifications with the
@@ -261,6 +161,99 @@ This allows users to enter text on Wear using the system default IME or third pa 
Input Method Framework</a>.

</p>





<h2 id="stand-alone">Standalone Devices</h2>



<p>Standalone watches will enable Android Wear apps to work independently of phone

 apps. This means your app can continue to offer full functionality even if the

 paired phone is far away or turned off. </p>



<h3 id="wear-apk">Wear-Specific APKs</h3>



<p>For delivery to a watch, an Android Wear app is currently embedded in its corresponding

phone app. This delivery method can result in an increased download size for users,

 regardless of whether they have an Android Wear device.

</p>



<p>With standalone devices, the

<a href ="{@docRoot}google/play/publishing/multiple-apks.html">Multi-APK</a>

 delivery method will be used. Developers will have the ability to release Android

  Wear apps independently of the corresponding phone apps. Please stay tuned for

   more information about this change.

</p>



<h3 id="network">Network Access</h3>



<p>Since Android Wear apps will work independently of phone apps, Android Wear's

 network access will no longer require the

 <a href="{@docRoot}training/wearables/data-layer/index.html">

 Wearable Data Layer API</a>. Android Wear apps will have the ability to make

 their own network requests. Additionally, they will be able to directly use

 Google Cloud Messaging.

</p>



<p>No APIs for network access or GCM are specific to Android Wear; refer to the

existing documentation about

<a href="{@docRoot}training/basics/network-ops/connecting.html">

Connecting to the Network</a> and

<a href="https://developers.google.com/cloud-messaging/">Cloud Messaging</a>.

</p>



<p>We recommend using the following libraries:</p>

<ul>

<li><a href="{@docRoot}reference/android/app/job/JobScheduler.html">

JobScheduler</a> for asynchronous jobs, including polling at regular intervals

</li>

<li>Multi-networking APIs if you need to connect to specific network types; see

the <a href="{@docRoot}about/versions/android-5.0.html#Wireless">

Multiple Network Connections</a>

</li>

</ul>



<p>You will still be able to use the

<a href="{@docRoot}training/wearables/data-layer/index.html">

 Wearable Data Layer API</a> to communicate with a phone app.

 However, use of this API to connect to a network will be discouraged.

 </p>





<h3 id="auth">Authentication</h3>



<p>Since Android Wear apps will work independently of phone apps, Android Wear's

 authentication capabilities will be more powerful; apps will have new ways to

 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>



<p>Google Keyboard will be standard on Android Wear, allowing for direct text entry.

 This feature will work as expected with standard

 <a href="{@docRoot}reference/android/widget/EditText.html">

  EditText widgets</a>. For passwords, the {@code textPassword} attribute will be

   used.



<h4>Utilizing Account Manager</h4>

Android Wear will include the <a href="{@docRoot}reference/android/accounts/AccountManager.html">

AccountManager</a>, which will be accessible for syncing and storing account

 data, as it is on an Android phone.

</p>



<h2 id="ui">User Interface Improvements</h2>



<p>The preview introduces powerful additions to the user interface, opening up
@@ -272,6 +265,8 @@ minutes. With the Complications API, 
The navigation and action drawers provide users with new ways to interact with apps.

</p>



<img src="/wear/preview/images/complications-main-image.png" height="240" style="float:right;margin:10px 0 0 40px" />



<h3 id="complications">Complications</h3>



<p>A complication is a feature of a watch face <a href="https://en.wikipedia.org/wiki/Complication_(horology)">
@@ -279,14 +274,6 @@ that displays more than hours and minutes</a>. For 
example, a battery indicator is a complication. The Complications API is for

both watch faces and data provider apps.</p>



<div style="float:right;">

<img src="images/complications-main-image.png"" style="padding-left:1.5em;">



<p class="img-caption" style="padding-left:2em;">

  <strong>Figure 5.</strong> Watch face Complications.

</p>

  



<p>Watch faces can display extra information without needing code for getting

the underlying data. Data providers can supply data to any watch face using the

API.</p>
@@ -309,13 +296,13 @@ see <a href="{@docRoot}wear/preview/features/complications.html"> 


<div class="cols">

<div class="col-2of6">

  <img src="{@docRoot}wear/preview/images/nav_drawer.gif" alt="" style="padding:.5em">

  <img src="{@docRoot}wear/preview/images/nav_drawer.gif" height="240" alt="" style="padding:.5em">

  <p class="img-caption">

      <strong>Figure 1.</strong> Navigation and Action Drawers.

    </p>

</div>

<div class="col-2of6">

  <img src="{@docRoot}wear/preview/images/action_drawer.gif" alt="" style="padding:.5em;"">

  <img src="{@docRoot}wear/preview/images/action_drawer.gif" height="240" alt="" style="padding:.5em;"">

</div>

</div>

<div class="cols">

docs/html/wear/preview/images/expanded_diagram.png

−15.5 KiB (56 KiB)
Loading image diff...

docs/html/wear/preview/images/messaging_style_diagram.png

0 → 100644
+69.3 KiB
Loading image diff...