wearable/wear/WearMessagingApp/template-params.xml

<?xml version="1.0" encoding="UTF-8"?>
<!--
 Copyright 2017 The Android Open Source Project

 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.
 You may obtain a copy of the License at

     http://www.apache.org/licenses/LICENSE-2.0

 Unless required by applicable law or agreed to in writing, software
 distributed under the License is distributed on an "AS IS" BASIS,
 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
-->
<sample>
    <name>WearMessagingApp</name>
    <group>Wearable</group>  <!-- This field will be deprecated in the future
                            and replaced with the "categories" tags below. -->
    <package>com.example.android.wearable.wear.messaging</package>

    <minSdk>22</minSdk>
    <targetSdkVersion>25</targetSdkVersion>
    <targetSdkVersionWear>25</targetSdkVersionWear>

    <wearable>
        <has_handheld_app>true</has_handheld_app>
    </wearable>

    <!-- Include additional dependencies here.-->
    <!-- dependency>com.google.android.gms:play-services:5.0.+</dependency -->

    <dependency>com.android.support:appcompat-v7:25.1.1</dependency>
    <dependency>com.android.support:cardview-v7:25.1.1</dependency>
    <dependency>com.android.support:design:25.1.1</dependency>

    <!--<dependency>com.google.android.gms:play-services-wearable:10.2.0</dependency>-->
    <dependency>com.google.android.gms:play-services-auth:10.2.0</dependency>

    <dependency>com.github.bumptech.glide:glide:3.7.0</dependency>

    <dependency_wearable>com.android.support:appcompat-v7:25.1.1</dependency_wearable>
    <dependency_wearable>com.android.support:design:25.1.1</dependency_wearable>

    <strings>
        <intro>
            <![CDATA[
            Sample demonstrates best practices for building a messaging experience on Android Wear.
            ]]>
        </intro>
    </strings>

    <template src="Wear" />

    <metadata>
        <!-- Values: {DRAFT | PUBLISHED | INTERNAL | DEPRECATED | SUPERCEDED} -->
        <status>DRAFT</status>
        <!-- See http://go/sample-categories for details on the next 4 fields. -->
        <!-- Most samples just need to udpate the Categories field. This is a comma-
             seperated list of topic tags. Unlike the old category system, samples
             may have multiple categories, so feel free to add extras. Try to avoid
             simply tagging everything with "UI". :)-->
        <categories>Wearable</categories>
        <technologies>Android</technologies>
        <languages>Java</languages>
        <solutions>Mobile</solutions>
        <!-- Values: {BEGINNER | INTERMEDIATE | ADVANCED | EXPERT} -->
        <!-- Beginner is for "getting started" type content, or essential content.
             (e.g. "Hello World", activities, intents)

             Intermediate is for content that covers material a beginner doesn't need
             to know, but that a skilled developer is expected to know.
             (e.g. services, basic styles and theming, sync adapters)

             Advanced is for highly technical content geared towards experienced developers.
             (e.g. performance optimizations, custom views, bluetooth)

             Expert is reserved for highly technical or specialized content, and should
             be used sparingly. (e.g. VPN clients, SELinux, custom instrumentation runners) -->
        <level>INTERMEDIATE</level>
        <!-- Dimensions: 512x512, PNG fomrat -->
        <icon>screenshots/icon-web.png</icon>
        <!-- Path to screenshots. Use <img> tags for each. -->
        <screenshots>
            <img>screenshots/1-main.png</img>
            <img>screenshots/2-settings.png</img>
        </screenshots>
        <!-- List of APIs that this sample should be cross-referenced under. Use <android>
        for fully-qualified Framework class names ("android:" namespace).

        Use <ext> for custom namespaces, if needed. See "Samples Index API" documentation
        for more details. -->
        <api_refs>
            <android>android.app.ActionBar</android>
        </api_refs>

        <!-- 1-3 line description of the sample here.

            Avoid simply rearranging the sample's title. What does this sample actually
            accomplish, and how does it do it? -->
        <description>
            Sample demonstrating how to instantiate an ActionBar on Android, define
            action items, and set an "up" navigation link. Uses the Support Library
            for compatibility with pre-3.0 devices.
        </description>

        <!-- Multi-paragraph introduction to sample, from an educational point-of-view.
        Makrdown formatting allowed. This will be used to generate a mini-article for the
        sample on DAC. -->
        <intro>
            Long intro here.

            Multi-paragraph introduction to sample, from an educational point-of-view.
            *Makrdown* formatting allowed. See [Markdown Documentation][1]
            for details.

            [1]: http://daringfireball.net/projects/markdown/syntax
        </intro>
    </metadata>
</sample>