Google Updates Complications API for Android Wear, Introduces Wear UI And Open-Sources Components

Friday

One of the announcements made at Google I/O is an updated Complications API. It will allow Android Wear developers to easily implement complications into watch faces.

We have discussed Android Wear 2.0 earlier this year. The system is a huge step forward in terms of usability. Google wants to give developers the tools to create the best Android Wear experience. To make it happen with relative ease, a new Wear UI library has been created.

Google has introduced four new tools for Android Wear developers. They are a part of Complications API introduced last year.

  • TextRenderer – Auto-sizes text to fit in bounds defined by watch face makers.
  • ComplicationDrawable – A full rendering solution for complications, that handles all the styling for you, and adjusts the layout to fit the space you specify
  • Easy watch face settings sample – Adoptable sample code that makes it easier to build complication settings with a rich and usable experience.
  • Complication test suite – A sample data provider to help check that your watch face can handle all the combinations of fields that can make up complication data.

Since the release of Android Wear 1.0, developers complained about its closed nature. Google decided to change that and open-source some components, and migrate some of the Android Wear UI components in the Android Support Library. Additionally, some Android Wear features will merge with Android under android.support.v4.widget. Finally, outdated user interface patterns will be deprecated. Google developers expect the migration process to continue during 2017. Wear developers will have time until mid-2018 to migrate to the new UI components.

These announced changes won’t impact Android Wear users directly, but they serve as a heads-up for developers to review their code and implement new changes. All new libraries should soon be available in the Android Support Library in Android Studio.


Source: Android Developer Blog

Related Post

Next
Previous