<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Martin Ma</title>
    <description>The latest articles on DEV Community by Martin Ma (@jumpingma).</description>
    <link>https://dev.to/jumpingma</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4191247%2F19d019e8-a8a3-4bd0-9788-2a9fd684838b.png</url>
      <title>DEV Community: Martin Ma</title>
      <link>https://dev.to/jumpingma</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jumpingma"/>
    <language>en</language>
    <item>
      <title>Designing friction instead of blocking: what I learned building a screen-time app</title>
      <dc:creator>Martin Ma</dc:creator>
      <pubDate>Sat, 17 Oct 2026 23:45:36 +0000</pubDate>
      <link>https://dev.to/jumpingma/designing-friction-instead-of-blocking-what-i-learned-building-a-screen-time-app-4fnc</link>
      <guid>https://dev.to/jumpingma/designing-friction-instead-of-blocking-what-i-learned-building-a-screen-time-app-4fnc</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhs3ma46t3b38ozisx9vp.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhs3ma46t3b38ozisx9vp.png" alt="ChoiceField — stop scrolling without locking yourself out. iOS 17+, free to start. QR: App Store (US)" width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;App Store: &lt;code&gt;https://apps.apple.com/us/app/id6769946195&lt;/code&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  The problem with every blocker I tried
&lt;/h2&gt;

&lt;p&gt;I've tried the usual stuff on my own phone: hard limits, one-tap locks, deleting apps. They all fail the same way. The block is absolute, so the fix is absolute too — you flip the switch off, and you're back to zero. Every attempt resets to the same starting line.&lt;/p&gt;

&lt;p&gt;My wife had the same pattern, worse: down at eleven, still awake at two, half of it short video and half of it shopping. So instead of another lock, I tried the opposite: keep access, add a small pause.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three rules we committed to
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Never make it impossible.&lt;/strong&gt; If the user can't get back in, they'll remove the app — and then there's no signal left to work with.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Make the exit visible.&lt;/strong&gt; Every bypass is counted and shown back to you. Hiding friction removes the feedback loop that changes behaviour.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Never go around the system.&lt;/strong&gt; No MDM profiles, no fake network tricks. Use the platform's own Screen Time stack.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What that looks like on iOS
&lt;/h2&gt;

&lt;p&gt;Under the hood it's the Screen Time APIs (Family Controls authorization, &lt;code&gt;DeviceActivity&lt;/code&gt; for monitoring, &lt;code&gt;ManagedSettings&lt;/code&gt; for shields). The interesting part isn't the API calls — it's the choices on top of them:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6bm2yr4a8yqcaz6ifu0p.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6bm2yr4a8yqcaz6ifu0p.jpg" alt="Per-app daily allowance, set once" width="800" height="1738"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Per-app allowance instead of one global limit.&lt;/strong&gt; A single 60-minute budget for the whole phone gets spent in ten minutes. Per-app budgets spread out.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A pause screen, not a wall.&lt;/strong&gt; When the allowance runs out you get a sentence and a way back in: wait a bit, or use one of a small number of unlocks you chose in advance.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Unlocks are logged, not blocked.&lt;/strong&gt; The point isn't prevention at all costs: it's seeing the pattern (three unlocks at 1am is information, not failure).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Friend Freeze.&lt;/strong&gt; A trusted person can freeze apps for you for a set window. Accountability without surveillance.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fd4rmugd30gz3i05g20go.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fd4rmugd30gz3i05g20go.jpg" alt="Setting a daily plan" width="800" height="1738"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What changed, measured
&lt;/h2&gt;

&lt;p&gt;Before: phone in hand until 2am, screen time after midnight ~50 minutes. After six weeks: down to about 20 minutes, and the useful part — it didn't feel like a fight. The unlock count went from 5–6 a night to 0–1.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzbad1j6tp8du9vca5nhr.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzbad1j6tp8du9vca5nhr.jpg" alt="Reviewing the week" width="800" height="1738"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  If you want to try it
&lt;/h2&gt;

&lt;p&gt;ChoiceField is free to start on iOS 17+. No account, everything on-device.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;https://apps.apple.com/us/app/id6769946195&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;If you're building something similar and want to compare notes on the Screen Time APIs — especially the entitlement review process — happy to share what we hit.&lt;/p&gt;

</description>
      <category>ios</category>
      <category>swiftui</category>
      <category>productivity</category>
      <category>design</category>
    </item>
  </channel>
</rss>
