Episode Summary
Executive Summary: The episode covers follow-up on Disney PhotoPass, a nuanced debate over cryptocurrency’s real use cases and risks, concern about Apple’s child-safety/CSAM system in the context of iCloud encryption, and a long critique of OnePassword 8’s move to Electron. The hosts also use the discussion to examine Apple’s fragmented UI framework strategy (AppKit, SwiftUI, Catalyst) and why cross-platform apps often degrade user experience.
Main Topics: Podcast housekeeping and follow-up corrections: The episode opens with a comedic recording mishap and then briefly revisits prior topics, correcting a mistake about Disney PhotoPass and clarifying a few technical details. Disney PhotoPass as a useful add-on for park trips: The hosts explain how Disney PhotoPass works, why it’s valuable for family trips, and why it complements—rather than replaces—bringing your own camera for candid photos. Crypto: legitimate use cases, but still high risk: The hosts respond to listener feedback by arguing that cryptocurrency can be useful in failed monetary systems, but remains volatile, technically demanding, environmentally costly, and risky for ordinary users. Apple child-safety/CSAM documents and the encryption question: They discuss Apple’s threat model document and interview with Craig Federighi, focusing on the tension between Apple’s current ability to access iCloud photos/backups and the possibility of future end-to-end encryption. OnePassword 8 beta and the move to Electron: A long critique of OnePassword 8’s Electron-based beta centers on usability regressions, platform non-native behavior, menu bar dependence, and the broader tradeoff between development velocity and user experience. Apple’s UI framework confusion: AppKit vs SwiftUI vs Catalyst: The discussion broadens into a critique of Apple’s unclear guidance on native Mac app development, arguing that multiple overlapping frameworks create uncertainty and push developers toward cross-platform compromises.
Key Arguments: Disney PhotoPass is worth the money because it captures family photos you otherwise miss and automatically syncs ride photos to your account. Cryptocurrency can be genuinely useful in countries with broken or collapsing fiat systems, but that does not make it a good general-purpose currency. Bitcoin/crypto are too volatile and too technically fragile to be safe for ordinary people to store significant wealth in. Apple’s CSAM design goals make sense in isolation, but they look contradictory if Apple already has access to iCloud photos and backups. If Apple ever makes iCloud photos/backups end-to-end encrypted, the CSAM system becomes a more serious surveillance vector and policy battleground. OnePassword’s Electron bet may improve development speed and cross-platform consistency, but it risks degrading the polished, native experience users valued. Apple’s lack of a clear “future of Mac UI” strategy leaves developers with three imperfect choices, which helps explain why some choose Electron instead of native frameworks. Cross-platform UI toolkits often save engineering effort by externalizing cost to users through slower apps, more memory use, and weaker platform conventions.
Data Points: PhotoPass cost: “a couple hundred bucks” - What the hosts recalled paying for Disney PhotoPass in late 2019 for a family trip. PhotoPass timeline: late 2019 - Referenced as the time they used Disney PhotoPass for their family trip. Photo uploads scanned by Facebook: 20 million photos - Correction from last week: the number was photos, not people. Bug bounty scale: “millions of dollars” - Used to describe large payouts that can attract more vulnerability hunters. OnePassword employees: 475 - Company size cited during discussion of OnePassword’s growth and direction. OnePassword revenue: $120 million - Referenced from a company newsletter / funding discussion. OnePassword first-round headcount: 174 employees - Compared with the current headcount to show growth over two years. OnePassword growth period: 2 years - Time between the first round and the later funding/growth figures. OnePassword funding: $100 million - Referenced as a new fundraising round for the company. Beta memory usage: about 135 MB at idle - Observed memory use for OnePassword 8 beta on the Mac. Podcast sponsor code: 10% off - Squarespace promotion in the ad read. Mac Weldon promo: 20% off first order - Advertising read for Mac Weldon. Linode credit: $100 in free credit - Offer for new Linode accounts in the ad read.
Pivotal Quotes: "If you want to make a native application, Mac application, how do I do it? The answer was AppKit, Coco. Period." — John: Argument that Apple needs a clearer native framework direction for developers. "The thing of it is, is that OnePassword, as I've said this before, I'll say it a few more times, was always, to use a grubrism, it was always a Mac-ass Mac app." — Casey: Why the OnePassword 8 Electron transition feels like a downgrade. "You don't want to use a thing whose value can be cut in half over the course of a couple of years." — Marco: Critique of Bitcoin’s volatility as a currency.
Implications: Listeners are left with a cautionary message: crypto is still too risky for most people, Apple’s privacy story may depend on future encryption choices, and cross-platform app strategies often sacrifice the polished feel users expect from native software.