[Valid Atom 1.0] This is a valid Atom 1.0 feed.


This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.


  1. <?xml version="1.0" encoding="utf-8"?>
  2. <feed xmlns="">
  3. <title>Daring Fireball</title>
  4. <subtitle>By John Gruber</subtitle>
  5. <link rel="alternate" type="text/html" href="" />
  6. <link rel="self" type="application/atom+xml" href="" />
  7. <id></id>
  10. <updated>2019-09-22T18:31:57Z</updated><rights>Copyright © 2019, John Gruber</rights><entry>
  11. <title>Instabug</title>
  12. <link rel="alternate" type="text/html" href=";utm_medium=nativeads&amp;utm_campaign=daringfireball-nativeads-newsfeedtitle-q319-september" />
  13. <link rel="shorturl" type="text/html" href="" />
  14. <link rel="related" type="text/html" href="" />
  15. <id>,2019:/linked//6.36057</id>
  16. <published>2019-09-22T00:40:00Z</published>
  17. <updated>2019-09-22T00:40:58Z</updated>
  18. <author>
  19. <name>John Gruber</name>
  20. <uri></uri>
  21. </author>
  22. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  23. <p>My thanks to Instabug for sponsoring DF this week. Instabug delivers Real-Time Contextual Insights throughout the entire mobile app lifecycle, helping mobile teams to connect with customers, accelerate their workflow, and release with confidence. With the best-in-class bug and feedback reporting, secure crash reporting, intuitive in-app surveys, and reliable infrastructure that supports over two billion devices worldwide, Instabug helps development and product teams easily collect bugs and feedback from beta testers and customers.</p>
  25. <p>Instabug helps you find out what your users really think through targeted in-app surveys that get higher response rates. Users can also request features and vote on which they need most. Mobile teams accelerate their workflows by seamlessly integrating with third-party tools like Github, Jira, Slack, Zendesk and much more. </p>
  27. <p>Join tens of thousands of companies like Lyft, eBay, and Verizon that rely on Instabug to iterate faster and enhance their app quality. Special deal just for DF readers: $150 “Instabug Credits”. Enter promo code “DF19” to claim your credits. <a href=";utm_medium=nativeads&amp;utm_campaign=daringfireball-nativeads-newsfeedcta-q319-september">Get started with Instabug now</a>.</p>
  29. <div>
  30. <a  title="Permanent link to ‘Instabug’"  href="">&nbsp;★&nbsp;</a>
  31. </div>
  33. ]]></content>
  34.  </entry><entry>
  35. <title>Nilay Patel’s Review of the iPhones 11 Pro</title>
  36. <link rel="alternate" type="text/html" href="" />
  37. <link rel="shorturl" type="text/html" href="" />
  38. <link rel="related" type="text/html" href="" />
  39. <id>,2019:/linked//6.36058</id>
  40. <published>2019-09-21T23:52:35Z</published>
  41. <updated>2019-09-21T23:52:37Z</updated>
  42. <author>
  43. <name>John Gruber</name>
  44. <uri></uri>
  45. </author>
  46. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  47. <p>Nilay Patel, writing at The Verge:</p>
  49. <blockquote>
  50.  <p>But after using an iPhone 11 Pro and iPhone 11 Pro Max for the
  51. past week, I think they’re more than the sum of several lightly
  52. updated parts. These are some of the most well-balanced, most
  53. capable phones Apple — or anyone — has ever made. They have
  54. excellent battery life, processors that should keep them relevant
  55. for years to come, absolutely beautiful displays, and a new camera
  56. system that generally outperforms every other phone, which should
  57. get even better with a promised software update later this fall.</p>
  59. <p>Yes, they’re expensive. And yes, I think most people should
  60. probably buy an iPhone 11, which has most of the same features,
  61. including the same basic camera system, for $300 less. But if you
  62. want to pay more to have the best display <em>and</em> the best camera,
  63. the iPhone 11 Pro is worth the premium over the iPhone 11.</p>
  64. </blockquote>
  66. <p>Glowing review overall, and some really interesting side-by-side photography tests pitting the 11 Pro against the Galaxy Note 10 Plus and last year’s iPhone XS and Google Pixel 3.</p>
  68. <p>It’s a matter of taste — and the Pixel 4 is coming next month — but I find iPhone 11’s Night Mode to be consistently more appealing, especially in color temperature, than the Pixel’s Night Sight.</p>
  70. <div>
  71. <a  title="Permanent link to ‘Nilay Patel’s Review of the iPhones 11 Pro’"  href="">&nbsp;★&nbsp;</a>
  72. </div>
  74. ]]></content>
  75.  </entry><entry>
  76. <title>‘The Fizz Was Gone’</title>
  77. <link rel="alternate" type="text/html" href="" />
  78. <link rel="shorturl" type="text/html" href="" />
  79. <link rel="related" type="text/html" href="" />
  80. <id>,2019:/linked//6.36056</id>
  81. <published>2019-09-21T20:30:20Z</published>
  82. <updated>2019-09-21T20:30:21Z</updated>
  83. <author>
  84. <name>John Gruber</name>
  85. <uri></uri>
  86. </author>
  87. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  88. <p>The Economist, last week:</p>
  90. <blockquote>
  91.  <p>Apple’s product launches are not what they used to be. A decade
  92. ago the unveiling of a new iPhone would inspire quasi-religious
  93. ecstasy; devotees would camp on pavements outside shops as the
  94. release date drew near. At the firm’s latest event, on September
  95. 10th, the format was the same: Apple’s boss stood on stage, clad
  96. in a regulation black jumper, and spoke of the world-changing
  97. power of the company’s latest wares. But the fizz was gone. The
  98. iPhone 11 looks like a merely incremental improvement on the
  99. models that have gone before it.</p>
  100. </blockquote>
  102. <p>One reason folks would camp out in the early years of iPhone is that you couldn’t pre-order them — if you wanted to buy one on day one your only choice was to wait in line at a retailer. But even now, years into the pre-order era when you can get a new iPhone delivered to your home on day one, thousands of people around the country line up for hours at Apple retail stores. And, yes, even <a href="">camp out the night before</a>. I stopped by the Philadelphia Apple Store last night around 7:30p and there were still <a href="">around 50 people queued up <em>outside the store</em> waiting to buy a new iPhone</a>.</p>
  104. <p>Fizz gone, indeed.</p>
  106. <div>
  107. <a  title="Permanent link to ‘‘The Fizz Was Gone’’"  href="">&nbsp;★&nbsp;</a>
  108. </div>
  110. ]]></content>
  111.  </entry><entry>
  112. <title>Drop-testing iPhone 11 and 11 Pro</title>
  113. <link rel="alternate" type="text/html" href="" />
  114. <link rel="shorturl" type="text/html" href="" />
  115. <link rel="related" type="text/html" href="" />
  116. <id>,2019:/linked//6.36055</id>
  117. <published>2019-09-21T18:22:52Z</published>
  118. <updated>2019-09-21T18:22:53Z</updated>
  119. <author>
  120. <name>John Gruber</name>
  121. <uri></uri>
  122. </author>
  123. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  124. <p>Lexy Savvides, CNet:</p>
  126. <blockquote>
  127.  <p>We decided to change things up with this year’s drop test. Our
  128. test zone was a concrete floor and to make the drops as consistent
  129. as possible, CNET Managing Producer Chris Parker built a system
  130. that helped each phone fall directly on the screen or on the back.
  131. While the drop machine didn’t guarantee the phones would land in
  132. the desired position every time, it did help us test in a
  133. controlled way.</p>
  134. </blockquote>
  136. <p>Impressive results. Similar impressive results in <a href="">this test from EverythingApplePro</a>.</p>
  138. <div>
  139. <a  title="Permanent link to ‘Drop-testing iPhone 11 and 11 Pro’"  href="">&nbsp;★&nbsp;</a>
  140. </div>
  142. ]]></content>
  143.  </entry><entry>
  144. <title>How to Use the New Text Tools in iOS and iPadOS 13</title>
  145. <link rel="alternate" type="text/html" href="" />
  146. <link rel="shorturl" type="text/html" href="" />
  147. <link rel="related" type="text/html" href="" />
  148. <id>,2019:/linked//6.36054</id>
  149. <published>2019-09-21T00:19:21Z</published>
  150. <updated>2019-09-21T00:29:28Z</updated>
  151. <author>
  152. <name>John Gruber</name>
  153. <uri></uri>
  154. </author>
  155. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  156. <p>Charlie Sorrel, writing for Cult of Mac:</p>
  158. <blockquote>
  159.  <p>For the last ten years, selecting and manipulating text has been a frustrating nightmare on the iPad. Try to select a couple of words in Safari, for instance — a package delivery tracking number, for instance — and the selection would bounce back and forth between a few characters, and the entire page.</p>
  161. <p>It was enough to drive you back to the comfort of the Mac’s mouse pointer.</p>
  163. <p>In iOS 13, though, this has all changed. Text selection is accurate and predictable. And the new copy/paste gesture shortcuts become second nature almost immediately.</p>
  164. </blockquote>
  166. <p>One more tip: With 3D Touch on pre-11 iPhones, you could not just move the insertion point by doing a hard-press-and-hold on the keyboard to turn it into a virtual trackpad, you could also select a range of text in this mode by hard pressing again while dragging. On iPhones 11 (and iPads), you can still get into text selection mode by tapping the keyboard area with another finger while in trackpad mode. This is nowhere near as elegant as 3D Touch, but it’s still a good trick to know. (This isn’t really new to iOS 13 — iPads have been doing this for years — but it’s new on iPhone for anyone accustomed to 3D Touch.)</p>
  168. <div>
  169. <a  title="Permanent link to ‘How to Use the New Text Tools in iOS and iPadOS 13’"  href="">&nbsp;★&nbsp;</a>
  170. </div>
  172. ]]></content>
  173.  </entry><entry>
  174. <title>Kotaku: ‘Apple Arcade Is Mobile Gaming Without All the Bullshit’</title>
  175. <link rel="alternate" type="text/html" href="" />
  176. <link rel="shorturl" type="text/html" href="" />
  177. <link rel="related" type="text/html" href="" />
  178. <id>,2019:/linked//6.36053</id>
  179. <published>2019-09-20T21:53:52Z</published>
  180. <updated>2019-09-21T03:23:10Z</updated>
  181. <author>
  182. <name>John Gruber</name>
  183. <uri></uri>
  184. </author>
  185. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  186. <p>Michael Fahey and Stephen Totilo, writing for Kotaku:</p>
  188. <blockquote>
  189.  <p>Entering into the busiest video game season of the year, we didn’t
  190. exactly need Apple Arcade, nor did we really want it, given
  191. Apple’s mediocre stewardship of video games for the past decade.
  192. What a shock, then, that Apple Arcade is one of the best gaming
  193. launches we can remember, and that we can recommend it without
  194. making any apologies or exceptions for the stuff no one likes
  195. about mobile games. This thing is great. […]</p>
  197. <p>There are, simply, none of the manipulative systems that have
  198. contaminated nearly all of mobile gaming. Just imagine playing a
  199. puzzle game and not having to wait an hour for a timer to tick
  200. down before you can play the next level. Imagine playing a
  201. strategy game where you aren’t offered the chance to pay more to
  202. speed up the suspiciously slow building times. Imagine not being
  203. screwed with while you play mobile games. What a concept!</p>
  204. </blockquote>
  206. <p>Sometimes a headline says it all.</p>
  208. <div>
  209. <a  title="Permanent link to ‘Kotaku: ‘Apple Arcade Is Mobile Gaming Without All the Bullshit’’"  href="">&nbsp;★&nbsp;</a>
  210. </div>
  212. ]]></content>
  213.  </entry><entry>
  215.    <link rel="alternate" type="text/html" href="" />
  216. <link rel="shorturl" href="" />
  217. <id>,2019://1.36052</id>
  218. <published>2019-09-20T06:27:57Z</published>
  219. <updated>2019-09-22T18:00:36Z</updated>
  220. <author>
  221. <name>John Gruber</name>
  222. <uri></uri>
  223. </author>
  224. <summary type="text">You asked, I’m answering.</summary>
  225. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  226. <p><a href="">You asked</a>, I’m answering.</p>
  228. <h2>iPhone 11 and 11 Pro</h2>
  230. <p><em>If I’m upgrading to an iPhone 11 this weekend, before iOS 13.1 comes out next week, do I need to upgrade my current iPhone to iOS 13.0 to do the new direct iPhone-to-iPhone data transfer when setting up a new iPhone?</em> </p>
  232. <p>No — iOS 12.4.1 fully supports this new feature, <a href="">which Apple calls Quick Start</a>. I recommend leaving your old phone on iOS 12.4.1. I tried Quick Start with my review units, and it worked great transferring data from my iPhone XS still running 12.4.1. And it’s a very cool feature.</p>
  234. <p><em>I’m upgrading to an iPhone 11 from an iPhone 6/7/8 — how long will it take to get used to the lack of a home button and Face ID?</em> </p>
  236. <p>Three days. Trust me.</p>
  238. <p><em>What’s the difference between Deep Fusion and Night Mode?</em> </p>
  240. <p>It’s pretty simple — Night Mode is for truly dark environments — under 10 lux. Deep Fusion — when it ships “later this year” (I’m guessing iOS 13.2) — is intended to improve photos in mid-level lighting, in the range of around 600-10 lux.</p>
  242. <p><em>What’s the deal with Night Mode and tripods?</em> </p>
  244. <p>If you mount any iPhone 11 on a tripod, after the phone notices (thanks to the gyroscope), Night Mode will, if needed, offer longer exposure times than it does when handheld. Handheld it seems to max out at 3 seconds. With a tripod I’ve seen it go up to 5 seconds, <a href="">but apparently it can go up to 30 seconds</a>.</p>
  246. <p><em>Any improvement with Face ID and sunglasses?</em> </p>
  248. <p>Face ID still doesn’t work with my <a href="">Ray-Bans with G-15 lenses</a>. (If you have sunglasses that don’t work with Face ID, you can turn off “Require Attention for Face ID” in Settings to allow Face ID to work while you’re wearing them — convenience at the expense of some security.)</p>
  250. <p><em>Which lens does Panorama Mode use?</em> </p>
  252. <p>Pano mode lets you choose from all three lenses (or two lenses on the regular 11) — very cool.</p>
  254. <p><em>Is the new SF Camera typeface exclusive to the new iPhone 11 phones?</em> </p>
  256. <p>Yes, the entire new Camera app UI is exclusive to the new phones — including the SF Camera font and the new QuickTake shutter button.</p>
  258. <p><em>Do the camera lenses protrude when using an Apple case?</em> </p>
  260. <p>No, as always with Apple’s first-party cases, the case is just thick enough that the lenses do not protrude.</p>
  262. <p><em>I take most photos with the volume button, and also take lots of bursts. Does QuickTake affect holding down the volume button?</em> </p>
  264. <p>Yes, the volume buttons work just like the on-screen shutter button — if you hold them down, you shoot a video, not a burst.</p>
  266. <p><em>Bummer. Follow-up: Is there a setting to make holding down the shutter shoot a burst instead of video?</em> </p>
  268. <p>No, there is no setting for this. There should be, though.</p>
  270. <p><em>Can you show the feature where you can edit a photo shot using the wide angle lens and it uses imagery captured outside the frame from the ultra-wide lens to allow you to rotate the photo a few degrees without cropping?</em> </p>
  272. <p>Sure, <a href="/misc/2019/09/captured-outside-frame-iphone-11.jpeg">here’s a screenshot</a>. The frame you see in that screenshot is the full size of the original image from the wide angle lens — everything you see outside that frame is from the ultra-wide. This feature can seem like magic with certain slightly crooked photos.</p>
  274. <p><em>Second camera lens on iPhone 11: upgrade, downgrade, or push vs. if it had been 2x instead of 0.5x?</em></p>
  276. <p>Good question. In other words, what would have been better for the regular iPhone 11 — the ultra-wide 0.5x lens that Apple did add, or a telephoto 2x lens like the second lenses on the iPhone X and XS? Obviously it depends what type of photos you shoot more. If you shoot a lot of landscapes, the ultra-wide is more useful. If you shoot a lot of portraits of people — using Portrait Mode or not — the telephoto lens is more useful. I think for <em>typical</em> users, though, the ultra-wide lens is a better choice.</p>
  278. <h2>Apple Watch Series 5</h2>
  280. <p><em>Is there any chance the always-on display feature will come to older Apple Watches?</em> </p>
  282. <p>Zero chance. The power efficiency comes from a new (hardware) display driver that supports variable refresh rates down to 1Hz (one update per second). Only Series 5 watches have this hardware.</p>
  284. <p><em>Does Theater Mode turn the display off completely even with always-on enabled?</em> </p>
  286. <p>Yes, Theater Mode works exactly the same as before — it turns the display completely off.</p>
  288. <p><em>Do any apps other than Workouts have support for the always-on display?</em> </p>
  290. <p>No, only Workouts. And third-party apps don’t have access to the APIs either.</p>
  292. <p><em>Does the screen stay on all night in Nightstand Mode?</em> </p>
  294. <p>No, Nightstand Mode seems to work the same — the display turns off for most of the night, and slowly comes back on as it nears the time when the watch thinks you want to wake up.</p>
  296. <p><em>If you go to sleep wearing your watch, does the screen stay on all night?</em> </p>
  298. <p>Yes — but in a dark room, the always-on display remains just bright enough to be legible, but it’s so dim that it doesn’t glow. It’s great for checking the time when you wake up in the middle of the night.</p>
  300. <p><em>Can people read my notifications in always-on low-power mode?</em> </p>
  302. <p>I mentioned this in <a href="">my review</a> but it’s worth emphasizing again: notifications do not appear on screen in low-power mode.</p>
  304. <p><em>With always-on, does the Apple Watch “smother it with your hand” gesture only ever return the screen to the 1 Hz dimmed view, unless you’re already in theater mode? Also, does turning the crown in either theater mode or low-power mode still slowly ramp up brightness?</em></p>
  306. <p>Yes and yes. The smother gesture (covering the entire watch display with your other hand) just dims the screen when always-on is enabled. And in both lower-power mode (dim) and theater more (display completely off), you can still rotate the crown slowly to slowly increase the brightness.</p>
  310.    ]]></content>
  311.  <title>★ iPhones 11 and Apple Watch Series 5 Q&amp;A</title></entry><entry>
  312. <title>Om Malik: ‘An Exclusive Look Inside Apple’s A13 Bionic Chip’</title>
  313. <link rel="alternate" type="text/html" href="" />
  314. <link rel="shorturl" type="text/html" href="" />
  315. <link rel="related" type="text/html" href="" />
  316. <id>,2019:/linked//6.36051</id>
  317. <published>2019-09-20T02:10:44Z</published>
  318. <updated>2019-09-20T02:14:47Z</updated>
  319. <author>
  320. <name>John Gruber</name>
  321. <uri></uri>
  322. </author>
  323. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  324. <p>Om Malik, writing for Wired:</p>
  326. <blockquote>
  327.  <p>The answer to that question clearly illustrates the inherent
  328. advantage of Apple owning the whole stack. To learn about how that
  329. vertical integration manifests itself in a chip like the A13
  330. Bionic, I sat down with Schiller and Anand Shimpi, who in a past
  331. life was an influential semiconductor- and systems-focused
  332. journalist who founded the website AnandTech. Shimpi is now part
  333. of Apple’s Platform Architecture team.</p>
  335. <p>The new A13 outpaces last year’s A12 handsomely, with a 20 percent
  336. performance gain across all of its main components: the six CPU
  337. cores, its graphics processor, and the neural engine. For an
  338. already high-performing chip to see such a significant boost is
  339. sort of like watching Usain Bolt beat himself in a sprint.</p>
  340. </blockquote>
  342. <p>Power efficiency and CPU / GPU performance are important, no question. But they’re not everything. I would never argue that Apple’s A-series chips are the main reason to use iPhones and iPads. If the tables were turned and it were Apple’s chips that were significantly slower and consumed more power, I’d still use and recommend iOS because of its user interface, apps, and overall experience. It’s the same reason I never considered switching away from the Mac during the latter years of the PowerPC era, when Intel-based PCs clearly had performance <em>and</em> performance-per-watt advantages.</p>
  344. <p>But the tables <em>aren’t</em> turned. Apple’s A-series chips <em>are</em> faster and more power efficient than anything available for Android. Can you imagine what Android enthusiasts would say if it were the other way around? They’d have a field day. Instead, they just pretend it isn’t an issue.</p>
  346. <p>How fast is the A13 CPU? <a href="">So fast that it beats <em>every</em> Mac available in Geekbench 5’s single-core benchmark</a>. Now think about how fast the A13X will be in the next iPad Pros.</p>
  348. <div>
  349. <a  title="Permanent link to ‘Om Malik: ‘An Exclusive Look Inside Apple’s A13 Bionic Chip’’"  href="">&nbsp;★&nbsp;</a>
  350. </div>
  352. ]]></content>
  353.  </entry><entry>
  354. <title>Joanna Stern’s Review of the iPhones 11</title>
  355. <link rel="alternate" type="text/html" href="" />
  356. <link rel="shorturl" type="text/html" href="" />
  357. <link rel="related" type="text/html" href="" />
  358. <id>,2019:/linked//6.36050</id>
  359. <published>2019-09-19T21:17:12Z</published>
  360. <updated>2019-09-19T21:17:14Z</updated>
  361. <author>
  362. <name>John Gruber</name>
  363. <uri></uri>
  364. </author>
  365. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  366. <p>Joanna Stern, writing for The Wall Street Journal:</p>
  368. <blockquote>
  369.  <p>In the scheme of iPhone upgrade history, the new iPhone 11, 11 Pro
  370. and 11 Pro Max sure seem boring. Same designs…but new colors!
  371. Cameras…but three of them! Glass…but stronger?! After a week of
  372. testing, I can tell you that’s mostly just smoke-and-mirrors
  373. marketing, except for one thing many of us have wanted all along:
  374. phones that are a bit heavier and thicker — but work when we damn
  375. well need them to. Yes, longer battery life.</p>
  376. </blockquote>
  378. <p>I love that her take is sort of the inverse of mine. She sees the much-longer battery life as the primary appeal, with the improved camera as a bonus. I see the camera as the primary appeal, with the longer battery life as a bonus.</p>
  380. <p>She also wrote a second review — “<a href="">An iPhone 11 Review for Owners of Aging iPhones</a>” — which is basically the same starting premise as Brian Chen’s bizarre review for The Times, except done right. Stern’s advice for owners of aging iPhones is accurate and useful.</p>
  382. <div>
  383. <a  title="Permanent link to ‘Joanna Stern’s Review of the iPhones 11’"  href="">&nbsp;★&nbsp;</a>
  384. </div>
  386. ]]></content>
  387.  </entry><entry>
  388. <title>Inside Apple’s Redesigned Fifth Avenue Flagship Store</title>
  389. <link rel="alternate" type="text/html" href="" />
  390. <link rel="shorturl" type="text/html" href="" />
  391. <link rel="related" type="text/html" href="" />
  392. <id>,2019:/linked//6.36049</id>
  393. <published>2019-09-19T21:02:31Z</published>
  394. <updated>2019-09-19T21:02:33Z</updated>
  395. <author>
  396. <name>John Gruber</name>
  397. <uri></uri>
  398. </author>
  399. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  400. <p>Lance Ulanoff, writing for Lifewire:</p>
  402. <blockquote>
  403.  <p>Apple’s business may be transforming from one driven almost
  404. entirely by a passionate devotion to beautiful hardware to one
  405. idolizing code and, especially, services, but the reimagined Apple
  406. Fifth Ave. flagship Store in Manhattan is a reminder that the
  407. physical still matters very much to the California-based company.</p>
  409. <p>The 13-year-old store, which sits at the base of Central Park and
  410. is instantly recognizable thanks to its iconic 32-foot glass cube
  411. with a suspended Apple logo inside of it, has undergone a massive,
  412. 2-year-long reinvention project that somehow maintains the core
  413. essence of what drew hundreds of people to the store to line up
  414. for their first iPhones more than a decade ago.</p>
  415. </blockquote>
  417. <p>Looks pretty cool — the skylights that double as benches on the plaza are clever.</p>
  419. <p>(As an aside, I think it’s wrong to frame Apple’s push into services as a transition. Apple has sort of sold that line to Wall Street, and I’ve seen several analysts buy it, but it’s just not true. Apple is as devoted to its hardware business as ever — the push into services is an <em>expansion</em>, not a transition.)</p>
  421. <div>
  422. <a  title="Permanent link to ‘Inside Apple’s Redesigned Fifth Avenue Flagship Store’"  href="">&nbsp;★&nbsp;</a>
  423. </div>
  425. ]]></content>
  426.  </entry><entry>
  427. <title>iOS 13.0 Is Buggy; Wait for 13.1</title>
  428. <link rel="alternate" type="text/html" href="" />
  429. <link rel="shorturl" type="text/html" href="" />
  430. <link rel="related" type="text/html" href="" />
  431. <id>,2019:/linked//6.36048</id>
  432. <published>2019-09-19T18:16:20Z</published>
  433. <updated>2019-09-20T03:42:59Z</updated>
  434. <author>
  435. <name>John Gruber</name>
  436. <uri></uri>
  437. </author>
  438. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  439. <p>Lauren Goode, writing for Wired:</p>
  441. <blockquote>
  442.  <p>iOS 13 holds a lot of promise. It introduces a Dark Mode,
  443. drastically overhauls the Photos app, includes a Street-View-like
  444. feature in Apple Maps, and officially introduces Apple Arcade, the
  445. new $5-per-month gaming portal.</p>
  447. <p>Something atypical for Apple is iOS 13’s notably buggy rollout.</p>
  448. </blockquote>
  450. <p>13.0 is really buggy — I’ve been using it on my iPhone 11 review units. I’d say don’t upgrade your iPhone to 13.0 — wait for 13.1. Which, according to Goode, may not be a long wait:</p>
  452. <blockquote>
  453.  <p>But if you can stand to wait five days, it might be worth it to
  454. wait for iOS 13.1, the next update to the iPhone’s OS that’s
  455. expected to drop on September 24, and should be more reliable.
  456. That’s when iPadOS, the retooled operating system for iPads, is
  457. coming out as well.</p>
  458. </blockquote>
  460. <p>This is news to me — Apple has previously said 13.1 would ship on September 30. I don’t know why they moved this up, but if they’re really shipping it on Tuesday, just five days from now, I don’t understand why they’re releasing 13.0 at all. The iPhones 11 already have it installed, of course. But for upgrades I don’t see why Apple is releasing it.</p>
  462. <p><strong>Update:</strong> The second footnote on <a href="">Apple’s iOS 13 features page</a> confirms that 13.1 is coming September 24.</p>
  464. <p><strong>Update 2:</strong> Best theory I’ve seen so far as to why Apple is going ahead with a wide 13.0 release instead of just waiting until next week for 13.1 — Apple Watch Series 5 requires iOS 13 on the iPhone it’s paired with. So people getting new watches tomorrow need to update their iPhone to iOS 13 tomorrow. This raises the question of why Apple didn’t delay the release of the Series 5 watches until iOS 13.1 was out.</p>
  466. <div>
  467. <a  title="Permanent link to ‘iOS 13.0 Is Buggy; Wait for 13.1’"  href="">&nbsp;★&nbsp;</a>
  468. </div>
  470. ]]></content>
  471.  </entry><entry>
  473.    <link rel="alternate" type="text/html" href="" />
  474. <link rel="shorturl" href="" />
  475. <id>,2019://1.36047</id>
  476. <published>2019-09-19T17:32:33Z</published>
  477. <updated>2019-09-20T01:53:18Z</updated>
  478. <author>
  479. <name>John Gruber</name>
  480. <uri></uri>
  481. </author>
  482. <summary type="text">The whole piece reads like Soviet propaganda, explaining why Soviet-built cars are just fine, they’re great even.</summary>
  483. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  484. <p><a href="">Brian X. Chen’s review of the iPhones 11</a> for The New York Times is bizarre:</p>
  486. <blockquote>
  487.  <p>So here’s what I ultimately suggest: You should definitely upgrade
  488. if your current device is at least five years old. The iPhone 11
  489. models are all a significant step up from those introduced in
  490. 2014. But for everyone else with smartphones from 2015 or later,
  491. there is no rush to buy. Instead, there is more mileage and value
  492. to be had out of the excellent smartphone you already own.</p>
  493. </blockquote>
  495. <p>It’s a fine idea to remind people that if they’re happy with their current phone, they should just keep using it. “Is this new phone really worth an upgrade?” is perhaps the most important question a review should help the reader answer. But Chen’s premise is to tell the reader not to even look at the new iPhones. And 2015? Really? If you bought a top of the line iPhone in 2015, that’s an iPhone 6S. That’s not excellent by any measure today. If you’re still using one that’s great, but it’s it severely outdated in every important regard: photography, performance, battery life. And if you bought a less-than-top of the line iPhone in 2015, it’s even worse.</p>
  497. <p>I look forward to Chen telling Android users to keep using 2015 phones, too. I see people every day raving about the performance of their Galaxy S6 and Google Nexus 6.</p>
  499. <blockquote>
  500.  <p>Photos taken with the iPhone 11 and 11 Pro looked crisp and clear,
  501. and their colors were accurate. But after I finished these tests,
  502. I looked back at my archived photos taken with an iPhone X.</p>
  504. <p>Those pictures, especially the ones shot with portrait mode, still
  505. looked impressive. Some of the low-light ones looked crummy in
  506. comparison with the ones taken by the iPhone 11s, but I wouldn’t
  507. recommend that you buy a new phone just to get better night
  508. photos. You could always just use flash.</p>
  509. </blockquote>
  511. <p>This is madness. <em>Just use flash?</em> The New York Times’s institutional crusade against big tech has brought us to this: their personal technology columnist is advising readers to use the flash rather than buy a new phone. I don’t think I’ve shot a single photo using the flash in three or four years — flash makes for terrible-looking photos <em>and</em> it hurts the eyes of the subjects. <a href="">As Nilay Patel quipped</a>, Chen’s advice here boils down to “You could upgrade your phone for better photos, or you could make all of your memories look like 2008 TMZ”.</p>
  513. <p>A mainstream technology columnist should be explaining to readers why they should <em>not</em> use flash, and how best to capture low-light photographs without it. “You could always just use flash” is technology malpractice.</p>
  515. <p>Chen:</p>
  517. <blockquote>
  518.  <p>All the iPhone 11 models have a new ultra-wide-angle lens in their
  519. cameras, which provides a wider field of view than traditional
  520. phone cameras. This makes them handy for shooting landscapes or
  521. large group gatherings. The iPhone X lacks the ultra-wide-angle
  522. lens, but its dual-lens camera is capable of shooting
  523. portrait-mode photos, which puts the picture’s main subject in
  524. sharp focus while softly blurring the background.</p>
  525. </blockquote>
  527. <p>This paragraph makes it obvious that Chen started with his conclusion — that you shouldn’t upgrade unless your phone is five years old — and wrote his review backwards from that conclusion. Think about the logic of this paragraph. It’s presented as a trade-off — the iPhone X doesn’t have an ultra-wide lens, but it does have portrait mode. But he’s comparing it to the iPhone 11 and 11 Pro, in what is ostensibly a review of the iPhones 11. The iPhone 11 and 11 Pro both have portrait mode too, and their portrait photos — particularly from the 11 Pro — are <em>way</em> better than those shot with the iPhone X. He might as well have written: <em>The iPhone X doesn’t have an ultra-wide lens, but, on the other hand, it does have a crappier version of the telephoto lens.</em></p>
  529. <blockquote>
  530.  <p>For those with younger iPhones, there are ways to get more mileage
  531. out of your current device. While the newest iPhones have superb
  532. battery life — several hours longer than the last generation — a
  533. fresh battery in your existing gadget costs only $50 to $70 and
  534. will greatly extend its life.</p>
  535. </blockquote>
  537. <p>So instead of better battery life you can spend a little money to get the same battery life as before. Again, if you can’t afford an iPhone 11, or if you just don’t care, it’s a great idea for a column to offer tips on how to get the most out of an older phone. But this is supposed to be a review of the new iPhones. The whole piece reads like Soviet propaganda, explaining why Soviet-built cars are just fine, they’re great even.</p>
  539. <p>The Times is treating the tech industry the way Pravda treated the West. Big tech deserves scrutiny — including Apple. But it’s starting to come across as a mindless dogmatic crusade.</p>
  543.    ]]></content>
  544.  <title>★ ‘You Could Always Just Use Flash’</title></entry><entry>
  545. <title>PR Honcho Steve Dowling Is Leaving Apple</title>
  546. <link rel="alternate" type="text/html" href="" />
  547. <link rel="shorturl" type="text/html" href="" />
  548. <link rel="related" type="text/html" href="" />
  549. <id>,2019:/linked//6.36046</id>
  550. <published>2019-09-18T19:58:42Z</published>
  551. <updated>2019-09-18T20:25:41Z</updated>
  552. <author>
  553. <name>John Gruber</name>
  554. <uri></uri>
  555. </author>
  556. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  557. <p>Steve Dowling, in a memo to staff (”leaked” to Recode):</p>
  559. <blockquote>
  560.  <p>After 16 years at Apple, countless keynotes, product launches and
  561. the occasional PR crisis, I’ve decided that the time is right for
  562. me to step away from our remarkable company. This is something
  563. that has been on my mind for a while, and it came into sharp
  564. focus during the latest — and for me, last — launch cycle. Your
  565. plans are set and the team is executing brilliantly as ever. So,
  566. it’s time.</p>
  568. <p>Phil will be managing the team on an interim basis starting today,
  569. and I’ll be available through the end of October to help with the
  570. transition. After that, I plan to take a good, long stretch of
  571. time off before trying something new. At home I have a supportive,
  572. patient spouse in Petra and two beautiful children blossoming into
  573. their teen years. I‘m looking forward to creating more memories
  574. with the three of them while I have the chance.</p>
  576. <p>My loyalty to Apple and its people knows no bounds. Working with
  577. Tim and this team, accomplishing all we have done together, has
  578. been the highlight of my career. I want to thank you for your hard
  579. work, your patience and your friendship. And I wish you every
  580. success.</p>
  582. <p>I will always bleed six colors.</p>
  584. <p>Dowling</p>
  585. </blockquote>
  587. <p>He’s going out on top. Dowling replaced the inimitable Katie Cotton five years ago, and it’s been a busy five years to say the least. I’ll just say it: I like Dowling. He’s been tremendously helpful to me — always available, always honest.</p>
  589. <p>When Cotton left, there were two clear possible successors, Dowling and Natalie Kerris. Cotton was very much Steve Jobs’s PR chief. She fit Jobs’s style like a glove. I think Dowling was a similar fit for Tim Cook. But there’s no clear successor to Dowling this time. Kara Swisher reports that Apple will be considering both internal and external candidates, and while it makes sense to look at everyone, Apple has such a unique culture, and is on such a good roll, that I’d be a little surprised if they go with an external candidate.</p>
  591. <div>
  592. <a  title="Permanent link to ‘PR Honcho Steve Dowling Is Leaving Apple’"  href="">&nbsp;★&nbsp;</a>
  593. </div>
  595. ]]></content>
  596.  </entry><entry>
  597. <title>Facebook Launches Portal TV, a $149 Video Chat Set-Top Box</title>
  598. <link rel="alternate" type="text/html" href="" />
  599. <link rel="shorturl" type="text/html" href="" />
  600. <link rel="related" type="text/html" href="" />
  601. <id>,2019:/linked//6.36045</id>
  602. <published>2019-09-18T17:32:45Z</published>
  603. <updated>2019-09-18T17:32:47Z</updated>
  604. <author>
  605. <name>John Gruber</name>
  606. <uri></uri>
  607. </author>
  608. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  609. <p>Josh Constine, writing for TechCrunch:</p>
  611. <blockquote>
  612.  <p>Facebook wants to take over your television with a clip-on camera
  613. for video calling, AR gaming and content co-watching. If you can
  614. get past the creepiness, the new Portal TV lets you hang out with
  615. friends on your home’s biggest screen.</p>
  616. </blockquote>
  618. <p>Imagine hearing “clip-on Facebook camera” and not running in the opposite direction.</p>
  620. <p>Also, their example footage is bullshit. There’s tiny small print stating that the footage is simulated, but they’re trying to pass off professional video camera footage as the work of this camera.</p>
  622. <div>
  623. <a  title="Permanent link to ‘Facebook Launches Portal TV, a $149 Video Chat Set-Top Box’"  href="">&nbsp;★&nbsp;</a>
  624. </div>
  626. ]]></content>
  627.  </entry><entry>
  629.    <link rel="alternate" type="text/html" href="" />
  630. <link rel="shorturl" href="" />
  631. <id>,2019://1.36044</id>
  632. <published>2019-09-18T10:03:40Z</published>
  633. <updated>2019-09-19T21:03:51Z</updated>
  634. <author>
  635. <name>John Gruber</name>
  636. <uri></uri>
  637. </author>
  638. <summary type="text">I’d have placed an order for a Series 5 watch even if Apple had put up a slide that said “Just one new feature: Always-on display.”</summary>
  639. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  640. <p>Deciding when to ship a new product is a balancing act. Ship too early and you’ll get off to a rocky start you might never recover from. (E.g. the Newton and the whole “<a href="">Eat up Martha</a>” / “<a href="">Egg Freckles</a>” handwriting recognition debacle.) Wait too long, though, and the world will pass you by.</p>
  642. <p>The original iPhone was a sensation, but it had several profound flaws: it was exclusive to one carrier in one country; its cellular networking was painfully slow; you needed to tether it to a Mac or PC to sync just about anything other than email; the new UI paradigm, brilliant though it was, was missing rudimentary features like copy and paste; etc. The original iPad was a bit more fully formed at its debut — owing largely to the fact that it was quite obviously an offshoot of the iPhone.</p>
  644. <p>The right time to ship a new product is when its utility and appeal outweigh its obvious flaws. The iPhone hit that mark. But then what do you do? You prioritize those obvious flaws, and start knocking them down, one by one.</p>
  646. <p>A new product really hits its stride when those obvious, glaring faults are mostly solved. For the iPhone that was probably the iPhone 4S. For the iPod, I’d say the finally-hit-its-stride marker was the <a href="">iPod Nano</a> in 2005, four years after the original iPod.</p>
  648. <p>Apple Watch, in hindsight, perhaps shipped a <em>little</em> too soon. The original models — “Series 0” — were slow, third-party apps were heavily promoted but profoundly unusable, and Apple wasn’t quite sure what the whole thing was meant for. Perhaps worst of all, it struggled to get through the day on a charge. But even in hindsight it’s a close call. Apple was under intense pressure from Wall Street, the media, and probably themselves to prove they could launch a great new product in the post-Jobs era.</p>
  650. <p>And then they did what Apple does: iterate, iterate, iterate. They started knocking down Apple Watch’s glaring flaws one by one. Battery life improved significantly. They identified what Apple Watch is meant for: health and fitness tracking, and notifications. They added optional cellular networking, so your watch could remain utterly useful while out of the range of your iPhone.</p>
  652. <p>The iPhone was a hit product before the iPhone 4S. The iPod was a hit before the Nano. And without question, the Apple Watch is already a massive hit — a mere four years in and it’s already <a href="">more successful than the iPod <em>ever</em> was</a>. When I talk about a product hitting its stride, I don’t mean that’s when it became popular — I mean that’s when the big missing pieces are mostly filled in.</p>
  654. <p>For me at least, Series 5 marks the Apple Watch hitting its stride.</p>
  656. <p>I spent an inordinate number of words in <a href="">my original Apple Watch review</a> complaining about the fact that the display was not always on. As a lifelong watch wearer, I just could not get used to it. Four years later, I’m still not used to it. Part of that is that I’ve never been, and likely never will be, a monogamous Apple Watch wearer. My collection of traditional watches is small, but the ones I own, I adore, and when I do wear one, it serves as a constant reminder that when I’m wearing my Apple Watch, I can’t always glance at it for the most basic purpose a watch serves: telling the goddamn time. </p>
  658. <p>And even if I were to wear my Apple Watch exclusively, there are too many scenarios in daily life where I glance at my wrist to check the time but can’t raise my wrist to wake the Apple Watch display. A common one: walking home carrying a full cup of coffee in each hand — one for me, one for my wife.</p>
  660. <p>Series 5’s always-on display solves my single biggest complaint about Apple Watch since day one. It’s not perfect, but it’s more than good enough. No other feature or improvement to Apple Watch to date has ever made me this happy. The watch face doesn’t really stay <em>on</em> on all the time — instead, when on previous Apple Watch generations the display would turn completely off, the watch face goes into a low-power mode. The display dims (but remains bright enough to be legible in most conditions), second hands go away, and you pretty much just see the hour and minutes. Raise your wrist and it fades in to full brightness. Notifications do not appear on screen while the watch is in its low-power state.</p>
  662. <p>The obvious reason why Series 0 through 4 didn’t offer an always-on display is battery life. I’ve been wearing a black stainless steel Series 5 since last Wednesday, on loan from Apple, and battery life has been more than fine. I even turn the brightness on my watch display to the maximum setting. If you charge it overnight you’ll have nothing to worry about. If, like me, you wear it to sleep, it takes a little over an hour to charge in the morning or at some other point during the day. There’s a setting to turn the always-on display off, which presumably will extend battery life, but I’ll never know because I wouldn’t want to spend a single day wearing this watch with the always-on display turned off.</p>
  664. <p>To me, the always-on display is the Apple Watch’s retina display moment — once you see it, you can’t go back.</p>
  666. <p>Series 5 brings other new features, but they’re mostly minor. There’s a compass now, and while it’s fun to play with, I don’t recall ever needing a compass in my entire life. It’s a huge boon to walking directions, though. (Apple did show me a clever feature of the compass, though. Traditional compasses spin randomly when you bring a magnet near them. Series 5’s compass won’t do this, because it uses the gyroscope to see if you’re actually moving. The compass won’t be fooled by a magnet because it can tell the watch itself isn’t spinning around. Smart.)</p>
  668. <p>I’d have placed an order for a Series 5 watch even if Apple had put up a slide that said “Just one new feature: Always-on display.”</p>
  672.    ]]></content>
  673.  <title>★ Apple Watch Series 5</title></entry><entry>
  674. <title>Panzarino: ‘The iPhone 11 Pro and iPhone 11 Do Disneyland After Dark’</title>
  675. <link rel="alternate" type="text/html" href="" />
  676. <link rel="shorturl" type="text/html" href="" />
  677. <link rel="related" type="text/html" href="" />
  678. <id>,2019:/linked//6.36043</id>
  679. <published>2019-09-17T21:47:38Z</published>
  680. <updated>2019-09-17T21:47:39Z</updated>
  681. <author>
  682. <name>John Gruber</name>
  683. <uri></uri>
  684. </author>
  685. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  686. <p>Matthew Panzarino:</p>
  688. <blockquote>
  689.  <p>As you’re probably now gathering, yes, I took the new iPhones to
  690. Disneyland again. If you’ve read my <a href="">other</a> <a href="">reviews</a> from the
  691. parks, you’ll know that I do this because they’re the ideal
  692. real-world test bed for a variety of capabilities. Lots of people
  693. vacation with iPhones.</p>
  695. <p>The parks are hot and the network is crushed. Your phone has to
  696. act as your ticket, your food ordering tool, your camera and your
  697. map. Not to mention your communication device with friends and
  698. family. It’s a demanding environment, plain and simple. And, I
  699. feel, a better organic test of how these devices fare than sitting
  700. them on a desk in an office and running benchmark tools until they
  701. go dead.</p>
  702. </blockquote>
  704. <p>A Disney park really is a great stress test for a phone — hard on the battery and so many photo and video opportunities.</p>
  706. <blockquote>
  707.  <p>Oh, about that improved Face ID angle — I saw, maybe, a
  708. sliiiiiiight improvement, if any. But not that much. A few
  709. degrees? Sometimes? Hard to say. I will be interested to see what
  710. other reviewers found. Maybe my face sucks.</p>
  711. </blockquote>
  713. <p>I tried testing this too, and couldn’t see how the Face ID angle or distance is any more generous on the iPhones 11. It might be faster, but in terms of angles I could see no difference.</p>
  715. <div>
  716. <a  title="Permanent link to ‘Panzarino: ‘The iPhone 11 Pro and iPhone 11 Do Disneyland After Dark’’"  href="">&nbsp;★&nbsp;</a>
  717. </div>
  719. ]]></content>
  720.  </entry><entry>
  721. <link rel="alternate" type="text/html" href=";utm_medium=nativeads&amp;utm_campaign=daringfireball-nativeads-newsfeedtitle-q319-september" />
  722. <link rel="shorturl" href="" />
  723. <link rel="related" type="text/html" href="" />
  724. <id>,2019:/feeds/sponsors//11.36042</id>
  725. <author><name>Daring Fireball Department of Commerce</name></author>
  726. <published>2019-09-17T16:59:12-04:00</published>
  727. <updated>2019-09-21T17:06:56-04:00</updated>
  728. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  729. <p>Instabug delivers Real-Time Contextual Insights throughout the entire mobile app lifecycle, helping mobile teams to connect with customers, accelerate their workflow, and release with confidence.</p>
  731. <p>With the best-in-class bug and feedback reporting, secure crash reporting, intuitive in-app surveys, and reliable infrastructure that supports over two billion devices worldwide, Instabug helps development and product teams easily collect bugs and feedback from beta testers and customers.</p>
  733. <p><a href=";utm_medium=nativeads&amp;utm_campaign=daringfireball-nativeads-midfeed-q319-september">Instabug</a> helps you find out what your users really think through targeted in-app surveys that get higher response rates. Users can also request features and vote on which they need most.</p>
  735. <p>Mobile teams accelerate their workflows by seamlessly integrating with third-party tools like Github, Jira, Slack, Zendesk and much more. </p>
  737. <p>Join tens of thousands of companies like Lyft, eBay, and Verizon that rely on Instabug to iterate faster and enhance their app quality.</p>
  739. <p>Special $150 “Instabug Credits” for DF readers. Enter promo code “DF19” to claim your credits. <a href=";utm_medium=nativeads&amp;utm_campaign=daringfireball-nativeads-newsfeedcta-q319-september">Get it now</a>.</p>
  741. <div>
  742. <a  title="Permanent link to ‘Instabug’"  href="">&nbsp;★&nbsp;</a>
  743. </div>
  745. ]]></content>
  746. <title>[Sponsor] Instabug</title></entry><entry>
  748.    <link rel="alternate" type="text/html" href="" />
  749. <link rel="shorturl" href="" />
  750. <id>,2019://1.36041</id>
  751. <published>2019-09-17T14:19:14Z</published>
  752. <updated>2019-09-22T18:31:57Z</updated>
  753. <author>
  754. <name>John Gruber</name>
  755. <uri></uri>
  756. </author>
  757. <summary type="text">It’s an impressive year-over-year camera improvement one year after an impressive year-over-year camera improvement.</summary>
  758. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  759. <p><a href="">A few weeks ago on my podcast</a>, speculating on the tentpole features for this year’s new iPhones, I said that “iCamera” would be a far more apt name than “iPhone”. MG Siegler, writing about Apple’s event last week, <a href="">had the same thought</a>:</p>
  761. <blockquote>
  762.  <p>The iPhone is now officially a camera. I mean, it has been a
  763. camera for a long time. The most popular camera in the world, as
  764. Apple is quick to point out each and every year, a decade on. But
  765. now it’s really a camera, as today’s keynote made clear. The key
  766. parts of the presentations for both the iPhone 11 and the iPhone
  767. 11 Pro were all about the camera. As Phil Schiller said in his
  768. portion: “I know what you’re waiting for, and I am too. Let’s talk
  769. about the cameras. Without question, my favorite part about
  770. iPhone.”</p>
  772. <p>It feels like if Apple wasn’t so wedded to their own legacy
  773. branding — more on that in a bit — they would rename this thing
  774. the iCamera.</p>
  775. </blockquote>
  777. <p>Apple’s not really going to do that, of course. But Apple spent the vast majority of the stage time for the iPhone 11 and iPhone 11 Pro talking about their cameras. They spent <em>no</em> time — not a word — talking about phone calls. It would have been weird if they did talk about phone calls. That’s probably the single biggest change in the landscape from 2007 to today. Back then, introducing the original iPhone, Steve Jobs spent a lot of time talking about phone calls and voicemail, and almost no time on the camera. It never ceases to amaze me that the original iPhone camera couldn’t even shoot video — at all — and within 10 years <a href="">Steven Soderbergh was using iPhones to shoot feature films</a>.</p>
  779. <p>Driven by the iPhone, the word <em>phone</em> has simply taken on a new definition — a pocket-sized touchscreen personal computer with wireless networking and one or more cameras. Try convincing a six-year-old that a landline telephone is a “phone” — they won’t believe you.</p>
  781. <p>If you want to know Apple’s top priority with the iPhones 11, just look at the back of the new iPhones. Remember when we thought the iPhone 6 camera bump was prominent? That it was something Apple <a href="">might be trying to hide</a> in marketing photos? With the iPhones 11, the camera system takes up an entire corner. It’s so large Apple had to move the Apple logo down to the center of the back. I’m not sure if it’s related to the lower position of the Apple logo, but for the first time, the iPhones 11 no longer say “iPhone”. The only two things on the back are the logo and a big camera system. They don’t have to rename it “iCamera” — these phones scream <strong>this is a camera</strong> just by looking at them. And if you insist upon judging Apple’s focus — no pun intended, I swear — for these new iPhones by what they talked about during last week’s event, <a href="">this 24-second highlight reel says it all</a>.</p>
  783. <p>I have been using an iPhone 11, iPhone 11 Pro, and iPhone 11 Pro Max since last Wednesday. Most of what I have to say — and I think most of what one needs to know to understand them — is about the cameras. My biggest problem is that I wrote this review last year. I re-read <a href="">my review of last year’s iPhones XS</a> (regular and Max) and at almost every single paragraph I found myself wanting to say the exact same thing again this year. Not that these phones are the same as last year’s phones, but that the year-over-year improvements are equally impressive and at times mind-boggling.</p>
  785. <p>Take this bit from last year’s XS review:</p>
  787. <blockquote>
  788.  <p>I’ve focused nearly the entirety of my testing on taking photos
  789. and videos side-by-side against my 10-month old iPhone X. Overall,
  790. I’m simply blown away by the iPhone XS’s results. Sometimes the
  791. difference is subtle but noticeable; sometimes the difference is
  792. between unusable and pretty good. The iPhone XS can capture still
  793. images and video that the iPhone X cannot.</p>
  794. </blockquote>
  796. <p>That’s exactly the case again, this time with the XS in the “last year’s phone” spot and the 11 Pro in the “this year’s phone” spot. It’s an impressive year-over-year camera improvement one year after an impressive year-over-year camera improvement.</p>
  798. <p>I’ll also crib this bit from last year’s XS review<sup id="fnr1-2019-09-17"><a href="#fn1-2019-09-17">1</a></sup>:</p>
  800. <blockquote>
  801.  <p>It’s worth emphasizing — as I do every year — that <em>normal
  802. people do not upgrade their phones after a single year</em>. Most
  803. don’t upgrade after two years. They upgrade when their old phone
  804. breaks or gets too slow. Anyone upgrading to the iPhone XS from an
  805. iPhone 7 or older is getting a great upgrade in dozens of ways,
  806. and the camera system is just one of them. I’ve concentrated on
  807. comparing the iPhone XS’s camera to the iPhone X’s for two
  808. reasons. First, even though most people don’t buy iPhones
  809. annually, Apple releases a new generation of iPhones annually, so
  810. that year-over-year comparison feels like the natural way to
  811. measure their progress. Second, a fair number of people <em>do</em>
  812. upgrade annually, or at least consider it (enough people that
  813. Apple deemed it worthwhile to create an <a href="">annual upgrade
  814. program</a>), and for the people who own an iPhone X who <em>are</em>
  815. considering an upgrade to the XS, to my mind, the camera system is
  816. the one and only reason to do it.</p>
  817. </blockquote>
  819. <p>Word for word, that holds up again this year, with one notable exception: there is a second reason iPhone XS owners might want to consider upgrading to an iPhone 11 or 11 Pro this year: battery life. It really is better. There’s my review of all three iPhone 11 models in a nut: the camera systems are remarkably improved year-over-year and battery life is noticeably longer.</p>
  821. <h2>Understanding the Relationship Between the iPhone 11 and 11 Pro</h2>
  823. <p>Just like last year with the XS and XS Max, the 11 Pro and 11 Pro Max are best thought of as two sizes of the same phone, pretty much like the two sizes of iPad Pro. Same A13 chip, same amount of RAM, exact same cameras. There are some minor software differences — the 11 Pro Max offers the choice between standard and zoomed display modes, whereas the 11 Pro offers only standard; on the Max, apps like Mail and Notes show their source lists of mailboxes/folders in an iPad-like two-column layout when the phone is in landscape orientation — but if you simply think of them as two sizes of the same phone, you won’t be wrong. I prefer the smaller 11 Pro size, and that’s the model I spent the most time with over the last six days. But henceforth in this review, when I write about the iPhone 11 Pro, I mean both the 11 Pro <em>and</em> the 11 Pro Max.</p>
  825. <p>Second, also just like last year with the XR and XS, the regular iPhone 11 and iPhone 11 Pro are <em>far</em> more alike than they are different. The regular iPhone 11 is so much less expensive that it seems like there ought to be a catch (or multiple catches), but there is no catch. The two primary differences are right there on the outside. On the front, the iPhone 11 has an LCD “Liquid Retina” display with @2x retina resolution; the iPhones 11 Pro have OLED “Super Retina XDR” displays with @3x retina resolution and slightly smaller bezels — the edges of the 11 Pro displays are a bit closer to the edges of the device. Flip them around and you can see the other primary difference: the regular iPhone 11 has a two-camera system (wide and ultra-wide lenses) and the 11 Pro models have three-camera systems (wide, ultra-wide, and telephoto).</p>
  827. <p>Apple claims the 11 Pro models can get faster LTE performance than the iPhone 11. I didn’t see anything notable running Speedtest here in Philadelphia, but I’m sure there are places where the 11 Pro gets faster LTE. And in my testing, the 11 Pro models scored about 5 percent higher than the regular iPhone 11 in the GeekBench 5 multi-threaded benchmark (single-threaded was equivalent). I ran the benchmarks five times and averaged the results, but that 5 percent difference could be within the margin for error. Bottom line, you can’t go wrong thinking that the only technical differences between the iPhone 11 and iPhone 11 Pro are the displays and the Pro’s  telephoto camera. The wide angle and ultra-wide angle cameras are exactly the same.</p>
  829. <p>Personally, I like that the bezels around the iPhone 11 Pro display are smaller, but even as a professional nit-picker I can’t say the slightly larger bezels around the iPhone 11 display are a big deal. As for the displays, my eyes simply aren’t good enough to see the difference in typical lighting conditions. Your mileage may vary on that front — my eyes are not great.</p>
  831. <p>Apple has to manage a delicate product marketing balance. At last week’s introduction event and in their advertising, they present the iPhone 11 and iPhone 11 Pro as two distinct phones. But putting aside the material differences — the 11’s aluminum vs. the 11 Pro’s stainless steel; the 11’s glossy back vs. the 11 Pro’s matte back — it really just comes down to the display technology and the 11 Pro’s telephoto camera.</p>
  833. <p>Here’s the pricing matrix:</p>
  835. <!-- Markdown Table
  836. |                    |  64 GB  |  128 GB  |  256 GB  |  512 GB  |
  837. |:-------------------|--------:|---------:|---------:|---------:|
  838. | iPhone 11 Pro Max  |  $1,100 |       -- |   $1,250 |   $1,450 |
  839. | iPhone 11 Pro      |   1,000 |       -- |    1,150 |    1,350 |
  840. | iPhone 11          |     700 |      750 |      850 |       -- |
  841. |                    |         |          |          |          |
  842. | *Δ from 64 GB*     |         |    *$50* |   *$150* |   *$350* |
  843. -->
  845. <table>
  846. <thead>
  847. <tr>
  848.  <th align="left"></th>
  849.  <th align="right">64 GB</th>
  850.  <th align="right">128 GB</th>
  851.  <th align="right">256 GB</th>
  852.  <th align="right">512 GB</th>
  853. </tr>
  854. </thead>
  855. <tbody>
  856. <tr>
  857.  <td align="left">iPhone 11 Pro Max</td>
  858.  <td align="right">$1,100</td>
  859.  <td align="right">—</td>
  860.  <td align="right">$1,250</td>
  861.  <td align="right">$1,450</td>
  862. </tr>
  863. <tr>
  864.  <td align="left">iPhone 11 Pro</td>
  865.  <td align="right">1,000</td>
  866.  <td align="right">—</td>
  867.  <td align="right">1,150</td>
  868.  <td align="right">1,350</td>
  869. </tr>
  870. <tr>
  871.  <td align="left">iPhone 11</td>
  872.  <td align="right">700</td>
  873.  <td align="right">750</td>
  874.  <td align="right">850</td>
  875.  <td align="right">—</td>
  876. </tr>
  877. <tr>
  878.  <td align="left"></td>
  879.  <td align="right"></td>
  880.  <td align="right"></td>
  881.  <td align="right"></td>
  882.  <td align="right"></td>
  883. </tr>
  884. <tr>
  885.  <td align="left"><em>Δ from 64 GB</em></td>
  886.  <td align="right"></td>
  887.  <td align="right"><em>$50</em></td>
  888.  <td align="right"><em>$150</em></td>
  889.  <td align="right"><em>$350</em></td>
  890. </tr>
  891. </tbody>
  892. </table>
  894. <p>This year’s 11 Pro models are the same prices as last year’s XS models. The regular iPhone 11, however, is $50 cheaper at each storage capacity than the equivalent XR model last year. Thus, the price gap between the 11 and 11 Pro is $50 higher than the gap last year between XR and XS.</p>
  896. <p>Last year I called the iPhone XR the iPhone most people should buy. Its successor is the iPhone 11 and the same thing is <em>more</em> true this year than last, if only because the equivalent models are $50 cheaper. The iPhone 11 is the best phone for most people. And once again, to my mind, the sweet spot in the whole lineup is the 128 GB iPhone 11 — for $50 you get double the storage of the base model, and 128 GB is more than enough for typical users.</p>
  898. <h2>3D Touch Is Gone; Battery Life Is Better</h2>
  900. <p>These might seem like two unrelated items, but they’re not.</p>
  902. <p>3D Touch was introduced with the iPhone 6S. Every new iPhone after the 6S, with the exception of the SE, had 3D Touch — until the iPhone XR last year. Instead of 3D Touch, the XR offered “Haptic Touch”. Haptic Touch is like 3D Touch except it doesn’t really detect the force of your finger press. It seems to me the heuristic is more complicated than just a long press, but it’s more like a long press with a bit of pressure applied.</p>
  904. <p>3D Touch was a great idea, but it never really took off for a few reasons. First, it was undiscoverable — the iOS interface never indicated what objects could be 3D Touched. Haptic Touch isn’t much better in this regard. Second, it always seemed to me that 3D Touch should have been a shortcut for a long press, and <em>only</em> a shortcut for a long press — a way to perform a long press without having to wait for the “long” part. Third, with the iPhone 6, SE, and XR, there were iPhones that didn’t even have 3D Touch, and no iPad has ever had it. So neither Apple nor third-party developers could design interfaces that assumed 3D Touch was universally available. </p>
  906. <p>Imagine if only <em>some</em> iOS devices had touchscreens. If that were the case we’d see half-hearted, inconsistent support for multitouch across the system and in third-party apps. That’s what happened to 3D Touch.</p>
  908. <p>So the good news is that switching from 3D Touch to Haptic Touch — along with changes in iOS 13 (and its sibling, iPadOS 13) — makes the whole thing more consistent across all iOS/iPadOS devices. Most iPhone users upgrading from a 3D Touch iPhone to an iPhone 11 or 11 Pro won’t even notice that Haptic Touch and 3D Touch are different.</p>
  910. <p>The bad news is, Haptic Touch is a bit slower. With 3D Touch, when you pressed, the action was instantaneous. With Haptic Touch, because it’s sort of a long press with pressure, there’s a very brief pause before it fires. One shortcut I use all the time, every day, is the camera button on the lock screen. On the iPhone 11 models, it feels just a bit less responsive than on the XS I’m used to. When you upgrade to a new iPhone, even year-over-year, everything usually feels faster or at least the same. Not so with Haptic Touch. It’s just the slightest of delays — a wee bit of latency — but I notice it.</p>
  912. <p>There’s also a shortcut that not many people know about, but when you show it to them, their minds are blown: with 3D Touch iPhones, you can 3D Touch and hold <em>anywhere</em> on the keyboard (that is to say, keep your thumb or finger pressed on the keyboard) and the keyboard turns into a virtual trackpad for moving the insertion point around any text editing field, exactly like moving a mouse pointer. With non-3D Touch devices (including iPads), you can still do this, but you can’t press <em>anywhere</em> on the keyboard to initiate it — you have to press-and-hold on the spacebar. I picked up this shortcut years ago and it long ago became second nature to me. It took me a few days to get used to having to start by pressing on the space bar. It’s a small regression in the user experience.</p>
  914. <p>So why did Apple get rid of 3D Touch? As I wrote above, one reason is to bring a far more consistent experience across all iOS 13 devices. But another reason is that 3D Touch required an entire layer under the display. Removing the 3D Touch sensors freed up space that Apple could use for something else — and it seems as though they’ve put it to use by including bigger, higher capacity batteries. Apple has never advertised the capacity of iPhone batteries, and even off the record, they don’t want to talk about it. We’ll find out when iFixit does their teardowns later this week, but I’ll be very surprised if the iPhone 11 Pro batteries aren’t significantly bigger than their iPhone XS counterparts, and I suspect the biggest reason why is that 3D Touch is gone.</p>
  916. <p>This theory — that removing 3D Touch made room for bigger batteries — fits with Apple’s advertised battery life improvements. The regular iPhone 11 “only” gets 1 additional hour of battery life compared to the iPhone XR. (I put “only” in dick quotes there because the iPhone XR had the longest battery life of any iPhone ever made — a 1-hour improvement over the previous champ is not bad.) But the iPhone 11 Pro and Pro Max are advertised as getting 4 and 5 more hours of battery life than the XS and XS Max, respectively. With so much of the internals shared between the 11 and 11 Pro models, I just don’t see how only the Pro models could gain so much more battery life unless the batteries are bigger in the iPhones 11 Pro than they were in the iPhones XS.</p>
  918. <p>So to recap, here’s my theory. Last year’s iPhone XR didn’t have 3D Touch, so it had a bigger battery than it would have if it did, and that’s why it got noticeably better battery life than the XS models. The regular iPhone 11 gained one hour of additional battery life compared to the XR via various small efficiencies in the A13 chip and other components. The iPhone 11 Pro and Pro Max have bigger batteries than their XS counterparts, using the space freed up by omitting 3D Touch. They benefit from the same small efficiencies that give the regular iPhone 11 one additional hour of battery life, plus a few more hours from bigger batteries. (The new 11 Pros are also about 0.4mm thicker than the XS models, and about 10-18 grams heavier. The thickness is negligible, but they’re about 7-8 percent heavier. Good chance that’s all battery.)</p>
  920. <p>Again, I miss 3D Touch’s instantaneity, but this is a good trade-off for longer battery life.</p>
  922. <p>I haven’t run any sort of battery testing with these review units, but anecdotally, I definitely seem to get more battery life from the iPhone 11 Pro than I do with my iPhone XS. (According to Settings → Battery → Battery Health, my one-year-old, much-used iPhone XS’s maximum battery capacity is still 92 percent.)</p>
  924. <h2>Camera Performance</h2>
  926. <p>I keep mentioning that the iPhone 11 Pro has a three-camera system and the iPhone 11 a dual-camera system. And I’ll mention that again. But what’s essential to understand is that you don’t need to know that the iPhone 11 camera systems consist of two or three discrete cameras. From the user’s perspective, they look and feel like a single camera with multiple zoom levels.</p>
  928. <p>At times the seamlessness of this experience feels like magic.</p>
  930. <p>For example, when shooting video, you can zoom in and out while shooting, and when you cross the 1x and 2x zoom thresholds, the camera system will automatically switch lenses on the fly. So far as I can see, there is no discernable sign of this in the resulting video. So using the iPhone 11 Pro, you can start filming using the ultra-wide lens at 0.5x, then zoom in and when you reach 1x, the camera system will switch to the regular wide lens. Keep zooming in and when you reach 2x it will switch to the telephoto lens. There’s no hiccup in the footage, and no difference in lighting or color. This works for 720p and 1080p at frame rates up to 60 FPS, and for 4K at 24 and 30 FPS. The exception is 4K 60 FPS — when shooting 4K 60 FPS, once you start recording, you’re stuck with the lens you started with.</p>
  932. <p>Google garnered much deserved praise last year for the <a href="">Night Sight mode</a> on its Pixel phones. The iPhones 11 now offer a similar feature Apple is calling Night Mode. Nomenclaturally, this is a bit weird, because on Pixels, Night Sight is a separate mode, and on iPhone 11, Night Mode is not a separate mode — it’s a feature that kicks in automatically in extreme low light conditions — about 10 or fewer lux. (If you don’t want Night Mode, you can turn it off by tapping a button, much like you can manually control the flash.)</p>
  934. <p>When Night Mode is engaged, it simulates a long exposure of 1, 2, or 3 seconds. You hold the phone still and when it’s done, you get an image that effectively makes the camera seem like it can see in the dark. With traditional photography, handheld exposures of more than 1/30th of a second start to get blurry. You just can’t keep your hands still for that long. Two- or three-second exposures handheld just aren’t feasible in traditional photography. Night Mode, on the other hand, doesn’t require anything more than casually steady hands. It’s like being able to hold your hands as steady as a tripod.</p>
  936. <p>Some comparison shots, between an iPhone XS and iPhone 11 Pro with Night Mode. These photos were shot at Hop Sing Laundromat — Philadelphia’s finest North Korean cocktail bar — <em>lit by nothing but candlelight</em>. No editing was performed on any of the files, other than to allow Photos to export HEIC originals as JPEGs.</p>
  938. <p>iPhone XS (<a href="" rel="nozoom">original image file</a>):</p>
  940. <p><img
  941.    src=""
  942.    alt=""
  943.    width="600"
  944.  /></p>
  946. <p>iPhone 11 Pro (<a href="" rel="nozoom">original image file</a>):</p>
  948. <p><img
  949.    src=""
  950.    alt=""
  951.    width="600"
  952.  /></p>
  954. <p>iPhone XS (<a href="" rel="nozoom">original image file</a>):</p>
  956. <p><img
  957.    src=""
  958.    alt=""
  959.    width="600"
  960.  /></p>
  962. <p>iPhone 11 Pro (<a href="" rel="nozoom">original image file</a>):</p>
  964. <p><img
  965.    src=""
  966.    alt=""
  967.    width="600"
  968.  /></p>
  970. <p>Portrait mode on the iPhone 11 Pro now has two lens options: 1x and 2x, for the wide and telephoto lenses, respectively. When using Portrait Mode, you must snap to one of these focal lengths — there’s no way to pinch-to-zoom to something in between like 1.5x. The iPhone 11 Pro’s telephoto lens has an aperture of f/2.0; the telephoto lens on the XS (and X before it) was f/2.4. A lower number for the f-stop means a wider aperture, which means more light reaches the sensor, which means it works better in low light conditions. If you ever tried using Portrait Mode in dim lighting with an iPhone X or XS, you were probably disappointed. You can’t use Night Mode while in Portrait Mode, but the iPhone 11 Pro’s faster 2x lens allows you to take Portrait Mode shots that the iPhone XS can’t. Example:</p>
  972. <p>iPhone XS (<a href="" rel="nozoom">original image file</a>):</p>
  974. <p><img
  975.    src=""
  976.    alt=""
  977.    width="600"
  978.  /></p>
  980. <p>iPhone 11 Pro (<a href="" rel="nozoom">original image file</a>):</p>
  982. <p><img
  983.    src=""
  984.    alt=""
  985.    width="600"
  986.  /></p>
  988. <p>The iPhone 11 Pro’s Portrait Mode in low light is far from perfect — if you look closely, it loses the back of the rim of the cocktail glass. But the iPhone XS portrait shot of the same scene is unusable.</p>
  990. <p>Another bit of magic. There are two new options in Settings → Camera: “Photos Capture Outside the Frame” (off by default) and “Videos Capture Outside the Frame” (on by default). When these options are turned on, when you shoot with the 1x or 2x lenses (wide or telephoto), the Camera app will use the next widest lens to capture additional footage outside the frame of the lens you’re shooting with. In post, this allows you to rotate the photo or video — typically, to fix a crooked horizon — <em>without cropping</em>. This seems to be, unfortunately, a bit buggy in iOS 13.0, but when it works, it’s amazing. At some point when Apple has more confidence in this feature, I expect it to be on by default for both video and photos.</p>
  992. <p>Last examples — both taken with the iPhone 11 Pro in Portrait Mode. I’m finding Portrait Mode with the 1x focal length to be a lot of fun. The 2x lens is better for capturing a flattering photo of a person willing to pose for you, but the 1x lens is better for small objects and pets. This is Mochi. Mochi looks good in both of these shots, but I think the 1x shot works better. It’s more fun to get closer.</p>
  994. <p>iPhone 11 Pro Portrait Mode, 1x (<a href="" rel="nozoom">original image file</a>):</p>
  996. <p><img
  997.    src=""
  998.    alt=""
  999.    width="600"
  1000.  /></p>
  1002. <p>iPhone 11 Pro Portrait Mode, 2x (<a href="" rel="nozoom">original image file</a>):</p>
  1004. <p><img
  1005.    src=""
  1006.    alt=""
  1007.    width="600"
  1008.  /></p>
  1010. <p>A few other observations about the iPhone 11 and 11 Pro camera systems:</p>
  1012. <ul>
  1013. <li><p>Night Mode is not available for the ultra-wide 11 Pro lens — it <a href="">doesn’t have focus pixels</a> like the other two lenses do. Only the wide angle lens has 100 percent focus pixels, but the wide angle lens covers the entire area of the telephoto lens.</p></li>
  1014. <li><p>The ultra-wide lens is fantastic, though, for action video.</p></li>
  1015. <li><p>The ultra-wide lens is so insanely wide that I need to learn a new phone grip while shooting photos. I caught my finger in the frame several times while shooting ultra-wide photos. <a href="">Here’s a picture of me holding the phone in a way that feels very natural</a>, but which puts the middle knuckle of my middle finger in the lower left of the field of view of the ultra-wide lens.</p></li>
  1016. <li><p>The entire Camera app UI has been redone for the iPhone 11 and 11 Pro. Among a host of changes, square photography is no longer a separate mode, which never really made sense. Instead there’s a row of controls that slide out of the shutter button area, and one of these controls gives you three aspect ratio options for still photos: 1:1 (square), 4:3, and 16:9. When you choose 1:1 or 16:9, you can later re-crop the photo in editing to get the full 4:3 frame. These aspect ratios are non-destructive, for lack of a better word.</p>
  1018. <p>The iPhone 11 Camera app is very different, but I took to it right away. It feels less like an app and more like a camera. It’s just great software.</p></li>
  1019. <li><p>There are two ways to access this new row of options (including flash, timer, and live filters). There’s a chevron button at the top of the iPhone display; tap it to hide/show the option buttons. What I find myself doing, though, is just sliding the controls out from the shutter area, sort of like pulling Control Center down from the top of the display.</p></li>
  1020. <li><p>The Photos app now lets you edit video in most, if not all, of the ways you can edit photos. Cropping, applying filters, adjusting brightness and contrast, etc. A lot of these features are computationally impressive. Applying filters to 4K video with no render time? On a phone? But my favorite new feature is so simple: you can trim video now without saving the trimmed version as a new video. So if you just want to trim a few seconds from the end of a clip, you don’t wind up with two videos in your library.</p></li>
  1021. <li><p>The new SF Camera font is delightful. Literally no one is going to buy an iPhone 11 just to get a slightly more industrial-looking font in the Camera app, but it’s a nice bonus. <strong>Update:</strong> OK, OK, we all know there’s at least one person who might buy an iPhone 11 just to get the new SF Camera font.</p></li>
  1022. <li><p>QuickTake seems the closest to marketing spite, by which I mean this is such a great idea that I really think it ought to be part of the Camera app for all iPhones running iOS 13. This is the feature where you can just tap-and-hold the shutter button in Photo Mode to shoot video instead. Previously, pressing and holding the shutter button shot a burst of stills. I want to shoot video way more often than I want to shoot a burst of stills. If you do want to shoot a burst of stills, slide the shutter button to the left. Slide the shutter to the right to lock it into video recording, so you don’t have to keep your thumb down on the shutter button. (Also: <a href="">nice name</a>.)</p></li>
  1023. </ul>
  1025. <h2>Colors and Textures</h2>
  1027. <p>The review units loaned to me by Apple are all green: green iPhone 11, “midnight green” iPhone 11 Pro and Pro Max.</p>
  1029. <p>The pastel green of the iPhone 11 is not my style, but it’s an intriguing color. Depending on the lighting, it sometimes looks <em>almost</em> like Tiffany blue. I feel like Apple is really trying to make this clear case thing happen, because they continue to put a <em>lot</em> of work into the new colors for iPhones.</p>
  1031. <p>Last week I described the 11 Pro’s midnight green as having “<a href="">a bit of a Boba Fett feel to it</a>”. I stand by that. It’s a very cool-looking green. It looks quite different depending on the lighting conditions, though. In sunlight, it clearly looks green. Indoors, however, it looks more neutral, and sometimes even look like dark gray. I pre-ordered a space gray iPhone 11 Pro for my personal use, not so much because I dislike the midnight green as that I’m boring that way. If Apple had replaced space gray with midnight green, I’d have ordered midnight green and wouldn’t have complained. It really is a neat look, different from any phone finish I’ve seen before. It’s no surprise that Apple’s first two iPhone 11 Pro TV commercials <a href="">exclusively</a> <a href="">feature</a> the midnight green finish. (Both spots also look like they take place in a spaceship corridor where Boba Fett would feel right at home.)</p>
  1033. <p>The glass backs of the iPhone 8, X, XS, and XR have all been glossy. So is the back of the iPhone 11. The 11 Pro back has a matte finish, though. I like it. I won’t say it adds a lot of grippiness, but it adds some, and it definitely makes it possible to tell which side of the phone is which by feel. The texture feels very similar to — if not identical to — the matte glass trackpads on recent MacBooks.</p>
  1035. <h2>iOS 13.0</h2>
  1037. <p>I ran into a handful of bugs over the last week. One time Messages completely froze, and the phone started getting very warm. Force quitting Messages didn’t help — I had to power-cycle the phone to get Messages working again. Several times the keyboard in Messages went entirely white. I could actually still type, but I couldn’t see the keys I was pressing. With iOS 13.1 coming just 10 days after iPhone 11 units get into customer hands, I don’t see the point in belaboring this, but 13.1 needs to be a lot more stable than 13.0. 13.0 feels like a late stage beta.</p>
  1039. <h2>Conclusion</h2>
  1041. <p>Here I am, 5,000+ words into this review of these three phones, and my gut feeling is that the best way to review them is simply to show dozens of photos and videos shot with them, compared to the same photos and videos shot with older iPhones and competing Android phones. “Show, don’t tell”, is probably the best way to tell the story of the iPhones 11.</p>
  1043. <p>The battery life gains should be of interest to everyone, even those who don’t care about the camera, but if you’re not interested in the camera systems, I don’t see how there’s any way to get you excited about the iPhones 11.</p>
  1045. <p>Several times over the past few years, I’ve had conversations along the lines of, “<em>I know they’re never going to do this, but wouldn’t it be cool if Apple made a real camera?</em>” As the iPhone camera system evolves, I’m starting to think Apple <em>is</em> making a real camera, right under our noses — or perhaps better said, right in our pockets.</p>
  1047. <div class="footnotes">
  1048. <hr />
  1049. <ol>
  1050. <li id="fn1-2019-09-17">
  1051. <p>And let me just add this for those who insist that it’s some sort of problem that the iPhones 11 — no matter how improved their cameras are, no matter their longer battery life, no matter their faster yet-at-the-same-time more power-efficient A13 chips — seem like mere incremental upgrades over last year’s iPhone XS and XR models. <em>When has it ever been different?</em> Were you blown away when the iPhone 3G added 3G networking and GPS and nothing else <em>and</em> replaced the original iPhone’s wonderful aluminum case with cheap-feeling plastic? Did the differences between the iPhone 4 and 4S knock you off your feet? Do you honestly remember the differences between the 4 and 4S? Incremental year-over-year improvements are <a href="">how Apple rolls</a>. For the $700 it costs to buy a base model iPhone 11 — let alone the $1,450 it costs for a 512 GB iPhone 11 Pro Max — you ought to expect it to last three years or longer before you feel a <em>need</em> for a new iPhone.</p>
  1053. <p>I’m sure this footnote will put an end to this argument.&nbsp;<a href="#fnr1-2019-09-17"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;</a></p>
  1054. </li>
  1055. </ol>
  1056. </div>
  1060.    ]]></content>
  1061.  <title>★ The iPhone 11 and iPhones 11 Pro</title></entry><entry>
  1062. <title>Matthew Panzarino Hopes Apple Arcade Makes Room for Weird, Cool Shit</title>
  1063. <link rel="alternate" type="text/html" href="" />
  1064. <link rel="shorturl" type="text/html" href="" />
  1065. <link rel="related" type="text/html" href="" />
  1066. <id>,2019:/linked//6.36040</id>
  1067. <published>2019-09-16T23:47:25Z</published>
  1068. <updated>2019-09-16T23:48:59Z</updated>
  1069. <author>
  1070. <name>John Gruber</name>
  1071. <uri></uri>
  1072. </author>
  1073. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1074. <p>Matthew Panzarino, writing for TechCrunch:</p>
  1076. <blockquote>
  1077.  <p>Apple Arcade seems purpose-built to make room in the market for
  1078. beautiful, sad, weird, moving, slow, clever and heartfelt. All
  1079. things that the action, shooter and MOBA-driven major market of
  1080. games has done nothing to foster over the last decade.</p>
  1082. <p>I had a chance to play a bunch of the titles coming to Apple
  1083. Arcade, which launched today in a surprise move for some early
  1084. testers of iOS 13. Nearly every game I played was fun, all were
  1085. gorgeous and some were really, really great.</p>
  1086. </blockquote>
  1088. <div>
  1089. <a  title="Permanent link to ‘Matthew Panzarino Hopes Apple Arcade Makes Room for Weird, Cool Shit’"  href="">&nbsp;★&nbsp;</a>
  1090. </div>
  1092. ]]></content>
  1093.  </entry><entry>
  1095.    <link rel="alternate" type="text/html" href="" />
  1096. <link rel="shorturl" href="" />
  1097. <id>,2019://1.36039</id>
  1098. <published>2019-09-16T16:21:57Z</published>
  1099. <updated>2019-09-16T22:13:17Z</updated>
  1100. <author>
  1101. <name>John Gruber</name>
  1102. <uri></uri>
  1103. </author>
  1104. <summary type="text">What Warzel has written — not on his personal blog, mind you, but in a column in the goddamn New York Times — has nothing to do with Apple, nothing to do with iPhone users, and nothing to do with society or culture at large. It is not an honest attempt to persuade anyone about anything.</summary>
  1105. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1106. <p>Charlie Warzel, in his column for The New York Times last Wednesday, “<a href="">The Last Apple Keynote (Let’s Hope)</a>”:</p>
  1108. <blockquote>
  1109.  <p>But what started as a Steve Jobs TED talk has become a parody — a
  1110. decadent pageant of Palo Alto executives, clothed in their finest
  1111. Dad Casual, reading ad copy as lead-ins for vaguely sexual
  1112. jump-cut videos of brushed aluminum under nightclub lighting. The
  1113. events are exhausting love letters to consumerism complete with
  1114. rounds of applause from the laptop-lit faces of the tech blogging
  1115. audience when executives mention that you (yes you!) can hold the
  1116. future in your hands for just $24.95 per month or $599 with
  1117. trade-in.</p>
  1118. </blockquote>
  1120. <p>There was a long thread on Twitter in response, mostly either <a href="">mocking Warzel</a> or <a href="">rationally objecting to</a> the slew of things he got wrong about these events. That second link will open a long conversation thread on Twitter, which Warzel himself joined, and is well worth reading. I’ll leave the point-by-point critique to that Twitter thread, but I must point out that the “tech bloggers” with “laptop-lit faces” generally don’t applaud during Apple keynotes — journalistic stoicism aside, the reason their faces are laptop-lit is that they’re busy live-blogging and typing notes. The raucous applause you hear throughout Apple keynotes comes from Apple employees and VIP invitees. There are a lot fewer media attendees at these events than most people think, especially at smaller venues like Steve Jobs Theater.</p>
  1122. <blockquote>
  1123.  <p>The entire event is at odds with our current moment — one in
  1124. which inequality, economic precarity and populist frustration
  1125. have infiltrated our politics and reshaped our relationships with
  1126. once-adored tech companies. But it’s not just the tech backlash.
  1127. When the world feels increasingly volatile and fragile, it feels
  1128. a little obscene to gather to worship a $1,000 phone. […]</p>
  1129. </blockquote>
  1131. <p>Nobody is there to “worship” a phone. But the main point Warzel misses is that the people invited to attend Apple’s events are not the point, and are not really the audience. These are not press events. They are “Apple events” and Apple invites a limited number of media to attend. The millions of people out in the world who watch via video are the real audience. Apple wants to pitch them directly, and millions of people want to see it. And I do mean millions — <em>tens of millions</em>. I’m going to be lazy and just quote here from last week’s issue of Dan Frommer’s excellent subscription newsletter <a href="">The New Consumer</a><sup id="fnr1-2019-09-16"><a href="#fn1-2019-09-16">1</a></sup>:</p>
  1133. <blockquote>
  1134.  <p>Apple generally doesn’t share information about how popular its
  1135. keynote livestreams are, even after it has spent the last several
  1136. years stoking the audience with Twitter-based reminder campaigns.</p>
  1138. <p>But yesterday the company also streamed its iPhone 11 event on
  1139. YouTube for the first time. And there alone, <a href="">almost 2 million
  1140. people</a> were watching concurrently. That’s on top of however
  1141. many were watching Apple’s official stream — potentially an equal
  1142. or greater number. That’s a lot!</p>
  1144. <p>The <a href="">full archived video</a> also now has 2 million views on
  1145. YouTube, an <a href="">Apple Event in a flash highlight reel</a> has 13
  1146. million, an <a href="">iPhone 11 video</a> has 14 million, and an <a href="">iPhone
  1147. 11 Pro video</a> has 10 million. Pity the <a href="">Apple Watch Series
  1148. 5</a>, with just 1.5 million views.</p>
  1150. <p>I think of this whenever I hear dated thinking about “normal
  1151. users” versus “geeks,” or some other similarly phrased dichotomy.</p>
  1152. </blockquote>
  1154. <p>Frommer wrote that Wednesday, the day after Apple’s event. Today, almost a week after the event, those YouTube view numbers are up to:</p>
  1156. <ul>
  1157. <li>Whole event: 4 million</li>
  1158. <li>“Apple Event in a Flash”: 17.4 million</li>
  1159. <li>“Introducing iPhone 11”: 27.4 million</li>
  1160. <li>“Introducing iPhone 11 Pro: 23.4 million</li>
  1161. <li>“Introducing Apple Watch Series 5”: 2.8 million</li>
  1162. </ul>
  1164. <p>And again, those numbers <em>don’t include</em> however many million people watch <a href="">Apple’s own hosted version of the event video</a>.</p>
  1166. <p>There are plenty of things one could criticize about Apple’s events, last week’s included, but the basic idea of them is not “at odds with our current moment”. If anything, people look to them as relief from the current moment. Gadgets are fun. Apple, of course, loves the massive publicity these events — especially iPhone events — generate. Apple enthusiasts love watching the events. Everyone else is free to ignore them. These events aren’t like the Super Bowl, where the whole country either shuts down or holds a viewing party.<sup id="fnr2-2019-09-16"><a href="#fn2-2019-09-16">2</a></sup> Apple events are ridiculously easy to ignore if you don’t care.</p>
  1168. <p>Back to Warzel:</p>
  1170. <blockquote>
  1171.  <p>The company’s flagship product — the iPhone — no longer feels
  1172. like a piece of the future dropped from into the hands of mere
  1173. mortals. It feels like, well, a phone, a commodity. And so the
  1174. whole thing seems gratuitous, self-serving and, most importantly,
  1175. quite removed from the very fraught relationship most of us have
  1176. with our phones.</p>
  1177. </blockquote>
  1179. <p>People love their phones, iPhone owners in particular, and millions of them are happy to watch Apple introduce new ones. There’s no question that “<em>Hey, maybe we all spend too much time and attention on our phones</em>” is on our minds, but that’s secondary to the fact that we love our phones.</p>
  1181. <blockquote>
  1182.  <p>That’s part of why the keynotes need to end. Losing them doesn’t
  1183. mean that the new technology isn’t impressively engineered
  1184. (machine learning cameras!) or that Apple has failed. It’s
  1185. probably the opposite. The iPhone set out to change everything,
  1186. and it did. Mr. Jobs famously pitched Apple products with the
  1187. line, “It just works.” He’s right. It does. And we live with the
  1188. effects — the good and the very bad — every day. There’s no more
  1189. need for the song and dance — or Lewis and Clarking a digital
  1190. frog across a bathroom floor.</p>
  1191. </blockquote>
  1193. <p>“Need” is a strawman word. Of course we don’t <em>need</em> to see Apple introduce new phones. And Apple doesn’t <em>need</em> to hold an event to introduce them. But <em>should</em> Apple continue to hold these events? Of course they should. Jiminy.</p>
  1195. <p>The whole thing is a bluff. If there’s even a whiff of seriousness to Warzel’s proposal, it’s that — what? — the tens of millions of people interested in learning about Apple’s new products would be better served reading about it in publications like, oh, say, The New York Times? Filtered by writers like Warzel, who is so jaded he’s already deemed the new phones “a commodity”, and his colleague Jack Nicas, who mocked a woman wearing a media badge at the event <a href="">for crying “during an Apple Watch ad”</a>. That was good for a <em>we’re above any sense of emotion</em> laugh until the woman in question, Ellen Cushing of The Atlantic, <a href="">piped into the thread with this unguarded and honest response</a>.</p>
  1197. <p>There’s no reason to write a column unless you have an objective. Could be you just want to make the reader laugh. Usually, it’s to make a point. You don’t have to make your point literally. Many times, it’s more effective <em>not</em> to make your point literally. Arguably the most famous essay in the English language is Jonathan Swift’s 1729 “<a href="">A Modest Proposal</a>”, wherein Swift proposed that poor Irish people sell their children as food to wealthy Englishmen. Swift’s point was made through satire: British callousness toward the plight of the Irish was deeply immoral. Absurdity made the point painfully clear.</p>
  1199. <p>Warzel’s column isn’t satirical in the least. But it’s not literal, either. Imagine Warzel’s own discomfort if Phil Schiller were to call him and invite him to Cupertino to help Schiller make the case to Tim Cook that Apple should stop holding events. Seriously, imagine if Tim Cook went to the Apple board and told them Apple would no longer be holding product introduction events, because he was persuaded by Charlie Warzel’s column in The New York Times. Imagine the scene. The board members would start looking around the room for hidden cameras. They’d check for booze on Cook’s breath.</p>
  1201. <p>This gets to the heart of the utter vacuousness of Warzel’s column. What Warzel has written — not on his personal blog, mind you, but in a column in the goddamn New York Times — has nothing to do with Apple, nothing to do with iPhone users, and nothing to do with society or culture at large. It is not an honest attempt to persuade anyone about anything.</p>
  1203. <p>It’s all about Charlie Warzel.</p>
  1205. <p>Warzel wrote an entire column in The New York Times to let the world know that even though he writes about technology, he’s so far above getting excited about any of it that he thinks Apple should stop holding events to introduce new products. To quote my favorite <a href="">spiritual leader</a>, “Well, isn’t that special?”</p>
  1207. <div class="footnotes">
  1208. <hr />
  1209. <ol>
  1211. <li id="fn1-2019-09-16">
  1212. <p>Frommer was my guest <a href="">last week on The Talk Show</a>, and is a friend, but I mean it when I say you should check out <a href="">The New Consumer</a> and consider subscribing.&nbsp;<a href="#fnr1-2019-09-16"  class="footnoteBackLink"  title="Jump back to footnote 1 in the text.">&#x21A9;&#xFE0E;</a></p>
  1213. </li>
  1215. <li id="fn2-2019-09-16">
  1216. <p>Feel free to substitute “World Cup” for “Super Bowl” if you live somewhere where football is played with feet.&nbsp;<a href="#fnr2-2019-09-16"  class="footnoteBackLink"  title="Jump back to footnote 2 in the text.">&#x21A9;&#xFE0E;︎</a></p>
  1217. </li>
  1220. </ol>
  1221. </div>
  1225.    ]]></content>
  1226.  <title>★ Let’s Go Further and Hope for Every Last Drop of Joy to Be Drained From the World</title></entry><entry>
  1227. <title>Kolide</title>
  1228. <link rel="alternate" type="text/html" href=";utm_medium=talkshow&amp;utm_campaign=launch" />
  1229. <link rel="shorturl" type="text/html" href="" />
  1230. <link rel="related" type="text/html" href="" />
  1231. <id>,2019:/linked//6.36038</id>
  1232. <published>2019-09-15T17:37:51Z</published>
  1233. <updated>2019-09-15T17:37:52Z</updated>
  1234. <author>
  1235. <name>John Gruber</name>
  1236. <uri></uri>
  1237. </author>
  1238. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1239. <p>My thanks to Kolide for again sponsoring Daring Fireball. Kolide is a new Slack app that messages employees when their Mac, Windows, or Linux device is not compliant with security best-practices or policy.</p>
  1241. <p>With this app, Kolide will notify users or groups when a device is out of compliance along with clear instructions about what is wrong, and step by step instructions to remediate the issue themselves. They can even confirm in real-time that they resolved the problem with an interactive button inside the Slack message!</p>
  1243. <p>Unlike most endpoint security solutions, Kolide was designed with user privacy in mind. Your users will know what data is collected about their device, who can see that data, and can even view the full source code of the agent that is run on the device.</p>
  1245. <p>Kolide is already used by hundreds of fast growing companies who want to level-up their device security without locking down their devices. <a href=";utm_medium=talkshow&amp;utm_campaign=launch">Try Kolide’s new product for free for 30 days for your entire fleet</a>.</p>
  1247. <div>
  1248. <a  title="Permanent link to ‘Kolide’"  href="">&nbsp;★&nbsp;</a>
  1249. </div>
  1251. ]]></content>
  1252.  </entry><entry>
  1253. <title>Jason Snell: ‘The U1 Chip in the iPhone 11 Is the Beginning of an Ultra Wideband Revolution’</title>
  1254. <link rel="alternate" type="text/html" href="" />
  1255. <link rel="shorturl" type="text/html" href="" />
  1256. <link rel="related" type="text/html" href="" />
  1257. <id>,2019:/linked//6.36037</id>
  1258. <published>2019-09-14T20:17:55Z</published>
  1259. <updated>2019-09-15T02:19:27Z</updated>
  1260. <author>
  1261. <name>John Gruber</name>
  1262. <uri></uri>
  1263. </author>
  1264. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1265. <p>Great piece from Jason Snell, writing at Six Colors:</p>
  1267. <blockquote>
  1268.  <p>From raw data alone, UWB devices can detect locations within 10
  1269. centimeters (4 inches), but depending on implementation that
  1270. accuracy can be lowered to as much as 5 millimeters, according to
  1271. Mickael Viot, VP of marketing at UWB chipmaker Decawave. […]</p>
  1273. <p>Of course, that’s only if most smartphones are UWB enabled. As of
  1274. today, the total number of smartphones shipping with UWB onboard
  1275. is zero. In fact the iPhone 11 family, when it arrives next week,
  1276. will be the first consumer smartphones to support UWB. A glance at
  1277. the various trade groups coalescing around this technology
  1278. suggests that Google, Samsung, HTC, and other major players plan
  1279. to get in the game.</p>
  1281. <p>“It’s huge,” Viot says, that Apple has taken this step. He likens
  1282. the move to Apple adopting Wi-Fi in the first iBook, which was the
  1283. push the technology needed to start rolling out everywhere.</p>
  1284. </blockquote>
  1286. <p>It’s interesting to think about Ultra Wideband in comparison to 5G. Critics are blasting Apple for not including 5G in any of this year’s iPhones, claiming that everyone buying an iPhone this year will be missing out for years to come. If UWB is the next big thing, everyone buying a 2019 iPhone will still get to play for years to come.</p>
  1288. <p>Apple’s usually <em>not</em> first to new technology (again: see 5G), but when they are, it is often a big new thing.</p>
  1290. <div>
  1291. <a  title="Permanent link to ‘Jason Snell: ‘The U1 Chip in the iPhone 11 Is the Beginning of an Ultra Wideband Revolution’’"  href="">&nbsp;★&nbsp;</a>
  1292. </div>
  1294. ]]></content>
  1295.  </entry><entry>
  1296. <title>University of Tennessee Offers Scholarship to Young Kid Bullied Over Homemade T-Shirt</title>
  1297. <link rel="alternate" type="text/html" href="" />
  1298. <link rel="shorturl" type="text/html" href="" />
  1299. <link rel="related" type="text/html" href="" />
  1300. <id>,2019:/linked//6.36036</id>
  1301. <published>2019-09-14T19:53:41Z</published>
  1302. <updated>2019-09-14T21:46:43Z</updated>
  1303. <author>
  1304. <name>John Gruber</name>
  1305. <uri></uri>
  1306. </author>
  1307. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1308. <p>Adam Rittenberg, writing for ESPN:</p>
  1310. <blockquote>
  1311.  <p>Tennessee announced Thursday that it has extended an offer of
  1312. admission and a four-year scholarship — for the Class of 2032 —
  1313. to the elementary school student in Altamonte Springs, Florida.</p>
  1315. <p>The university will cover the cost of the boy’s scholarship if he
  1316. chooses to attend the school and meets all admission requirements.</p>
  1318. <p>The boy’s story drew national attention earlier this week when
  1319. Laura Snyder, his teacher, detailed on Facebook how the boy had
  1320. been bullied after clipping a piece of paper with a “UT” design to
  1321. an orange T-shirt for “college colors day” at the school.</p>
  1322. </blockquote>
  1324. <p>There’s a lot of crummy news these days. Here’s a story that will make you feel good about humanity — and the power of social networks to do good. 15 years ago the upside of this story never would’ve happened.</p>
  1326. <div>
  1327. <a  title="Permanent link to ‘University of Tennessee Offers Scholarship to Young Kid Bullied Over Homemade T-Shirt’"  href="">&nbsp;★&nbsp;</a>
  1328. </div>
  1330. ]]></content>
  1331.  </entry><entry>
  1332. <title>Disney CEO Bob Iger Resigns From Apple Board</title>
  1333. <link rel="alternate" type="text/html" href="" />
  1334. <link rel="shorturl" type="text/html" href="" />
  1335. <link rel="related" type="text/html" href="" />
  1336. <id>,2019:/linked//6.36035</id>
  1337. <published>2019-09-13T23:56:14Z</published>
  1338. <updated>2019-09-13T23:56:16Z</updated>
  1339. <author>
  1340. <name>John Gruber</name>
  1341. <uri></uri>
  1342. </author>
  1343. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1344. <p>CNBC:</p>
  1346. <blockquote>
  1347.  <p>Disney is launching streaming video service Disney+ on Nov. 12,
  1348. which will compete with Apple’s Apple TV+ service, scheduled to
  1349. become available on Nov. 1.</p>
  1351. <p>Iger resigned on Sept. 10, the day Apple announced the price and
  1352. release date for its streaming service. The two streaming services
  1353. will increasingly come into conflict in the future as both compete
  1354. for original content.</p>
  1355. </blockquote>
  1357. <p>This seems to be just for propriety’s sake — Apple TV+ and Disney+ do compete directly, so it just wouldn’t be appropriate for Iger to remain on Apple’s board. His statement and Apple’s both make the departure seem very amicable. Apple’s statement is downright effusive:</p>
  1359. <blockquote>
  1360.  <p>Bob has been an exemplary board member for nearly eight years, and
  1361. for as long as he has led Disney he has been one of Apple’s most
  1362. trusted business partners. He is a dedicated, visionary CEO and a
  1363. role model for an entire generation of business leaders. More than
  1364. anything, Bob is our friend. He leads with his heart and he has
  1365. always been generous with his time and advice. While we will
  1366. greatly miss his contributions as a board member, we respect his
  1367. decision and we have every expectation that our relationship with
  1368. both Bob and Disney will continue far into the future.</p>
  1369. </blockquote>
  1371. <div>
  1372. <a  title="Permanent link to ‘Disney CEO Bob Iger Resigns From Apple Board’"  href="">&nbsp;★&nbsp;</a>
  1373. </div>
  1375. ]]></content>
  1376.  </entry><entry>
  1377. <title>Might the iPhones 11 Contain Hardware for Two-Way Inductive Charging?</title>
  1378. <link rel="alternate" type="text/html" href="" />
  1379. <link rel="shorturl" type="text/html" href="" />
  1380. <link rel="related" type="text/html" href="" />
  1381. <id>,2019:/linked//6.36034</id>
  1382. <published>2019-09-13T23:48:25Z</published>
  1383. <updated>2019-09-14T00:12:06Z</updated>
  1384. <author>
  1385. <name>John Gruber</name>
  1386. <uri></uri>
  1387. </author>
  1388. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1389. <p>Sonny Dickson, on Twitter:</p>
  1391. <blockquote>
  1392.  <p>Reliable sources are saying iPhone 11 and 11 Pro do include the
  1393. hardware for bilateral charging, but that it is software disabled.
  1394. Uncertain whether this was removed prior to final production run.</p>
  1395. </blockquote>
  1397. <p>This is the feature that was much-rumored in lead-up to this week, where you could set your AirPods charging case on the back of your iPhone and charge the AirPods case inductively (a.k.a. “wirelessly” but don’t get me started on that).</p>
  1399. <p>I wondered in response whether Apple had ever shipped hardware features without mentioning them, only to enable them in a software update later. They have:</p>
  1401. <ul>
  1402. <li>In 2007 Apple shipped a software update (for $2) <a href="">that enabled 802.11n Wi-Fi in several Macs</a>.</li>
  1403. <li>In 2008 they shipped a software update for iPod Touch that enabled Bluetooth. The update cost $20 (!). They had to charge for these software updates a decade ago due to the accounting of the time.</li>
  1404. <li><a href=";locale=en_US">Bluetooth wasn’t mentioned in the original specs</a> for the second-generation Apple TV, but <a href="">support was added in a software update</a>.</li>
  1405. </ul>
  1407. <p>And I’ve been told by a reliable little birdie that in years past Apple has shipped hardware that wound up <em>never</em> enabled in software.</p>
  1409. <div>
  1410. <a  title="Permanent link to ‘Might the iPhones 11 Contain Hardware for Two-Way Inductive Charging?’"  href="">&nbsp;★&nbsp;</a>
  1411. </div>
  1413. ]]></content>
  1414.  </entry><entry>
  1416.    <link rel="alternate" type="text/html" href="" />
  1417. <link rel="shorturl" href="" />
  1418. <id>,2019://1.36033</id>
  1419. <published>2019-09-13T16:01:27Z</published>
  1420. <updated>2019-09-13T16:13:01Z</updated>
  1421. <author>
  1422. <name>John Gruber</name>
  1423. <uri></uri>
  1424. </author>
  1425. <summary type="text">When a utility is designed to compensate for a hole in Mac OS X, the developer should not expect the hole to remain unfilled by Apple forever.</summary>
  1426. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1427. <p>As referenced in today’s <a href="">letter to Apple from the House Judiciary Committee</a>, Reed Albergotti writing for The Washington Post last week (“<a href="">How Apple Uses Its App Store to Copy the Best Ideas</a>”):</p>
  1429. <blockquote>
  1430.  <p>Clue, a popular app women use to track their periods, has risen to
  1431. near the top of Apple’s Health and Fitness category.</p>
  1433. <p>It could be downhill from here.</p>
  1435. <p>Apple plans this month to incorporate some of Clue’s core
  1436. functionality such as fertility and period prediction into its own
  1437. Health app that comes pre-installed in every iPhone and is free —
  1438. unlike Clue, which is free to download but earns money by selling
  1439. subscriptions and services within its app. Apple’s past
  1440. incorporation of functionality included in other third-party apps
  1441. has often led to their demise. […]</p>
  1443. <p>When Apple made a flashlight part of its operating system in
  1444. 2013, it rendered instantly redundant myriad apps that offered
  1445. that functionality. Everything from the iPhone’s included
  1446. “Measure” app to its built-in animated emoji were originally apps
  1447. in the App Store.</p>
  1448. </blockquote>
  1450. <p>The thrust of the Post’s story is clear from its headline. But I don’t think it holds any water. What’s the alternative? For Apple never to add any features to the OS that exist in third-party apps? Of course fertility and period-tracking should be features in Apple’s Health app. If anything they should have been there sooner. Apple didn’t need to look at Clue’s popularity to know this. One of the factors every successful developer considers is whether or not an idea might be something Apple (or Google, or Microsoft, or whoever the platform vendor is) might incorporate as a feature in the system. The more basic the feature, the more likely that is. The flashlight is a perfect example. It’s so obviously a good feature for the system that it’s a button on the lock screen — one of only two, right next to the camera.</p>
  1452. <p>When Apple implements a feature or app idea, they do it in a way that has the broadest possible appeal (or at least try to). The key to competing with Apple as a third-party developer is to focus on segments of the audience that want more than the basics. Apple’s Mail, Podcasts, Notes, and Calendar apps (to name just a few) are well-done and much-used. And all of those categories have very successful third-party alternatives. Apple improved Reminders significantly this year, but I don’t think Things or OmniFocus (or any of the other popular to-do/task managers) have anything to worry about.</p>
  1454. <blockquote>
  1455.  <p>The misfortune of having an idea copied by Apple even has an
  1456. industry term. “Getting Sherlocked” harks back to the time Apple’s
  1457. desktop search tool called “Sherlock” borrowed many of the
  1458. features of a third-party companion tool called “Watson,” which no
  1459. longer exists.</p>
  1460. </blockquote>
  1462. <p>Two points here. First, Sherlock doesn’t exist any more either — the entire concept wasn’t long for this world. Second, and more importantly, the Sherlock/Watson thing <a href="">happened in 2002</a> — 6 years before the iOS App Store and 8 years before the Mac App Store. The debate over what’s fair game for Apple (or Google, or Microsoft) to copy from third-party developers has nothing to do with app stores.  A popular app is a popular app, and the platform vendors have always known all the popular apps.</p>
  1464. <p>Back in October 2003, <a href="">I wrote about a controversy in which a third-party developer accused Apple of stealing their Command-Tab switcher</a>, even though the features Apple was adding dated back to Microsoft Windows 3 a decade earlier. Ideas are cheap. My concluding sentence in that piece works just as well today:</p>
  1466. <blockquote>
  1467.  <p>When a utility is designed to compensate for a hole in Mac OS X,
  1468. the developer should not expect the hole to remain unfilled by
  1469. Apple forever.</p>
  1470. </blockquote>
  1474.    ]]></content>
  1475.  <title>★ About That Washington Post Story on Apple Copying Features From Top Apps in the App Store</title></entry><entry>
  1476. <title>House Judiciary Committee Investigating Apple Regarding ‘Competition in Digital Markets’ (PDF)</title>
  1477. <link rel="alternate" type="text/html" href="" />
  1478. <link rel="shorturl" type="text/html" href="" />
  1479. <link rel="related" type="text/html" href="" />
  1480. <id>,2019:/linked//6.36032</id>
  1481. <published>2019-09-13T15:16:49Z</published>
  1482. <updated>2019-09-13T15:26:59Z</updated>
  1483. <author>
  1484. <name>John Gruber</name>
  1485. <uri></uri>
  1486. </author>
  1487. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1488. <p>(Note that the link is a scanned PDF.)</p>
  1490. <p>My reading is that this is a <em>really</em> broad request. They want Apple to break down revenue by specific products in a far more granular way than they provide in quarterly statements — e.g. revenue for Apple Watch specifically. And they’re asking for “all communication” from executives regarding a slew of topics.</p>
  1492. <p>The letter says “we write to request that Apple Inc. (the “Company”) provide the documents and executive communications set forth in the Schedule in accordance with the attached Definitions and Instructions no later than October 14, 2019.” Unclear to me as a non-lawyer is whether this really is a “request” — and even if it is, it feels like <a href="">an offer Apple can’t refuse</a>.</p>
  1494. <p>I enjoy that on page 4, they use “sherlock” as a verb, albeit in quotes, with no explanation other than a footnote pointing to <a href="">this Washington Post story from last week</a>.</p>
  1496. <div>
  1497. <a  title="Permanent link to ‘House Judiciary Committee Investigating Apple Regarding ‘Competition in Digital Markets’ (PDF)’"  href="">&nbsp;★&nbsp;</a>
  1498. </div>
  1500. ]]></content>
  1501.  </entry><entry>
  1502. <title>What It’s Like to Demo a Game Live on Stage at an Apple Event</title>
  1503. <link rel="alternate" type="text/html" href="" />
  1504. <link rel="shorturl" type="text/html" href="" />
  1505. <link rel="related" type="text/html" href="" />
  1506. <id>,2019:/linked//6.36031</id>
  1507. <published>2019-09-13T14:59:25Z</published>
  1508. <updated>2019-09-13T15:00:34Z</updated>
  1509. <author>
  1510. <name>John Gruber</name>
  1511. <uri></uri>
  1512. </author>
  1513. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1514. <p>“Steve would really like you to get 5 stars…”</p>
  1516. <div>
  1517. <a  title="Permanent link to ‘What It’s Like to Demo a Game Live on Stage at an Apple Event’"  href="">&nbsp;★&nbsp;</a>
  1518. </div>
  1520. ]]></content>
  1521.  </entry><entry>
  1522. <title>Apple Arcade: 100 Games in 100 Seconds</title>
  1523. <link rel="alternate" type="text/html" href=";" />
  1524. <link rel="shorturl" type="text/html" href="" />
  1525. <link rel="related" type="text/html" href="" />
  1526. <id>,2019:/linked//6.36029</id>
  1527. <published>2019-09-13T02:50:15Z</published>
  1528. <updated>2019-09-13T02:50:16Z</updated>
  1529. <author>
  1530. <name>John Gruber</name>
  1531. <uri></uri>
  1532. </author>
  1533. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1534. <p>Apple should have played this video in Tuesday’s event instead of wasting so much time on a handful of live game demos. This video conveys excitement, and makes it feel like there are going to be a lot of games with a lot of variety.</p>
  1536. <div>
  1537. <a  title="Permanent link to ‘Apple Arcade: 100 Games in 100 Seconds’"  href="">&nbsp;★&nbsp;</a>
  1538. </div>
  1540. ]]></content>
  1541.  </entry><entry>
  1542. <title>Ring Fit Adventure for Nintendo Switch</title>
  1543. <link rel="alternate" type="text/html" href="" />
  1544. <link rel="shorturl" type="text/html" href="" />
  1545. <link rel="related" type="text/html" href="" />
  1546. <id>,2019:/linked//6.36027</id>
  1547. <published>2019-09-12T21:09:47Z</published>
  1548. <updated>2019-09-13T15:22:50Z</updated>
  1549. <author>
  1550. <name>John Gruber</name>
  1551. <uri></uri>
  1552. </author>
  1553. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1554. <p>Neat idea — brings back a lot of the feel of the Wii. The Wii was great in a few ways, but it was unique in the way it made casual gaming physical. You really could work up a sweat playing a game.</p>
  1556. <p>(There’s something weird about the two spokespeople in the video, though.  They’re impossibly cheerful. They have the feel of hostages extolling the virtues of Kim Jong-un’s hotel in Pyongyang.)</p>
  1558. <div>
  1559. <a  title="Permanent link to ‘Ring Fit Adventure for Nintendo Switch’"  href="">&nbsp;★&nbsp;</a>
  1560. </div>
  1562. ]]></content>
  1563.  </entry><entry>
  1564. <title>MG Siegler: ‘But Will They Go to 12?’</title>
  1565. <link rel="alternate" type="text/html" href="" />
  1566. <link rel="shorturl" type="text/html" href="" />
  1567. <link rel="related" type="text/html" href="" />
  1568. <id>,2019:/linked//6.36026</id>
  1569. <published>2019-09-12T20:26:03Z</published>
  1570. <updated>2019-09-12T20:26:05Z</updated>
  1571. <author>
  1572. <name>John Gruber</name>
  1573. <uri></uri>
  1574. </author>
  1575. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1576. <p>Another solid piece on Apple’s event Tuesday, from MG Siegler:</p>
  1578. <blockquote>
  1579.  <p>The iPhone is now officially a camera. I mean, it has been a
  1580. camera for a long time. The most popular camera in the world, as
  1581. Apple is quick to point out each and every year, a decade on. But
  1582. now it’s really a camera, as today’s keynote made clear. The key
  1583. parts of the presentations for both the iPhone 11 and the iPhone
  1584. 11 Pro were all about the camera. As Phil Schiller said in his
  1585. portion: “I know what you’re waiting for, and I am too. Let’s talk
  1586. about the cameras. Without question, my favorite part about
  1587. iPhone.”</p>
  1589. <p>It feels like if Apple wasn’t so wedded to their own legacy
  1590. branding — more on that in a bit — they would rename this thing
  1591. the iCamera.</p>
  1592. </blockquote>
  1594. <p>Just look at the back of these phones to see how central the camera systems are.</p>
  1596. <blockquote>
  1597.  <p>That was my main takeaway from today’s event, with a side of one
  1598. more thing: Apple is so far ahead when it comes to their chips in
  1599. these devices that they invited out their VP of Silicon to do a
  1600. verbal victory lap. Was this aimed at Samsung? Google? Xiaomi?
  1601. Qualcomm? Intel? Probably all of the above.</p>
  1602. </blockquote>
  1604. <p>I’ve said it before and will say it again: imagine what the Android commentariat would be saying if the tables were turned, and it was Snapdragon chips that were years ahead of Apple’s A-series chips in every single regard: CPU, GPU, and power efficiency. The first question for anyone who wants to argue that Apple showed no innovation Tuesday is how to explain the A13’s astonishing dominance over every other competing chipset.</p>
  1606. <div>
  1607. <a  title="Permanent link to ‘MG Siegler: ‘But Will They Go to 12?’’"  href="">&nbsp;★&nbsp;</a>
  1608. </div>
  1610. ]]></content>
  1611.  </entry><entry>
  1612. <title>Ben Thompson: ‘The iPhone and Apple’s Services Strategy’</title>
  1613. <link rel="alternate" type="text/html" href="" />
  1614. <link rel="shorturl" type="text/html" href="" />
  1615. <link rel="related" type="text/html" href="" />
  1616. <id>,2019:/linked//6.36025</id>
  1617. <published>2019-09-12T19:59:05Z</published>
  1618. <updated>2019-09-12T19:59:06Z</updated>
  1619. <author>
  1620. <name>John Gruber</name>
  1621. <uri></uri>
  1622. </author>
  1623. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1624. <p>Ben Thompson, writing at Stratechery, on Tuesday’s event:</p>
  1626. <blockquote>
  1627.  <p>That means that this year actually saw three price cuts:</p>
  1629. <ul>
  1630. <li><p>First, the iPhone 11 — this year’s mid-tier model — costs $50
  1631. less than the iPhone XR it is replacing.</p></li>
  1632. <li><p>Second, the iPhone XR’s price is being cut by $150 a year after
  1633. launch, not $100 as Apple has previously done.</p></li>
  1634. <li><p>Third, the iPhone 8’s price is also being cut by $150 two years
  1635. after launch, not $100 as Apple has previously done.</p></li>
  1636. </ul>
  1637. </blockquote>
  1639. <p>I completely missed this.</p>
  1641. <p>Also a great observation about why Apple brought out Deirdre O’Brien at the very end of the event:</p>
  1643. <blockquote>
  1644.  <p>So, in the case of this slide, you can get an iPhone 11 and Apple
  1645. TV+ for $17/month. […]</p>
  1647. <p>To that end, how long until there is a variant of the iPhone
  1648. Upgrade Program that is simply an all-up Apple subscription? Pay
  1649. one monthly fee, and get everything Apple has to offer. Indeed,
  1650. nothing would show that Apple is a Services company more than
  1651. making the iPhone itself a service, at least as far as the
  1652. customer relationship goes. You might even say it is innovative.</p>
  1653. </blockquote>
  1655. <div>
  1656. <a  title="Permanent link to ‘Ben Thompson: ‘The iPhone and Apple’s Services Strategy’’"  href="">&nbsp;★&nbsp;</a>
  1657. </div>
  1659. ]]></content>
  1660.  </entry><entry>
  1661. <title>Google-Owned Crashlytics Is Using Custom Fonts to Track Users</title>
  1662. <link rel="alternate" type="text/html" href="" />
  1663. <link rel="shorturl" type="text/html" href="" />
  1664. <link rel="related" type="text/html" href="" />
  1665. <id>,2019:/linked//6.36024</id>
  1666. <published>2019-09-12T18:35:51Z</published>
  1667. <updated>2019-09-13T02:02:05Z</updated>
  1668. <author>
  1669. <name>John Gruber</name>
  1670. <uri></uri>
  1671. </author>
  1672. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1673. <p>One of the things iOS has been sorely lacking for a decade is the ability for users to install custom fonts. Apple has put it off on the grounds that custom fonts open security and privacy holes. Proving Apple’s point, Google-owned Crashlytics is already abusing the feature to track users by installing a font with a custom identifier embedded. iOS 13 isn’t even out yet and they’re abusing this for tracking. Because these fonts are installed system-wide — which is the whole point of the feature, so users can use their custom fonts in any app that supports choosing a font — I believe <em>any</em> app can use Crashlytics’s font to uniquely identify users.</p>
  1675. <p>I haven’t tried this feature yet, but <a href="">Apple’s developer documentation indicates that users are prompted</a> to allow an app to install a font, so it can’t be done silently in the background. Most users, I suspect, would just allow this, thinking fonts are harmless — but at least those of you reading this are forewarned.</p>
  1677. <p><strong>Update:</strong> <a href="">Apparently this isn’t something based on iOS 13’s custom fonts feature</a>, but instead based on an older iOS feature that allows custom fonts to be installed with a configuration profile. The basic fact remains: custom fonts, however they’re installed, are not meant to be used for tracking users.</p>
  1679. <div>
  1680. <a  title="Permanent link to ‘Google-Owned Crashlytics Is Using Custom Fonts to Track Users’"  href="">&nbsp;★&nbsp;</a>
  1681. </div>
  1683. ]]></content>
  1684.  </entry><entry>
  1685. <link rel="alternate" type="text/html" href=";utm_medium=talkshow&amp;utm_campaign=launch" />
  1686. <link rel="shorturl" href="" />
  1687. <link rel="related" type="text/html" href="" />
  1688. <id>,2019:/feeds/sponsors//11.36023</id>
  1689. <author><name>Daring Fireball Department of Commerce</name></author>
  1690. <published>2019-09-11T22:51:29-04:00</published>
  1691. <updated>2019-09-11T22:51:30-04:00</updated>
  1692. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1693. <p>Kolide is a new Slack app that messages employees when their Mac, Windows, or Linux device is not compliant with security best-practices or policy.</p>
  1695. <p>With this app, Kolide will notify users or groups when a device is out of compliance along with clear instructions about what is wrong, and step by step instructions to remediate the issue themselves. They can even confirm in real-time that they resolved the problem with an interactive button inside the Slack message!</p>
  1697. <p>Unlike most endpoint security solutions, Kolide was designed with user privacy in mind. Your users will know what data is collected about their device, who can see that data, and can even view the full source code of the agent that is run on the device.</p>
  1699. <p>Kolide is already used by hundreds of fast growing companies who want to level-up their device security without locking down their devices. Try Kolide’s new product for free for 30 days for your entire fleet by visiting <a href=""></a>.</p>
  1701. <div>
  1702. <a  title="Permanent link to ‘Kolide: User Focused Security for Teams That Slack’"  href="">&nbsp;★&nbsp;</a>
  1703. </div>
  1705. ]]></content>
  1706. <title>[Sponsor] Kolide: User Focused Security for Teams That Slack</title></entry><entry>
  1707. <title>Uber Says It Is Not Subject to California Gig-Worker Law</title>
  1708. <link rel="alternate" type="text/html" href="" />
  1709. <link rel="shorturl" type="text/html" href="" />
  1710. <link rel="related" type="text/html" href="" />
  1711. <id>,2019:/linked//6.36021</id>
  1712. <published>2019-09-11T20:41:17Z</published>
  1713. <updated>2019-09-12T03:23:09Z</updated>
  1714. <author>
  1715. <name>John Gruber</name>
  1716. <uri></uri>
  1717. </author>
  1718. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1719. <p>Kate Conger, reporting for The New York Times:</p>
  1721. <blockquote>
  1722.  <p>Tony West, Uber’s chief legal officer, said in a news conference
  1723. that the ride-hailing company would not treat its drivers, who are
  1724. independent contractors, as employees under the California bill.
  1725. He said that drivers were not a core part of Uber’s business and
  1726. could maintain their independent status when the measure goes into
  1727. effect as state law on Jan. 1.</p>
  1728. </blockquote>
  1730. <p>Drivers are not a core part of Uber’s business. OK, sure.</p>
  1732. <div>
  1733. <a  title="Permanent link to ‘Uber Says It Is Not Subject to California Gig-Worker Law’"  href="">&nbsp;★&nbsp;</a>
  1734. </div>
  1736. ]]></content>
  1737.  </entry><entry>
  1738. <title>Uber Lays Off 435 People Across Engineering and Product Teams</title>
  1739. <link rel="alternate" type="text/html" href="" />
  1740. <link rel="shorturl" type="text/html" href="" />
  1741. <link rel="related" type="text/html" href="" />
  1742. <id>,2019:/linked//6.36020</id>
  1743. <published>2019-09-10T23:16:10Z</published>
  1744. <updated>2019-09-11T17:02:43Z</updated>
  1745. <author>
  1746. <name>John Gruber</name>
  1747. <uri></uri>
  1748. </author>
  1749. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1750. <p>Typically bad news gets announced on a Friday afternoon. In the tech industry, there’s an even better way to bury bad news: announcing it on the day of an iPhone event.</p>
  1752. <div>
  1753. <a  title="Permanent link to ‘Uber Lays Off 435 People Across Engineering and Product Teams’"  href="">&nbsp;★&nbsp;</a>
  1754. </div>
  1756. ]]></content>
  1757.  </entry><entry>
  1758. <title>New Apple Developer Tech Talk: ‘Metal Enhancements for A13 Bionic’</title>
  1759. <link rel="alternate" type="text/html" href="" />
  1760. <link rel="shorturl" type="text/html" href="" />
  1761. <link rel="related" type="text/html" href="" />
  1762. <id>,2019:/linked//6.36019</id>
  1763. <published>2019-09-10T21:28:08Z</published>
  1764. <updated>2019-09-10T21:28:09Z</updated>
  1765. <author>
  1766. <name>John Gruber</name>
  1767. <uri></uri>
  1768. </author>
  1769. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1770. <p>If you want nitty-gritty details on what’s new with the GPU in the A13 Bionic chip, Apple already has a 35-minute developer tech talk. For an overview, <a href="">graphics driver team manager Gokhan Avkarogullari posted a short thread on Twitter</a>.</p>
  1772. <div>
  1773. <a  title="Permanent link to ‘New Apple Developer Tech Talk: ‘Metal Enhancements for A13 Bionic’’"  href="">&nbsp;★&nbsp;</a>
  1774. </div>
  1776. ]]></content>
  1777.  </entry><entry>
  1778. <title>Release Dates for OS Updates, New iPhones, and Apple Watch</title>
  1779. <link rel="alternate" type="text/html" href="" />
  1780. <link rel="shorturl" type="text/html" href="" />
  1781. <link rel="related" type="text/html" href="" />
  1782. <id>,2019:/linked//6.36018</id>
  1783. <published>2019-09-10T21:18:54Z</published>
  1784. <updated>2019-09-10T23:22:28Z</updated>
  1785. <author>
  1786. <name>John Gruber</name>
  1787. <uri></uri>
  1788. </author>
  1789. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1790. <p>So glad John Voorhees put this list together — there are a lot of dates to keep track of here. Some oddities: iOS 13.0 is coming September 19, and 13.1 is scheduled to drop just 11 days later. iPadOS 13 isn’t shipping until September 30, which presumably means it’s going straight to 13.1. Unusual schedule for WatchOS 6, too: “September 19, 2019 for Series 3 and later Apple Watches and later this fall for Series 1 and 2.”</p>
  1792. <p>Federico Viticci <a href="">has a list of iOS/iPadOS features that are slated for “later this fall”</a>, presumably in iOS 13.2.</p>
  1794. <div>
  1795. <a  title="Permanent link to ‘Release Dates for OS Updates, New iPhones, and Apple Watch’"  href="">&nbsp;★&nbsp;</a>
  1796. </div>
  1798. ]]></content>
  1799.  </entry><entry>
  1800. <title>The Talk Show: ‘The Dumbest Thing Possible’</title>
  1801. <link rel="alternate" type="text/html" href="" />
  1802. <link rel="shorturl" type="text/html" href="" />
  1803. <link rel="related" type="text/html" href="" />
  1804. <id>,2019:/linked//6.36017</id>
  1805. <published>2019-09-10T03:59:00Z</published>
  1806. <updated>2019-09-10T23:42:11Z</updated>
  1807. <author>
  1808. <name>John Gruber</name>
  1809. <uri></uri>
  1810. </author>
  1811. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1812. <p>Special guest Dan Frommer returns to the show for a preview of this week’s Apple event.</p>
  1814. <p>Sponsored by:</p>
  1816. <ul>
  1817. <li><a href="">Eero</a>: Free overnight shipping with code “thetalkshow”. </li>
  1818. <li><a href="">Hullo Pillow</a>: Your favorite pillow, guaranteed.</li>
  1819. <li><a href="">Clearbanc</a>: Find out how you can receive Clearbanc capital by getting your 20 minute term sheet.</li>
  1820. </ul>
  1822. <div>
  1823. <a  title="Permanent link to ‘The Talk Show: ‘The Dumbest Thing Possible’’"  href="">&nbsp;★&nbsp;</a>
  1824. </div>
  1826. ]]></content>
  1827.  </entry><entry>
  1828. <title>Kolide</title>
  1829. <link rel="alternate" type="text/html" href=";utm_medium=talkshow&amp;utm_campaign=launch" />
  1830. <link rel="shorturl" type="text/html" href="" />
  1831. <link rel="related" type="text/html" href="" />
  1832. <id>,2019:/linked//6.36016</id>
  1833. <published>2019-09-08T16:26:13Z</published>
  1834. <updated>2019-09-08T16:28:59Z</updated>
  1835. <author>
  1836. <name>John Gruber</name>
  1837. <uri></uri>
  1838. </author>
  1839. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1840. <p>My thanks to Kolide for sponsoring last week at DF. Kolide is a new Slack app that messages employees when their Mac, Windows, or Linux device is not compliant with security best-practices or policy.</p>
  1842. <p>With this app, Kolide will notify users or groups when a device is out of compliance along with clear instructions about what is wrong, and step by step instructions to remediate the issue themselves. They can even confirm in real-time that they resolved the problem with an interactive button inside the Slack message!</p>
  1844. <p>Unlike most endpoint security solutions, Kolide was designed with user privacy in mind. Your users will know what data is collected about their device, who can see that data, and can even view the full source code of the agent that is run on the device.</p>
  1846. <p>Kolide is already used by hundreds of fast growing companies who want to level-up their device security without locking down their devices. <a href=";utm_medium=talkshow&amp;utm_campaign=launch">Try Kolide’s new product for free for 30 days for your entire fleet</a>.</p>
  1848. <div>
  1849. <a  title="Permanent link to ‘Kolide’"  href="">&nbsp;★&nbsp;</a>
  1850. </div>
  1852. ]]></content>
  1853.  </entry><entry>
  1854. <title>NOAA Staff Warned Against Contradicting Trump</title>
  1855. <link rel="alternate" type="text/html" href="" />
  1856. <link rel="shorturl" type="text/html" href="" />
  1857. <link rel="related" type="text/html" href="" />
  1858. <id>,2019:/linked//6.36015</id>
  1859. <published>2019-09-08T16:15:25Z</published>
  1860. <updated>2019-09-08T16:24:32Z</updated>
  1861. <author>
  1862. <name>John Gruber</name>
  1863. <uri></uri>
  1864. </author>
  1865. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1866. <p>The Washington Post:</p>
  1868. <blockquote>
  1869.  <p>“This is the first time I’ve felt pressure from above to not say what truly is the forecast,” the meteorologist said. “It’s hard for me to wrap my head around. One of the things we train on is to dispel inaccurate rumors and ultimately that is what was occurring — ultimately what the Alabama office did is provide a forecast with their tweet, that is what they get paid to do.”</p>
  1870. </blockquote>
  1872. <p>Even if you’re an outright bigot (and if you voted for him, you are) you ought to be outraged by Trump at this point. He’s politicized the goddamn weather.</p>
  1874. <div>
  1875. <a  title="Permanent link to ‘NOAA Staff Warned Against Contradicting Trump’"  href="">&nbsp;★&nbsp;</a>
  1876. </div>
  1878. ]]></content>
  1879.  </entry><entry>
  1880. <title>Apple Pushes Back on iOS Security in Wake of Google’s Report</title>
  1881. <link rel="alternate" type="text/html" href="" />
  1882. <link rel="shorturl" type="text/html" href="" />
  1883. <link rel="related" type="text/html" href="" />
  1884. <id>,2019:/linked//6.36014</id>
  1885. <published>2019-09-06T17:48:23Z</published>
  1886. <updated>2019-09-06T18:49:09Z</updated>
  1887. <author>
  1888. <name>John Gruber</name>
  1889. <uri></uri>
  1890. </author>
  1891. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1892. <p>Apple Newsroom:</p>
  1894. <blockquote>
  1895.  <p>First, the sophisticated attack was narrowly focused, not a
  1896. broad-based exploit of iPhones “en masse” as described. The attack
  1897. affected fewer than a dozen websites that focus on content related
  1898. to the Uighur community. Regardless of the scale of the attack, we
  1899. take the safety and security of all users extremely seriously.</p>
  1901. <p>Google’s post, issued six months after iOS patches were released,
  1902. creates the false impression of “mass exploitation” to “monitor
  1903. the private activities of entire populations in real time,”
  1904. stoking fear among all iPhone users that their devices had been
  1905. compromised. This was never the case.</p>
  1907. <p>Second, all evidence indicates that these website attacks were
  1908. only operational for a brief period, roughly two months, not “two
  1909. years” as Google implies.</p>
  1910. </blockquote>
  1912. <p>Reading between the lines here, what Apple is pushing back on is the fact that Google’s report on this attack against the <a href="">Uyghur</a> community only mentioned iOS. Coverage of Google’s report created the impression that only iOS users were hacked, when in fact, <a href="">the Chinese government also exploited Windows and Android users</a>, and that these exploits may have been targeting people everywhere.</p>
  1914. <p>Conspicuously unmentioned in Apple’s response: “China”.</p>
  1916. <div>
  1917. <a  title="Permanent link to ‘Apple Pushes Back on iOS Security in Wake of Google’s Report’"  href="">&nbsp;★&nbsp;</a>
  1918. </div>
  1920. ]]></content>
  1921.  </entry><entry>
  1922. <title>Interesting Report From Barclays Analyst Blayne Curtis Back in May</title>
  1923. <link rel="alternate" type="text/html" href="" />
  1924. <link rel="shorturl" type="text/html" href="" />
  1925. <link rel="related" type="text/html" href="" />
  1926. <id>,2019:/linked//6.36013</id>
  1927. <published>2019-09-06T02:42:58Z</published>
  1928. <updated>2019-09-06T02:43:00Z</updated>
  1929. <author>
  1930. <name>John Gruber</name>
  1931. <uri></uri>
  1932. </author>
  1933. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1934. <p>This report from Barclays analyst Blayne Curtis back in May is interesting. He predicted both of the things Mark Gurman reported today: the return of Touch ID via an in-screen fingerprint sensor, and a new iPhone SE based on the iPhone 8.</p>
  1936. <div>
  1937. <a  title="Permanent link to ‘Interesting Report From Barclays Analyst Blayne Curtis Back in May’"  href="">&nbsp;★&nbsp;</a>
  1938. </div>
  1940. ]]></content>
  1941.  </entry><entry>
  1942. <title>Gurman Claims Touch ID Coming Back to iPhone With In-Screen Fingerprint Sensor</title>
  1943. <link rel="alternate" type="text/html" href="" />
  1944. <link rel="shorturl" type="text/html" href="" />
  1945. <link rel="related" type="text/html" href="" />
  1946. <id>,2019:/linked//6.36011</id>
  1947. <published>2019-09-05T22:43:17Z</published>
  1948. <updated>2019-09-05T22:43:19Z</updated>
  1949. <author>
  1950. <name>John Gruber</name>
  1951. <uri></uri>
  1952. </author>
  1953. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  1954. <p>Mark Gurman and Debby Wu, reporting for Bloomberg<sup>*</sup>:</p>
  1956. <blockquote>
  1957.  <p>Apple Inc. is developing in-screen fingerprint technology for as
  1958. early as its 2020 iPhones, according to people familiar with the
  1959. plans. The technology is in testing both inside Apple and among
  1960. the company’s overseas suppliers, though the timeline for its
  1961. release may slip to the 2021 iPhone refresh, said the people, who
  1962. asked not to be identified discussing private work. […]</p>
  1964. <p>The upcoming fingerprint reader would be embedded in the screen,
  1965. letting a user scan their fingerprint on a large portion of the
  1966. display, and it would work in tandem with the existing Face ID
  1967. system, the people familiar with Apple’s plans said.</p>
  1968. </blockquote>
  1970. <p>If true, I would guess this would be an optional way to increase security by requiring both Face ID <em>and</em> Touch ID authentication.</p>
  1972. <blockquote>
  1973.  <p>Apple is also working on its first low-cost iPhone since the
  1974. iPhone SE. That could come out as early as the first half of 2020,
  1975. the people said. The device would look similar to the iPhone 8 and
  1976. include a 4.7-inch screen. The iPhone 8 currently sells for $599,
  1977. while Apple sold the iPhone SE for $399 when that device launched
  1978. in 2016. The new low-cost phone is expected to have Touch ID built
  1979. into the home button, not the screen.</p>
  1980. </blockquote>
  1982. <p>The SE debuted about 6 months after the iPhone 6S, with the same A9 chipset. If Apple follows the same playbook, this new iPhone would have the A13 chip we expect to see in next week’s new iPhones — the iPhone 8 has an A11 that will soon be two years old. Makes a lot of sense — none of the X-class phones are going to drop to $400 in 2020, but it would be good for Apple and for users if there were a $400 iPhone with A13 specs. The only downside of this report is for people holding onto hope that Apple will make a new SE-sized phone with a 4-inch display. I would expect this rumored phone to look as much like an iPhone 8 as the SE looks like an iPhone 5S.</p>
  1984. <p><small>* Bloomberg, of course, is the publication that published “<a href="">The Big Hack</a>” last October — a sensational story alleging that data centers of Apple, Amazon, and dozens of other companies were compromised by China’s intelligence services. The story presented no confirmable evidence at all, was <a href="">vehemently denied</a> by <a href="">all companies</a> involved, <a href="">has not been confirmed by a single other publication</a> (despite much effort to do so), and has been <a href="">largely discredited by one of Bloomberg’s own sources</a>. By all appearances “The Big Hack” was complete bullshit. Yet Bloomberg has issued no correction or retraction, and seemingly hopes we’ll all just forget about it. I say we do not just forget about it. Bloomberg’s institutional credibility is severely damaged, and everything they publish should be treated with skepticism until they retract the story or provide evidence that it was true.</small></p>
  1986. <div>
  1987. <a  title="Permanent link to ‘Gurman Claims Touch ID Coming Back to iPhone With In-Screen Fingerprint Sensor’"  href="">&nbsp;★&nbsp;</a>
  1988. </div>
  1990. ]]></content>
  1991.  </entry><entry>
  1992. <title>Camera Sales Are Falling Sharply</title>
  1993. <link rel="alternate" type="text/html" href="" />
  1994. <link rel="shorturl" type="text/html" href="" />
  1995. <link rel="related" type="text/html" href="" />
  1996. <id>,2019:/linked//6.36010</id>
  1997. <published>2019-09-05T22:09:39Z</published>
  1998. <updated>2019-09-05T22:09:41Z</updated>
  1999. <author>
  2000. <name>John Gruber</name>
  2001. <uri></uri>
  2002. </author>
  2003. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  2004. <p>Om Malik:</p>
  2006. <blockquote>
  2007.  <p>Camera sales are <a href="">continuing</a> to falling off a cliff. The latest
  2008. data from the Camera &amp; Imaging Products Association (CIPA) shows
  2009. them in a swoon befitting a Bollywood roadside Romeo. All four big
  2010. camera brands — Sony, Fuji, Canon, and Nikon — are reposting
  2011. rapid declines. And it is not just the point and shoot cameras
  2012. whose sales are collapsing. We also see sales of higher-end DSLR
  2013. cameras stall. And — wait for it — even mirrorless cameras,
  2014. which were supposed to be a panacea for all that ails the camera
  2015. business, are heading south.</p>
  2016. </blockquote>
  2018. <p>Hard to overstate just how good camera phones are getting, and just how convenient it is for sharing to have them right there on your phone, immediately.</p>
  2020. <div>
  2021. <a  title="Permanent link to ‘Camera Sales Are Falling Sharply’"  href="">&nbsp;★&nbsp;</a>
  2022. </div>
  2024. ]]></content>
  2025.  </entry><entry>
  2026. <title>Twitter Is Finally Working on Search for DMs</title>
  2027. <link rel="alternate" type="text/html" href="" />
  2028. <link rel="shorturl" type="text/html" href="" />
  2029. <link rel="related" type="text/html" href="" />
  2030. <id>,2019:/linked//6.36009</id>
  2031. <published>2019-09-05T20:48:08Z</published>
  2032. <updated>2019-09-05T22:24:11Z</updated>
  2033. <author>
  2034. <name>John Gruber</name>
  2035. <uri></uri>
  2036. </author>
  2037. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  2038. <p>Jon Fingas, reporting for Engadget:</p>
  2040. <blockquote>
  2041.  <p>Twitter isn’t just launching a deluge of tests — it just
  2042. announced that a few sought-after features in the pipeline. Most
  2043. notably, it’s developing a long-overdue search for direct
  2044. messages. Although there aren’t many specifics at this point, it’s
  2045. reasonable to say this will spare you from digging through a
  2046. conversation to find a crucial message from days ago. The social
  2047. network added that it’s “re-energizing” its work on DMs, so this
  2048. is really just the highlight of a larger strategy.</p>
  2049. </blockquote>
  2051. <p>Weeks-old news but I didn’t see it until just now. The lack of any search at all for Twitter DMs makes iMessage search seem useful.</p>
  2053. <p>My experiment with leaving my DMs open to everyone on Twitter has been successful, by the way — very little spam, very high signal-to-noise from folks whom I don’t follow (who, if my DMs were not open, wouldn’t be able to DM me).</p>
  2055. <div>
  2056. <a  title="Permanent link to ‘Twitter Is Finally Working on Search for DMs’"  href="">&nbsp;★&nbsp;</a>
  2057. </div>
  2059. ]]></content>
  2060.  </entry><entry>
  2061. <title>Using the Command Key to Reveal Items in the Finder From Spotlight and the Dock</title>
  2062. <link rel="alternate" type="text/html" href="" />
  2063. <link rel="shorturl" type="text/html" href="" />
  2064. <link rel="related" type="text/html" href="" />
  2065. <id>,2019:/linked//6.36008</id>
  2066. <published>2019-09-05T15:46:52Z</published>
  2067. <updated>2019-09-06T22:37:58Z</updated>
  2068. <author>
  2069. <name>John Gruber</name>
  2070. <uri></uri>
  2071. </author>
  2072. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  2073. <p>Glenn Fleishman, writing at Macworld, “How to Open Items in the Enclosing Folder Directly From a Spotlight Search in macOS”:</p>
  2075. <blockquote>
  2076.  <p>One might think after many years of Spotlight search being in
  2077. macOS that there would be no new tricks. But a colleague on
  2078. Twitter asked a reasonable question and many people chimed in with
  2079. the same query: When viewing a list of results in a Spotlight
  2080. search in the Finder, how do you jump to see the item in the
  2081. context of its enclosing folder rather than just opening the file?</p>
  2083. <p>The answer is simple: hold down Command and press the Return key
  2084. or press Command-R. You can also hold down Command and
  2085. double-click the item in the results list.</p>
  2086. </blockquote>
  2088. <p>Using the Command key as a modifier to reveal items in the Finder while clicking has a long and consistent history on the Mac. You can also Command-click items in the Dock to reveal them rather than open them. (If you Command-Option-click a folder in the Dock it will open that folder, rather than reveal that folder in its parent folder.) Also useful: you can click on a folder in the Dock (Downloads is one I use this with frequently) and then Command-click on one of the items in the menu listing the folder’s contents. And in document-based apps, you can Command-click on the document’s proxy icon in the window’s title bar and you’ll get a pop-up menu showing the folder hierarchy of the document’s location in the file system. Select any of those folders and you’ll go to that folder in the Finder.</p>
  2090. <p><strong>Sidenote:</strong> From System 7 in 1991 through MacOS 10.13 High Sierra, ⌘R was also the shortcut for “Show Original” in the Finder. Select an alias (or symlink), hit ⌘R, and you’d see what the alias/symlink was pointing to. In MacOS 10.14 Mojave last year, some idiot at Apple changed the shortcut for “Make Alias” from ⌘L to ⌤⌘A and the shortcut for “Show Original” to ⌤⌥⌘A. Someone told me why this idiot made this change, but damned if I can remember or figure it out, because it doesn’t seem like the Finder in Mojave or Catalina uses ⌘R or ⌘L for anything else. Someone just decided to change 30-year-old shortcuts with no regard for muscle memory or consistency with other places where ⌘R reveals something in the Finder. (<a href="">Apple still has support documents with the old shortcuts</a>.)</p>
  2092. <p><strong>Update to Sidenote:</strong> Thanks to a few readers for reminding me — starting with 10.14 Mojave, ⌘R and ⌘L are now used for rotating images right and left. I couldn’t find the shortcuts because (a) they only work when an image file is selected, and (b) they don’t have commands in the Finder’s menu bar, another bit of UI lunacy.</p>
  2094. <p>And to top this all off — truly, this is genuinely hard to believe — these ⌘R and ⌘L shortcuts not only break 27-year-old Finder shortcuts, but they aren’t even consistent with Photos, <a href="/misc/2019/09/photos-rotate-shortcuts.png">which uses ⌘R for “Rotate Counterclockwise” and ⌥⌘R for “Rotate Clockwise”</a>. So in Photos the R maps to <em>R</em>otate not <em>R</em>ight, and the direction for an image rotated using ⌘R is <em>left</em>/counterclockwise. I don’t use the word lightly, but whoever pushed this change through for the Finder is an idiot.</p>
  2096. <p><strong>One More Update:</strong> There <em>is</em> some consistency to using ⌘L and ⌘R as shortcuts for “Rotate Left” and “Rotate Right” — those are the same command names and shortcuts that Preview uses. But there’s no reason Preview doesn’t use the same command names and shortcuts as Photos, and Photos’s use of “Clockwise” and “Counterclockwise” is, in my opinion, more clear than “Right” and “Left”. And, lastly, if you miss the longstanding use of ⌘L and ⌘R in the Finder for “Make Alias” and “Show Original”, <a href="/misc/2019/09/fixing-finder-alias-shortcuts.png">you can easily restore them manually in the Keyboards pane in System Preferences</a> — one of the great features of MacOS. You can also make custom shortcuts for the Finder’s “Rotate Left” and “Rotate Right” commands, even though they’re both hidden menu items.</p>
  2098. <p><strong>OK, OK, I Swear This One Really Is the Last Update:</strong> Another good Command-click trick — which dates back at least to System 7 in 1991, and possibly earlier — is that you can Command-click on any window in the background and drag it around <em>without bringing the window forward</em>. <strong>Update to the Last Update but I’m Not Breaking My Promise That There Would Be No More Updates Because I’m Not Putting This One in a New Paragraph:</strong> <a href="">My old friend Andrew Ross tweets</a> that Command-clicking to move and interact with background windows goes back at least to System 4 and perhaps to System 1.</p>
  2100. <div>
  2101. <a  title="Permanent link to ‘Using the Command Key to Reveal Items in the Finder From Spotlight and the Dock’"  href="">&nbsp;★&nbsp;</a>
  2102. </div>
  2104. ]]></content>
  2105.  </entry><entry>
  2106. <title>How a Haverford Student Came Close to Getting Trump’s Tax Returns</title>
  2107. <link rel="alternate" type="text/html" href="" />
  2108. <link rel="shorturl" type="text/html" href="" />
  2109. <link rel="related" type="text/html" href="" />
  2110. <id>,2019:/linked//6.36007</id>
  2111. <published>2019-09-05T15:36:32Z</published>
  2112. <updated>2019-09-05T15:43:33Z</updated>
  2113. <author>
  2114. <name>John Gruber</name>
  2115. <uri></uri>
  2116. </author>
  2117. <content type="html" xml:base="" xml:lang="en"><![CDATA[
  2118. <p>Sam Wood, reporting for The Philadelphia Inquirer:</p>
  2120. <blockquote>
  2121.  <p>In the days before the November 2016 election, two Haverford College students came within a hair’s breadth of prising Donald Trump’s tax returns from a government database.</p>
  2123. <p>Nearly three years later, the man who federal investigators believe masterminded the plan is pleading guilty. Andrew Harris, 24, is scheduled to admit on Thursday that he used a student financial aid site in a failed attempt to access Trump’s most-guarded financial documents.</p>
  2124. </blockquote>
  2126. <p>There are a couple of gems in this story, including Harris’s own attorney expressing regret for comparing his client and friend to Beavis and Butt-Head.</p>
  2128. <div>
  2129. <a  title="Permanent link to ‘How a Haverford Student Came Close to Getting Trump’s Tax Returns’"  href="">&nbsp;★&nbsp;</a>
  2130. </div>
  2132. ]]></content>
  2133.  </entry></feed><!-- THE END -->

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid Atom 1.0" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda