For the past 2 months, I've been on a mission: Figure out what it takes for the general public to get excited about smart glasses with today's hardware capabilities.
My approach: I prototyped smart glasses apps I wanted for my own daily use, then demoed them on Instagram to gauge enthusiasm and gather feedback. Beyond learning a ton about the art of building prototypes and content creation, I connected with incredible tech and design creators, founders, and leaders in music, media, and art.
★ The main thing I learned: Episodic use, not all-day wear, is where the adoption is right now.
Current hardware limitations and AI capabilities can’t yet give most people enough reason to change their personal style and become all-day glasses wearers. As a result, it's still less friction to pull out a phone for most use cases than to wait for glasses to turn on and connect. But for specific, time-bound activities where glasses augment the experience in a way the phone cannot (like hands-free videography), people will naturally tolerate that setup cost. These are the use cases I’m focused on building and productionizing.
Two more things stood out:
➤ Control still lives on the phone: Currently, photography is one of the most used glasses features partly because it’s triggered by an intuitive physical button. But to launch an app like Shazam, people still reach for their phone rather than invoke AI to start it. Until voice becomes a socially acceptable input method, reliable quick-action buttons or assignable gestures could make more use cases feel as accessible on glasses as the camera does.
➤ Aesthetics and comfort are critical prerequisites: Users strongly prefer not to compromise their personal style for a new device. Even for brief, episodic tasks, the glasses must feel comfortable to wear out in the real world.
Things are moving fast, so I'll keep updating my findings as I go. Curious what others building in this space are seeing as well.
My next step: Productionize some of the apps I've built. By getting them into the hands of users, I can test my hypotheses and gain more observable, real-world insights!
I left Google Android XR in June to build my own Smart Glasses Apps. Here are the 3 Most Important Principles I learned as a Senior Engineer that still drive success in my work (and life).
‣ 1. The 5 Whys (Find the Real Root Cause)
The most effective engineering leaders don't just solve problems; they solve the right problems the right way. By recursively asking "why" 5 times, I often found that a lot of technical problems stemmed from organizational causes. Both deep technical skill and organizational understanding were equally important in root-causing the problem, strategizing on a solution, and executing the fix.
‣ 2. The Eisenhower Matrix + Pareto Principle (Ruthless Prioritization)
Big tech is chaotic - Engineering leaders are pulled into so many directions and priorities, so I had to ruthlessly protect my focus. I needed to Decide: what are the 20% of things I should focus on now to deliver 80% of the impact (5 Whys help here), Delete and defer out everything else so they don’t distract me and my team, thoughtfully Delegate to others to grow them and their scope, and most importantly, make focus time for me to execute on the things I needed to Do myself.
‣ 3. Sender Responsibility (Own Your Message)
The best engineering leaders are attentive to the human element as much as the technical details. If my message didn’t land, I had to take responsibility for what I said and how I said it - it’s not them, it’s me. I learned to empathize with my audience to understand their incentives, their background, and their thought process (5 whys help here again), so that I could craft my message with the Clarity, Conciseness, and Courtesy they needed to believe in me and my direction.
These principles are all easier said than done, so I want to thank all my managers at Google for mentoring me and helping me put these principles into practice throughout my time on Android XR.