Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Designing apps for devices powered by Wear OS is different than designing for phones or tablets.
Wear OS uses four interaction types: notifications, watch faces, native apps, and voice commands, as described in the sections below. To dive deeper into how to design for Wear OS, see the Wear OS design guidelines.
Notifications
Notifications display ambient, contextual data. A notification may also let the user launch your app.
Notifications can offer lightweight experiences, like replying to a message, opening a location on a map, or playing a song. There are ready-made notification templates for instant messaging, music playback, and calendar events.
Read more about designing notifications.
Watch faces and complications
Watch faces can tell more than the hour and date. By adding a gadget called a complication to the watch face, an installed app can display useful, timely information.
With a single tap on the watch face, users can open an app associated with a complication or change the look of the watch face itself, such as its color.
Read more about designing watch faces.
Wear OS apps
Developers can create branded, engaging experiences using native Android apps. These apps can take advantage of a watch's hardware to provide on-demand experiences that are independent of a phone.
Read more about Wear app components.
Voice commands
Voice commands allow hands-free interaction with Wear OS. Commands can use Google’s search services and trigger actions on installed apps.
Read more about Voice commands.