<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>iPhone — FTWynn Thoughts</title>
    <link>https://ftwynn.writeas.com/tag:iPhone</link>
    <description>A space for me to write about things. Probably tech and people. But also maybe not.</description>
    <pubDate>Sun, 22 Nov 2026 20:58:47 +0000</pubDate>
    <item>
      <title>MagSafe on iPhone is Wonderful and Should be a Wider Standard</title>
      <link>https://ftwynn.writeas.com/magsafe-on-iphone-is-wonderful-and-should-be-a-wider-standard?pk_campaign=rss-feed</link>
      <description>When I was first stranded across the country due to COVID, I was sadly without my sunrise alarm clock (which I will probably use forever ...</description>
      <content:encoded><![CDATA[<p>When I was first stranded across the country due to COVID, I was sadly without my sunrise alarm clock (which I will probably use forever at this point). The closest thing I could get without buying a whole new clock was the Pixel Stand, which gave the Pixel a sunrise alarm along with it.</p>

<p>The alarm itself was a little finicky, but it took actually putting the device on and off the charger for me to appreciate how nice wireless charging is.</p>

<p>That said... the positioning on the Pixel Stand was always finicky and annoying. My in laws had a different third party wireless charge for their phones, and while it was easier to target, it certainly never felt like I put it in the “perfect” spot.</p>

<p>Switching to iPhone introduces... MagSafe. Finally a nice, clean feedback mechanism for correct positioning in wireless charging. This should be a standard, and it&#39;s practically a crime it isn&#39;t implemented in all phones.</p>

<p>The gentle tug to get in line. The snug confirmation you&#39;re in the right spot. The moderate but not too much effort it takes to pull off. It&#39;s all wonderful, and I very much do not want to go back to being without it.</p>

<p>Shame on Apple for hoarding this one for themselves. Make the world a better place and make the phone version of MagSafe something everyone can have, regardless of phone model.</p>

<p><a href="https://ftwynn.writeas.com/tag:iPhone" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">iPhone</span></a></p>
]]></content:encoded>
      <guid>https://ftwynn.writeas.com/magsafe-on-iphone-is-wonderful-and-should-be-a-wider-standard</guid>
      <pubDate>Sun, 20 Jun 2021 05:04:00 +0000</pubDate>
    </item>
    <item>
      <title>Hidden UI Elements are Bad</title>
      <link>https://ftwynn.writeas.com/hidden-ui-elements-are-bad?pk_campaign=rss-feed</link>
      <description>I would like to start by saying that minimal design is a good thing. Clutter is objectively bad, and it takes a lot of really difficult w...</description>
      <content:encoded><![CDATA[<p>I would like to start by saying that minimal design is a good thing. Clutter is objectively bad, and it takes a lot of <em>really difficult</em> work to cram a lot of capability into a smaller and smaller UI surface. I am completely acknowledging that.</p>

<p>That said, some gestures on the iPhone can go screw themselves.</p>

<p>In particular, whoever decided that <code>swipe up from the bottom but not too much</code> was a good idea should be publicly shamed.</p>

<p>Again, I understand the need to fit more functionality into a less space. If they break down the swipe up gesture into <code>a little</code> and <code>a lot</code> variants, you get two functions for the price of one. It makes sense... <em>on paper</em>.</p>

<p>But in reality? When I&#39;m switching phones and trying to figure out what the distances are on all these swipes? It&#39;s really terrible.</p>

<p>On top of that, the animation for <code>close an app</code> looks <em>awfully similar</em> to the end of the animation for <code>dismiss the app carousel</code>. Given that they both use the same overloaded swipe up gesture it&#39;s just... incredibly uncomfortable not knowing what happens when I stutteringly swipe up, which happens from time to time on the big phone screen.</p>

<p>I wish they took Android&#39;s cue for the three buttons at the bottom. Then I would know when I&#39;m summoning the carousel, and when I&#39;m not. Calling in a HUD also gives you a lot more options to make features visible when needed, rather than overloading a fixed set of UI options.</p>

<p>I know Android implemented a similar semi-swipe up an OS update or two ago, but I immediately found a way to get the buttons back. No such luck for customization on Apple.</p>

<p>Apple keeps trimming UI elements to the point where functionality is now <em>ambiguously hidden</em> instead of just <em>out of the way</em>. To me, that seems like a bad line to cross.</p>

<p><a href="https://ftwynn.writeas.com/tag:iPhone" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">iPhone</span></a></p>
]]></content:encoded>
      <guid>https://ftwynn.writeas.com/hidden-ui-elements-are-bad</guid>
      <pubDate>Thu, 17 Jun 2021 17:31:02 +0000</pubDate>
    </item>
    <item>
      <title>Back to iPhone After 12 Years</title>
      <link>https://ftwynn.writeas.com/back-to-iphone-after-12-years?pk_campaign=rss-feed</link>
      <description>This past Memorial Day weekend I woke up to my own Groundhog Day-style disappointment. My Pixel 4 XL&#39;s battery had stopped holding a char...</description>
      <content:encoded><![CDATA[<p>This past Memorial Day weekend I woke up to my own Groundhog Day-style disappointment. My Pixel 4 XL&#39;s battery had stopped holding a charge... <em>again</em>... on a third device.</p>

<p>Working in technology, I&#39;m used to having things break. I&#39;ve also been a big Android user since the release of the <a href="https://en.wikipedia.org/wiki/Motorola_Droid" rel="nofollow ugc">Motorola Droid</a>, sticking with the OS through a fair share of warts and growing pains. But when my phone broke last week in the same way as my other two Pixel devices, causing a Monday morning scramble to the store, I decided maybe it was time to be less of a tinkerer and more of a user again.</p>

<p>... at least when it comes to phones.</p>

<p>To help get used to the publishing flow on my blog, I&#39;m going to note some of my thoughts here for others to chew on (and spit at) if they&#39;re so inclined. I&#39;ll admit upfront I did fairly minimal homework, thinking my years at big tech companies and affinity for tinkering would get me through any adjustment pains.</p>

<p>Some things have been smooth. Some have been choppy. Some are mystifyingly difficult. It reminds me a lot of when I had a Mac laptop actually.</p>

<p>As a general rule, a few weeks in now, I can feel the stability I traded for. I&#39;m still frustrated by some limitations, but I think it&#39;s been the right call so far.</p>

<p>I just have to come to terms with the fact that I&#39;m now just a user... and be OK with that.</p>

<p><a href="https://ftwynn.writeas.com/tag:iPhone" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">iPhone</span></a></p>
]]></content:encoded>
      <guid>https://ftwynn.writeas.com/back-to-iphone-after-12-years</guid>
      <pubDate>Mon, 07 Jun 2021 02:53:36 +0000</pubDate>
    </item>
  </channel>
</rss>