MOUNTAIN VIEW, Calif.—Google has provided three major updates to Android Wear since it came to market two years ago—every time the version of Android that Wear is built on top of is updated, Google also adds Wear-specific features. Android 5.0, 5.1, and 6.0 all had corresponding Wear releases that smoothed out rough edges, refined the interface, and made the watches more capable.

Today at its developer conference, Google is announcing Android Wear 2.0, a version number bump that reflects the magnitude of the changes it introduces. The update gives the UI a comprehensive Material Design-themed overhaul, enables compatible watches to do more without a phone attached, introduces some new input methods to make communication easier, and copies one of the things that the Apple Watch gets right. And since it’s based on Android N, it picks up support for features like Data Saver, Java 8, and new emoji, among other platform features. Here are the highlights.

Standalone apps

Probably the biggest addition to Wear 2.0 is the ability for apps to communicate directly over the Internet via Bluetooth, Wi-Fi, or (for the few watches that have it) cellular, rather than relying exclusively on a tethered phone or cloud syncing between your watch and your phone for communication.

This mostly just means that your watch will be more useful without your phone, at least when it has Internet connectivity (Android Wear watches can already connect to known Wi-Fi networks automatically when your phone is out of Bluetooth range or on another known network entirely). But Google also points out that this will allow users of Android Wear on iOS to enjoy more capable apps.

Apple doesn’t offer full-fledged smartwatch APIs for Wear to hook into, and so using Wear with an iPhone is an inherently limited experience; with standalone apps, watches will be able to communicate directly over the Internet using Wi-Fi or your iPhone’s LTE connection, skirting around the API problem that currently makes Wear on iOS so lackluster.

The utility of this feature for your particular watch may vary depending on which features it supports; early Wear watches didn’t include Wi-Fi support because the software platform launched without it. But this is great for modern watches with full-featured wireless—smart watches will slowly become less dependent on our phones over time just as our phones became less dependent on our PCs, and this is a significant step down that road.

An API for complications

Third parties have been able to make Android Wear watch faces for some time now, but the kind of information they can display is heavily dependent on the watch face itself—even with lots of options, it might be hard to find one that looks good and gives you the glance-able information you want.

Wear 2.0 introduces a full-fledged API for complications, those little snippets of extra information on dumb watches (or on the Apple Watch, for that matter) that show you things like the current date or moon phases. The Complications API lets app developers pass raw data to watch faces, which can format and style the data however they want to make it look good next to the rest of the watch face. Tapping on individual complications can take you into the full watch app for more information.

These complications should obviate the need for purpose-built weather or fitness-related watch faces, among others. All we need are apps and watch faces that use the API.

A redone UI

Android Wear’s notification cards have been redesigned to be primarily light text on a black background instead of dark text on a white background, which the company says is intended to conserve battery life on watches with OLED screens and to make notifications less obtrusive if they light your watch up in a dark or dimly lit room.

A few other core aspects of the UI have been tweaked and rethought, too. When notification cards are waiting for you, your watch face will display smaller, less obtrusive icons instead of devoting a big swath of the watch face to a notification card. As you swipe through your notification cards, you’ll see a small progress bar scooting along the right side of the display to show you how far you’ve gone down your notification stack. That bar and the revised app launcher both hug the curved edges of round screens, reflecting the fact that most Android Wear watches are now round instead of square (though Google assured us that square screens still work just fine).

We’ll need to get our hands on some actual software to take stock of all the changes—look for that to happen as soon as we can get the preview installed.

A dinky keyboard and handwriting recognition

You can already kind-of-sort-of use your watch for texting and Hangouts and other communications now, but you mostly have to rely on sometimes-flaky voice dictation features and short, canned quick replies. Wear 2.0 adds two new input methods: a tiny little swipe-style keyboard that you can use to type and a handwriting recognition mode that lets you sketch out letters on your watch’s screen to spell out messages.

Given the small size of most Android Wear displays, these input methods still don’t sound like they’ll be a ton of fun to use. But for situations where you can’t or don’t want to use voice and your short canned replies won’t get the job done, both options give you more ways to send out a quick response without digging out your phone. Any app that already allows for voice input automatically supports the two new input methods without any additional effort on the part of app developers.

Google Fit additions

Finally, Wear 2.0 makes a handful of Google Fit-related improvements intended to make Wear watches better fitness trackers. Some of these are really only of interest to developers—watch apps can automatically be notified and updated when Fit data changes, rather than having to query for updates constantly. But apps will also be able to detect when users begin walking, running, or biking, and they can use that information to automatically open the appropriate apps.

Developer preview details

Android Wear 2.0 will be available today as a developer preview, though the bad news is that your hardware options are pretty limited right now. It’s only compatible with the LG Watch Urbane Second Edition LTE (quite a name, that one) and the Huawei Watch, and anyone with different hardware will need to rely on the Android emulator images for testing.

That’s certainly not the full list of existing Wear watches that will get the 2.0 update—so far, every Wear update has eventually been delivered to every Wear watch going all the way back to the original LG G Watch and Samsung Gear Live. Wear has no skins and doesn’t allow extensive OEM-specific customization, so the situation isn’t as bad as it is for phones and tablets. Though Google wouldn’t confirm or deny to us whether all watches would get the final version of Wear 2.0 when it’s ready, the press picture above shows the second-generation Moto 360 and the Asus ZenWatch 2 alongside the LG and Huawei hardware. Hardware shouldn’t be a limiting factor, at least—almost all past and present Android Wear hardware uses the same Snapdragon 400 SoC, so if it will run on current watches it should run on older ones, too.

We won’t know more details for sure until the finished version of Android Wear 2.0 is released this fall, presumably around the same time that the final Android N code is released to Nexus devices and the AOSP repositories. In the meantime, Google is asking developer preview users to leave feedback about features and bugs, which you can do over here.