It has been 24 hours since I put Google’s Android Wear LG G smart watch on. And I have to say, I’m pretty excited.

Below are my thoughts on what the current experience looks like, and what some of the opportunities in wearable design are going forward.

Current state: Android Wear today

First: Aesthetics.

The LG G is a surprisingly slick little watch. With a 1.65 inch display, it’s not exactly little, but it’s not that large either. I have comically slender (dare I say dainty) wrists, so I initially assumed the watch would be both too large and too awkward for me to wear in public. Remarkably, the LG G fits perfectly.

Now, either someone at Google/LG G decided to measure teenage boys’ wrists for the product (because boys! and gadgets! that’s a thing!), or they are actually designing wearables with women in mind.

I jest, but this is actually not trivial when you think about it: Women buy more consumer electronics than men, install more apps, and spend more on paid apps, so it’s not only important that wearables are done right for both sexes, but especially for women. Startups like Ringly have picked up on this, designing fashionable smartphone-connected jewelry and accessories precisely for that market. As the market grows, wearables will have to not only address fashion, but cater to it.

This is why the fact that you can swap out wristbands on the LG G is a small but important first step. The LG G’s screen resolution may not be as good as the Samsung watch’s (which many a developer repeatedly told me at I/O when I showed them my choice), but to the average consumer, aesthetic details are likely to trump minor differences in screen resolution. This is also why having the round Moto 360 is the right move, despite naysayers that complain screens aren’t meant to be circular. (Notice though, that all of the Moto 360 marketing material pictures men, so we still have a ways to go on designing wearables with women in mind.)

The LG G is not a gorgeous accessory, but it definitely looks more watch-like than gadgety, and that’s promising.

Second: Functionality.

In its current iteration, taking actions feels messy. Since I started wearing the LG G, I have accidentally emailed my mother, responded to a calendar invite (I have no idea how), and supposedly set my alarm, but perhaps disabled it when I muted the watch. (All very unclear.) I am sure there are some fancy user settings in the works, but there’s just not much to work with yet.

That said, when I’m not taking any action, the watch is great. That is of course what makes Google Now so useful, and its integration into the LG G is unsurprisingly pretty great.

I also loved having the weather widget first thing when I wake up. This was an idea I had toyed around with earlier this year for iOS , so it’s neat to see it enabled on the LG G.

These apps work well on the LG G because I don’t have to do anything: the information is just there when I need it. The watch works best when you do nothing, and the apps do the work for you.

That means the watch’s usefulness is dependent on the apps it syncs with, which is currently limited to Google Now, Pinterest, Lyft, Gmail, and a handful of others. For now, most of these currently leverage the watch as a glorified wearable notifications stream; this isn’t terribly interesting yet, but the platform will likely become more dynamic as more apps start building highly contextual use cases around it.

Future state: Moving forward

1. Designing for Android Wear will require a thoughtful, minimalist mentality.

At Google I/O, many of the presenters talked about “glanceability:” wearables should be “the rearview mirror” to your current experience, not the entire windshield. (Real-time, in the moment life is considered to be the windshield.)

This is a nice thought, but we should also talk about interruptability, because more screens inevitably means more room for distractions. If the average Android user checks their Android phone on average 125x every day, how many times should they be checking their Android wearable, and for what? What is worth taking our eyes off the road for?

As designers and developers, this is an opportunity to really hone in on your product’s core functionality and unit of success, and be honest about what’s important to the user. What is the single CTA your users go to you for? With such limited real estate, designing for Android wear requires discipline, and commitment: you can only afford to give the user the most important information at any time.

You can see how Google’s Material Design “FAB” (Floating Action Button) becomes a set of training wheels for designers and developers to focus on that one core thing, too.

The option to “open on phone” (and I imagine eventually desktop and tablet) will no doubt relieve some of the pressure to jam too much information or action on a single screen, but it shouldn’t be used as a crutch either. Wearable experiences should remain very, very simple and be deeply rooted and aware of context, relevance, & personalization in delivering that one core thing.

2. Social etiquette should be considered and explored.

A watch that lights up and vibrates can be a little rude. I went out for drinks to catch up with a friend last night. The bar was dark and my wrist glowed every few minutes, whenever an email came in. This was particularly noticeable since I’m fairly expressive and often talk with my hands. If wearables are meant to enhance the real world experience, then screen illumination, notifications types and alerts: all of these need to be considered in real world environments, for any time of day, at any place.

If you’re designing for Android Wear, think about the user’s context, but also about their company.

Related: Voice-enabled actions are clever. The thing is, talking to yourself in public is still awkward. I’m sure we’ll get over it, but we’re just not there yet. If you can design a voice-enabled feature that’s unobtrusive, go forth! But remember the potential awkwardness at stake.

3. Think holistically across devices and towards experiences.

Being a designer or developer today can sometimes feel like being a kid in a candy shop: it’s exciting to think about the kinds of products you can create today, and the tools and resources are gleefully abundant.

But as you start designing and building new products, it’s also a good idea to take a step back and get a birds eye-view of the landscape, across devices and experiences. How will your products live on every device? How will you design consistent experiences? (Not just apps, but experiences.) When is which part of the system important, and on what screen?

Understanding how your product could work holistically across experiences will also change what “growth” and “success” metrics look like for your product, so it’s worth reconsidering those, too. What will engagement look like? The DAU? Does it make sense to measure a particular action by device, or holistically across all a suite of them?

These are admittedly big questions: we are still in the very early phases of wearable design. But it’s exciting to think about where we’ll go as we attempt to answer them. So far, from where I stand, the outlook is promising.