<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Andrew Paier on Medium]]></title>
        <description><![CDATA[Stories by Andrew Paier on Medium]]></description>
        <link>https://medium.com/@andrewpaier?source=rss-126c1fcaea44------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*zG5ecbeP7VKFeF60.</url>
            <title>Stories by Andrew Paier on Medium</title>
            <link>https://medium.com/@andrewpaier?source=rss-126c1fcaea44------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 15 Nov 2026 23:10:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@andrewpaier/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[A Morning Surprise]]></title>
            <link>https://medium.com/@andrewpaier/a-morning-surprise-918dee20f164?source=rss-126c1fcaea44------2</link>
            <guid isPermaLink="false">https://medium.com/p/918dee20f164</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[frustration]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[apple-watch]]></category>
            <dc:creator><![CDATA[Andrew Paier]]></dc:creator>
            <pubDate>Tue, 26 Sep 2017 18:28:13 GMT</pubDate>
            <atom:updated>2017-09-26T18:28:13.729Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/442/1*bfrUaeMtkdH-BZlI7i5wIA.jpeg" /></figure><p>This is a quick post to try and highlight how seemingly unimportant UX changes can have significant impact on your end users. Sometimes to their detriment.</p><p>My whole life I’ve been a person who is generally late. I would go to bed late, wake up late, get to class late, etc. This is my fundamental nature.</p><p>As a responsible adult I quickly realized our household runs much better on a very regimented schedule. My part in making this run smoothly is being in charge of the waking of the family during week days. While this is certainly not my forte, I decided early on that waking the kiddos was my responsibility, not my wife’s.</p><p>I’ve come to rely strongly on my Apple Watch over the last 2+ years as my key dependency in this routine. It works as follows -</p><ul><li>5:50 am — first alarm goes off. Hit snooze.</li><li>5:59 am — alarm goes off again. Hit snooze. Warn wife we will be getting up in a few minutes</li><li>6:08 am — alarm goes off. Day starts</li></ul><p>Yesterday however our routine came crashing down. It was something along the lines of — 6:25 am look at watch through blurry eyes, have panic set in, scramble to get day going.</p><p>This threw off the entire family’s schedule, at least helping lead to one of the poorest morning launches for our family in the last year. I spent significant time apoligizing to my wife for messing up the alarm. I clearly must have hit cancel and not snooze, although I thought I was relatively well trained on this. We agreed to set a 6:15 “emergency” alarm to avoid future derailment of our mornings.</p><p>This morning my daughter crawled into bed at ~6am, and I realized that I hadn’t had my 1st snooze go off. Half asleep I programmed an alarm for 6:09 so that we would be sure to get up in time. When I awoke to that alarm, since I was fairly awake this is what I saw (ignore the time on the screen shot)-</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/476/1*u_mlmbaMPWujwqdH25FFxg.png" /></figure><p>Now for context that is the WatchOS 4 screen shot of an alarm going off. This is a screen shot of the same exact interface in WatchOS 3 —</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/342/1*kTeXtS5q5zT5lqoF6MC0DQ.png" /><figcaption>WatchOS 3 Alarm Screen</figcaption></figure><p>For those who can’t spot the difference, not only was the Snooze button relocated from the left hand side of the screen to the right, the color indicators were also changed so that the more colorful button is still on the left, just with the completely opposite functionality.</p><p>I honestly cannot believe I’m the only person that has been bit by this change. I also have difficulty understanding what designer decided that these 2 changes were warranted. It seems like a complete disconnect with anyone who relies on this for the primary use case — waking up.</p><p>I clearly won’t be getting rid of my Apple Watch over this minor change. I just wanted to highlight how lack of attention to detail and continuity can greatly impact the users of your tools. Now that I understand the change, I can adjust. But if it were not for my daughter’s accidental intervention, I might have abandoned using it to start my day.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=918dee20f164" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>