Episode Summary
Executive Summary: The episode spans APFS conversion concerns, conference food pricing, a live ATP show announcement at AltConf during WWDC, iPhone 8 Touch ID rumors, iPhone 7 haptic/home-button impressions, Overcast and Apple Watch feature updates, and a broader critique of app-store enforcement and platform power (using Uber as the example). It closes with an extended travel/vacation digression about London and Disney, contrasting “traveling” with “vacationing.”
Main Topics: APFS and file-system compression: They debate what happens if APFS conversion encounters HFS+ compressed files on Macs and whether APFS already transparently supports decompression. The core concern is whether in-place conversion can safely preserve compressed data without needing risky disk-space-consuming expansion. Conference food pricing and venue economics: A discussion of a $40/day boxed lunch at Moscone/GDC evolves into a broader explanation of why conference food is so expensive: exclusive vendor contracts, unions, and venue lock-in. They extrapolate to WWDC lunches and the sheer scale of the cost. ATP live show at AltConf during WWDC: The hosts announce a live ATP show at AltConf in San Jose during WWDC week, with low-cost tickets for capacity control and a plan to stream audio if connectivity allows. They frame it as a community-friendly alternative to self-booking a venue. iPhone 8 rumors: Touch ID on the back vs. under the screen: They analyze leaked parts suggesting Touch ID may move to the back of the phone, weighing ergonomics, case cutouts, aesthetics, and the possibility of in-screen fingerprint sensing. Both hosts are skeptical but open to adapting. Non-moving iPhone 7 home button and haptics: The hosts revisit the iPhone 7’s force/solid-state home button and conclude they’ve both fully adapted and now prefer it to the old mechanical button. They also praise the Taptic Engine’s broader system-wide haptic feedback. Overcast development: chapters, watch playback, and SmartSpeed: Marco explains a fix for M4A chapter handling, notes that MP3 chapters will be easier to create soon, and gives a detailed progress report on offline Apple Watch playback. He describes watch OS limitations, phone-side transcoding, SmartSpeed baking, and why voice boost remains hard. Platform enforcement and Uber’s misuse of private APIs: They discuss Uber’s alleged use of private APIs to read device identifiers and evade detection, then broaden into a larger argument about Apple’s leverage over major apps, selective enforcement, and why some companies get stern warnings instead of app-store bans.
Key Arguments: APFS conversion becomes much harder if it cannot transparently handle HFS+ compression, because expanding compressed files can require extra disk space that may not exist on a nearly full device. Conference and venue pricing can look absurd from the outside, but exclusivity agreements, union rules, and captive vendors often make these costs unavoidable once you are inside the venue ecosystem. The ATP live show at AltConf is designed as a practical community event: cheap tickets are mainly for attendance management, not revenue, and the show will also be released as the regular weekly episode. Back-of-phone Touch ID is technically and ergonomically plausible, but it is less ideal than front placement, especially for case users who dislike back cutouts and lint-collecting sensor craters. The solid-state iPhone 7 home button, initially disliked, now feels more natural than the old mechanical one because haptics train user expectation. Overcast’s Apple Watch playback required major engineering compromises because the watch has severe power, storage, bandwidth, and API limitations; the phone now transcodes files and bakes in SmartSpeed to make offline playback viable. Apple’s enforcement against private API abuse is uneven in practice because major platforms like Uber and Facebook have enough user demand to create a power standoff, whereas smaller developers do not. A company can technically detect private API abuse with review tooling and device-based simulations, but hiding intent is the key; obvious obfuscation makes violations much easier to prove intentional.
Data Points: WWDC live show timing: Monday, June 5, 5:00–7:00 p.m. - ATP live show at AltConf during WWDC week Live show ticket price: $5 - Capacity-management ticket for the AltConf ATP live recording GDC lunch price: $40/day - The boxed lunch example cited from Moscone/GDC Lunch contents: sandwich, chips, apple, cookie, water/soda - Description of the $40 boxed lunch Estimated WWDC lunch total: ~$1,000,000 - Rough estimate using $40/day, five days, and 5,000 attendees Episode schedule assumption: 5 days - Used in the WWDC lunch cost calculation Attendee estimate used in calculation: 5,000 attendees - Used to estimate total lunch spend Touch ID rumor location: back of phone below Apple logo - Discussion of leaked iPhone 8 parts and sensor placement Screen ratio speculation: 2:1 / 18:9 - Referenced as the kind of taller display Apple might adopt if it removes chin/forehead bezels Watch sync/transfer time: up to an hour - Transferring podcast files to Apple Watch can take a very long time without optimization Watch playback adoption: about 0.5% - Marco’s analytics for current Apple Watch playback usage Transcoding speed: ~110–112x real time - Raw sample processing on iPhone 7 when transcoding for watch playback Transcoding via audio graph: ~12x real time - Slower performance when using the audio graph instead of raw sample processing Raw podcast playlist example: 15 podcasts - Marco’s example of a plausible playlist size versus overly ambitious user expectations Build/deploy improvement on Series 2: about 20 seconds faster - Difference in development cycle time that convinced Marco to buy a Series 2 Apple Watch Apple Watch build cycle: ~45 seconds - Approximate build/run/debug loop time on older watch hardware Current watch file-player API: WKAudioFilePlayer - The API used in the currently shipping Overcast watch version before moving to AVAudioPlayer Apple Watch offline playback version: 3.1.2 - The version expected to ship the improved offline watch playback support Overcast chapter issue: M4A chapters fixed next version - Marco’s tweet follow-up about metadata parsing and chapter support
Pivotal Quotes: "max speed should be higher" — Marco: Complaint about Overcast’s long-list drag-and-scroll behavior "I am fully converted to the non-moving home button" — John: Revisiting the iPhone 7 solid-state home button after long-term use "If I did that in Overcast, I would be kicked out of the app store immediately" — John: Argument about Apple’s unequal treatment of major companies like Uber versus smaller developers
Implications: Listeners get a preview of how Apple’s next hardware and software changes may affect everyday use, while developers hear practical lessons about platform constraints, haptics, watch limitations, and the real-world cost of shipping niche features.