Episode Summary
Executive Summary: The episode centered on Apple’s iOS 10 and iPhone 7 lineup: revisiting home-button behavior, the utility and limits of AirPods and Lightning audio, iPhone 7 Plus camera tradeoffs, and the practical frustrations of Apple’s new defaults. The hosts debated design philosophy, accessibility settings, Bluetooth codec quality, and whether the Plus is worth its size. A long side argument over Messages effects and Reduced Motion became the show’s most heated—and comedic—exchange.
Main Topics: iOS 10 home-button and lock-screen behavior: The hosts discussed Apple’s new raise-to-wake and press-home-to-unlock flow, how it changes long-ingrained habits, and the accessibility setting that restores the old behavior. They also compared how different family members unlock their phones. Assistive Touch, home-button superstition, and regional habits: They explored reports that some users—especially in parts of Asia—use Assistive Touch to avoid pressing the home button, driven by superstition, resale concerns, and past hardware failures. Lightning audio and AirPods architecture: The group examined whether Lightning EarPods and the $9 Lightning adapter use digital audio with onboard DACs, concluding that Apple likely moved conversion into the accessory and that the practical sound difference is minimal for most users. AirPods controls and usability: They debated the absence of dedicated physical playback/volume controls on AirPods, whether Siri or taps can sufficiently replace them, and how Apple’s design prioritizes simplicity over tactile control. iPhone 7 Plus camera system and fusion processing: They discussed the dual-camera fusion approach, depth mapping, raw capture support, and the tradeoffs of the telephoto lens being slower and lacking stabilization, which may make the regular iPhone 7 more attractive than the Plus. Accessory and hardware design tradeoffs: The show also covered the new Apple battery case, metal buttons on leather cases, and the broader theme of Apple favoring sealed, non-moving hardware parts to improve reliability and water resistance. Messages effects vs Reduced Motion: A long, escalating debate focused on whether iOS should let users keep Reduced Motion enabled while still sending iMessage effects like lasers, balloons, and confetti. One host argued for a separate toggle; the others argued accessibility settings should remain blunt instruments.
Key Arguments: Apple’s new iOS 10 lock-screen flow is generally manageable, but it collides with deeply ingrained habits, so some users will prefer the old behavior restored via Accessibility settings. Home-button superstition and home-button avoidance may be widespread in some regions, which could influence Apple’s hardware and UI decisions. The Lightning-to-headphone adapter and Lightning EarPods likely contain their own DAC/amp, making Apple’s move to digital audio mostly a packaging and compatibility decision rather than a major sound-quality breakthrough. For most listeners, codec and DAC concerns are less important than headphone driver quality and connection stability; audio-file complaints are often overstated for typical consumer use. AirPods’ usability depends heavily on software and Siri; lacking tactile volume and playback controls is a major drawback for some users, though a hidden setting can repurpose taps for play/pause. The iPhone 7 Plus’s telephoto camera is weaker in low light because of f/2.8 and no stabilization, so the regular iPhone 7 may be the better balance of size and camera quality for many people. Messages effects should not be fully blocked by Reduced Motion because some users treat that setting as a preference, not a necessity, and should be able to opt into effects separately. Accessibility settings are blunt tools meant for broad needs, but hidden UI failures should still explain why an effect cannot be sent instead of silently failing.
Data Points: Mac Pro update gap: 1000 days - Opening joke about how long it had been since the Mac Pro was updated. Alternative Mac Pro span: ~1100 days - If the 2012 Mac Pro is treated as a continuation of the 2010 model. AirPods/Lightning adapter price: $9 - Discussing the Lightning headphone adapter and its embedded DAC/amp. Smart battery case capacity (iPhone 7): 2,365 mAh - Compared with the previous iPhone 6/6s battery case. Previous smart battery case capacity: 1,877 mAh - Referenced as the older case’s capacity. Linode plan price: $10/month - Sponsor read describing the entry-level VPS plan. Linode performance claim: 300% performance increase - Claimed benchmark improvement after switching from Xen to KVM. Linode credit: $10 - Promo code incentive for listeners. iPhone 7 Plus memory: 3 GB - Discussed as likely supporting dual-camera fusion processing. Telephoto aperture: f/2.8 - Used to explain poorer low-light performance of the iPhone 7 Plus telephoto lens. Wide camera aperture: f/1.8 - Compared with the telephoto lens on the iPhone 7 Plus. Depth layers for portrait effect: 9 layers - BuzzFeed/Apple discussion of depth mapping for simulated shallow depth-of-field. iPhone camera raw support: 6S and newer - RAW capture in iOS 10 for devices with 12-megapixel cameras. Wireless headphone code names: W1 chip - Apple’s custom Bluetooth pairing/connection chip for AirPods.
Pivotal Quotes: "“this is the longest span by a good margin. Yay! Happy birthday, Mac Pro, or something.”" — John Siracusa: Opening joke about the long-delayed Mac Pro update cycle. "“There’s also a setting to change it back to the old behavior.”" — Casey Liss: Explaining that iOS 10’s home-button unlock behavior can be reverted in Accessibility settings. "“Do not use accessibility features to tweak the phone.”" — ATP tipster / quoted in discussion: Used as the counterargument against repurposing Reduced Motion just to keep sending iMessage effects.
Implications: Apple is pushing users toward software-defined interactions and sealed hardware, but that creates friction for entrenched habits and power users. Future devices may emphasize fewer moving parts, more automation, and more hidden system intelligence—while still leaving room for user-facing toggles and clearer explanations.