<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Mobile on Phosphor BBS</title>
		<link>https://phosphorbbs.net/tags/mobile/</link>
		<description>Recent content in Mobile on Phosphor BBS</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://phosphorbbs.net/tags/mobile/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Five Bugs in One Morning: Debugging the Phosphor iOS Client</title>
				<link>https://phosphorbbs.net/blog/five-bugs-in-one-morning-debugging-the-phosphor-ios-client/</link>
				<pubDate>Fri, 04 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://phosphorbbs.net/blog/five-bugs-in-one-morning-debugging-the-phosphor-ios-client/</guid>
				<description>&lt;p&gt;The &lt;a href=&#34;https://phosphorbbs.net/blog/a-qr-code-on-a-text-screen-pairing-phones-to-a-bbs-without-a-login&#34;&gt;QR pairing post&lt;/a&gt; ended with a working native iOS client for Phosphor BBS. What it didn&amp;rsquo;t cover is what happened next: the app crashed randomly, the keyboard never appeared, and the whole UI rendered in a sad little window in the middle third of the screen. One morning of debugging later, every bug had a root cause, and every root cause was a lesson worth writing down.&lt;/p&gt;&#xA;&lt;p&gt;This is a war story. Five bugs, five root causes, and the one thread that ties them together: &lt;strong&gt;things that pass every test and still fail on real hardware.&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>A QR Code on a Text Screen: Pairing Phones to a BBS Without a Login</title>
				<link>https://phosphorbbs.net/blog/a-qr-code-on-a-text-screen-pairing-phones-to-a-bbs-without-a-login/</link>
				<pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate>
				<guid>https://phosphorbbs.net/blog/a-qr-code-on-a-text-screen-pairing-phones-to-a-bbs-without-a-login/</guid>
				<description>&lt;p&gt;There&amp;rsquo;s a moment in every mobile-client story where the design gets embarrassing. Your BBS just grew a beautiful native iOS app — SwiftUI, an embedded terminal, SSH, the works. And then someone asks the question that matters: &lt;em&gt;how does the phone prove it&amp;rsquo;s you?&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;The boring answer is a login form on a touchscreen. Type your username. Type your password. Maybe paste a token. On a touch keyboard. For a terminal system whose whole identity is that it never needed a GUI.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Your BBS in Your Pocket: Push Notifications and the Mobile-Ready Phosphor</title>
				<link>https://phosphorbbs.net/blog/your-bbs-in-your-pocket-push-notifications-and-the-mobile-ready-phosphor/</link>
				<pubDate>Sat, 29 Aug 2026 00:00:00 +0000</pubDate>
				<guid>https://phosphorbbs.net/blog/your-bbs-in-your-pocket-push-notifications-and-the-mobile-ready-phosphor/</guid>
				<description>&lt;p&gt;The old argument against BBSes — and self-hosted community servers generally — used to be simple: &lt;em&gt;they&amp;rsquo;re not where you are.&lt;/em&gt; A terminal lives on a desk. Your community lives on your phone, in your pocket, buzzing you when something happens. We fixed that. Phosphor BBS is now mobile-ready in the way that matters: it can reach out and grab you when your community needs you, and put you back exactly where you were when you answer.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
