But first, I need to set low expectations for iOS 13, watchOS 6, and macOS Catalina updates this fall. Halfway through the summer, I’ve made much less progress than expected, having been overwhelmed by the required OS changes, my own technical and design debts, and unusually rough betas.
Rather than shipping a big iOS update, a standalone Watch app, and a Mac app on day one, these will probably come incrementally over the next year.
Fortunately, I haven’t stopped improving the app in the meantime.
Per-podcast customization, longer clips
You can now set download-vs.-stream and auto-delete behavior per podcast, one of the most frequently requested features over the last few years. (Sorry it took so long — it required a lot of server-side work for uninteresting reasons.)
I’ve also raised the clip-sharing length limit to 90 seconds. When I debuted this feature, I had to guess how it would be used and received, and 60 seconds seemed like a good limit. In practice, that’s sometimes a bit too short to capture a complete thought. 90 seconds should be better — most clips won’t need to be that long, but it’ll be nice to have the headroom when you need it.
“Suggestions for You” replacing Twitter
Overcast has had a Twitter-powered social-recommendations feature since version 1.0 in 2014, which made sense at the time: I didn’t have any popularity data to generate recommendations from, and social networks were nicer places to be than they are today.
But after five years, only 10% of active users have connected a Twitter account in Overcast, and only 0.2% of new podcast subscriptions have actually been added via Twitter recommendations.
Not only was the feature not providing much value to the 10% of people who enabled it, but the other 90% of Overcast’s customers haven’t been getting personalized recommendations at all.
In the meantime, I’ve accumulated five years of popularity data, so I tried writing my own recommendation engine. It worked — and it’s better.
Overcast now offers its own data-driven recommendation engine, and I’ve removed Twitter integration entirely.
Podcasts in the new “Suggestions for You” section of the Add Podcast screen are based on the shows you subscribe to, and what else their subscribers subscribe to, which gives much better recommendations without involving any social networks.
Most importantly, it works for all of Overcast’s customers.
Something big changed at Apple around the beginning of 2017.
They had encountered significant turbulence in the product line over the preceding years, especially Macs. It was a rough time to be a pro Mac user.
The “trash can” 2013 Mac Pro addressed only a fraction of the needs solved by the previous “cheese grater” towers, aged quickly without critical upgrade paths, and suffered from high GPU-failure rates from its cooling solution — all because its design prioritized size and appearance over performance and versatility in the one Mac model that should never make that tradeoff.
Over the next few years, it became clear that the Mac Pro was an embarrassing, outdated flop that Apple seemed to have little intention of ever updating, leaving its customers feeling unheard and abandoned. I think Apple learned a small lesson from it, but they learned a much bigger one a few years later.
The current MacBook Pro generation launched in late 2016, and I think Apple was truly caught completely by surprise when the new Touch Bar, sparse USB-C-only port offerings, high prices, and highly polarizing butterfly keyboard were met with harsh criticism, mixed reviews, and high failure rates. This one really hurt: while the Mac Pro is a niche machine for the highest-end and most-specialized needs, the popular MacBook Pro is the lifeblood of the Mac.
By the end of 2016, in addition to the generally buggy, neglected state macOS seemed to be perpetually stuck in, Apple had replaced its entire “pro” Mac lineup with controversial, limiting products that seemed optimized to flex Apple’s industrial-design muscles rather than actually addressing their customers’ needs.
The only company that can make computers for our OS seemed incapable of making good computers anymore. Each update threatened to remove or break things we needed or loved. Their newest designs felt punitive, rather than feeling like a celebration of computing.
Then, in April 2017, out of nowhere, Apple held a Mac Pro roundtable discussion with the press to announce that they were in the early stages of completely redesigning the Mac Pro.1
The follow-up briefing a year later promised that the new Mac Pro would be released in 2019, and publicized the existence of a “Pro Workflow Team” of real pro users working inside Apple to inform the direction of their pro hardware and software.
It sounded like they’d gone from not listening to their customers at all to an institutionalized process of listening. And the newly designed Macs released since then have been great.2
The late-2017 iMac Pro, which I’m using to write this, is the best Mac I’ve ever owned by far. It’s versatile, incredibly powerful, beautiful, and silent. It’s so good that I’ll probably never really need a Mac Pro again,3 and if this was the only new “Mac Pro”, I’d be mostly fine with that.
The late-2018 Mac Mini replaced a pitiful, punitive, neglected relic with a practical, powerful mini-Mac-Pro. Apple could’ve let it die, or replaced it with a tiny, no-port marvel of uselessness, but instead, they made a computer so good that I started and ended a YouTube mini-career just to review it.
And the 2019 Mac Pro, finally unveiled last week, looks to be absolutely killer — it’s the first true successor to the tower Mac Pro, which saw its last real update almost a decade ago in 2010.4 It’s big, bulky, ludicrously fast, and almost obscenely upgradeable — exactly what a Mac Pro needs to be, and far better than any of us expected.
The new Mac Pro is, truly, a celebration of computing.
Even more importantly than any hardware releases, macOS itself has also seen massive engineering effort recently. For the first time in a decade, the Mac was a major focus of WWDC, with great new APIs poised to usher in a huge wave of fresh software.
To be fair, this story hasn’t ended yet. The Mac Pro isn’t actually out yet (and will be very expensive), they still need to resolve the problematic MacBook Pro with its next generation (rumors are promising), and the lack of standalone Apple displays under six thousand dollars really hurts the Mac Pro story.5
But I’m optimistic for the first time in years.
It’s hard to tell when Apple is listening. They speak concisely, infrequently, and only when they’re ready, saying absolutely nothing in the meantime, even when we’re all screaming about a product line as if it’s on fire. They make great progress, but often with courageous losses that never get reversed, so an extended silence because we’re stuck with a change forever is indistinguishable from an extended silence because the fix isn’t ready yet.
But there has clearly been a major shift in direction for the better since early 2017, and they couldn’t be more clear now:
Apple is listening again, they’ve still got it, and the Mac is back.
Based on what we’ve learned since, they had likely started the project a very short time before holding the roundtable. ↩︎
I’m excluding the 2018 MacBook Air because it feels like a stopgap that wasn’t originally planned to exist — the no-Touch-Bar 13” MacBook “Escape” seemed intended to replace it — that was rushed into the 2016-era generation mid-cycle, rather than being the first of a new design. Even so, with the large exception of the butterfly keyboard, it’s quite good. ↩︎
The 2010/“2012” Mac Pro was so good, and so upgradeable, that it’s still in surprisingly widespread use today for needs that weren’t possible or compelling on the “trashcan” successor. ↩︎
And the MacBook Pro. A very common setup for developers — Apple’s largest identified segment of pro users — is a 15” MacBook Pro connected to an external monitor, for which a good solution no longer exists. Developers would be much better served by a $1,500-ish standalone version of the iMac’s 5K display than a $6,000 XDR reference monitor for professional video colorists. ↩︎
Sharing podcasts has never been easy, but I’ve always tried to lead the way with Overcast, with publicly shareable episode links and optional recommendations from your Twitter friends since version 1.0 in 2014.
Podcast sharing has been limited to audio and links, but today’s social networks are more reliant on images and video, especially Instagram. Podcasts need video clips to be shared more easily today.
I’ve seen some video clips from tools specific to certain podcast networks or hosts, but they were never available to everyone, or for every show. So people mostly just haven’t shared podcast clips, understandably, because it has been too hard.
With today’s 2019.4 update1, you can now share audio or video clips, up to a minute each, from any public podcast. Simply tap the share button in the upper-right corner.
You can generate an audio clip, or portrait, landscape, or square video, using your current Overcast theme setting.
In order to help spread podcasts further, I didn’t want to be heavy-handed in the Overcast branding — not everyone wants to advertise for one specific podcast app when promoting their shows. So the “Shared with Overcast” badge is optional, and if you’d like, you can also add an Apple Podcasts badge.
Finally, I wanted to extend the same app-agnosticism to Overcast’s share links. While this design still needs a lot of modernization, I’ve done a small refresh:
Now, for non-logged-in visitors, Overcast’s public sharing pages display badges for other podcast apps and the RSS feed for any podcast listed in Apple Podcasts.
It’s important for me to promote other apps like this, and to make it easy even for other people’s customers to benefit from Overcast’s sharing features, because there are much bigger threats than letting other open-ecosystem podcast apps get a few more users.
For podcasting to remain open and free, we must not leave major shortcomings for proprietary, locked-down services to exploit.2 Conversely, the more we strengthen the open podcast ecosystem with content, functionality, and ease of use, the larger the barrier becomes that any walled garden must overcome to be compelling.
One of the most common shortcomings we hear is that podcasts are hard to share. Hopefully, Overcast’s new clip-sharing feature changes that, and other apps build similar features soon.
So go get Overcast and start sharing your favorite moments. It’ll help me, of course, but more importantly, it’ll help your favorite shows gain listeners, and it’ll strengthen the amazing, open, standards-based world of podcasting.
Like Slopes and Castro, I’ve changed to a date-based version-numbering scheme — 2019.4 is the fourth update released in 2019, the next version will be 2019.5, and so on — partly because version numbers don’t really matter anymore, but mostly because I no longer wanted to delay completed features until a major-version change or worry that I didn’t do enough to justify a certain number. ↩︎
YouTube was able to dominate video because it made everything easy in a medium that (at the time) was very hard to do elsewhere. If a proprietary service takes a very hard aspect of podcasting and makes it very easy, it may rapidly rise to prominence.
Other major shortcomings I’m concerned about: the difficulty of getting sponsorships for small shows (“AdSense for podcasts”), and the complexity of creation and publishing (“Tumblr for podcasts”). This is probably why Spotify bought Anchor. ↩︎
The first thing someone does in a podcast app is add some podcasts, and most active Overcast users add at least two new podcasts each month.
Over 80% of podcasts are added to Overcast by searching, with the vast majority as searches for a specific podcast by name (rather than searching for generic keywords, such as “business”).
Good search is a critical, differentiating feature of any podcast app.
I’m not satisfied if the podcast you’re looking for is somewhere in the middle of a long list — I want it to be the first one, displayed quickly, after typing the fewest characters possible. I’ve been building toward this by analyzing years of popularity statistics and anonymous search data.
Instant Search is the next step in Overcast’s search evolution. It combines a small local cache with a highly optimized search service to give the most relevant results immediately as you type, even after only a single letter.1
It’s a dramatic, delightful improvement to a critical, frequently used feature. This was a lot of fun to build, and I’m proud of it.
Rather than try to be comprehensive, I focused on what matters most to me: size choice between the 11” and 12.9”, the Smart Keyboard Folio from my perspective as a frequent 10.5” Smart Keyboard user, the new Pencil, and why “getting work done” isn’t important to me.
I hardly ever think about my Mac Mini, but it serves a vital role for my family as our home-theater mixer, Plex server, ScanSnap server, Apple Photos backup, and Backblaze host for our NAS.1 Almost every port on the back is in use, and it runs 24/7, reliably, in total silence.
Until last week, I thought it would be the last Mac Mini that Apple ever made.
And when rumors started swirling about an imminent Mac Mini update, I assumed the worst: if it came at all, it would be a tiny box with a slow, ultra-low-power processor and almost zero ports, optimizing for small size instead of versatility.
I don’t think this was an unreasonable fear after the 2014 Mac Mini update, which made many key aspects much worse without making anything much better. It seemed clear then, and for the following four years that it went without an update, that Apple held the Mac Mini and its customers in very low regard.
The 2018 Mac Mini is real, and it’s spectacular.
It makes almost nothing worse and almost everything better, finally bringing the Mac Mini into the modern age.
Ports! Glorious ports!
Number one — and this is a big one these days, especially for this product — is that it’s not any less useful or versatile than the outgoing Mac Mini, including the generous assortment of ports. If the previous one served a role for you, the new one can probably do it just as well, and probably better and faster, with minimal donglage.2
It’s the same size as the old one, which is the right tradeoff. I know zero Mac Mini owners who really need it to get smaller, and many who don’t want it to get fewer ports or worse performance.
The point of the Mac Mini is to be as versatile as possible, addressing lots of diverse and edge-case needs that the other Macs can’t with their vastly different form factors and more opinionated designs. The Mac Mini needs to be a utility product, not a design statement. (Although, even as someone tired of space-gray everything, I have to admit that the Mini looks fantastic in its new color.)
The base price has increased to $800, and that’s not great. It’s partly justifiable because it’s much higher-end than before — the processors are much better, the architecture is higher-end and includes big advances like the T2, and all-SSD is standard — but it’s still an expensive product in absolute terms.
Apple lent me a high-end configuration for review — 6-core i7, 32 GB RAM, 1 TB SSD — which would cost $2499 (much of which is the SSD). This would’ve sounded crazy to spend on a Mac Mini a few years ago, but when it’s specced up like this, it’s targeting a much higher-end market than the previous model could. Compared to similarly specced iMacs and MacBook Pros, the pricing is generally reasonable.
And this can truly be a pro desktop, with just one exception.
The big story to me is how incredibly fast this thing is. Granted, I’m testing the fastest CPU offered, but damn.
Geekbench results are very strong. The i7 Mac Mini scored better on single-core performance than every other Mac today (!) at 5912, and its multi-core score of nearly 24,740 beats every Mac to date except the iMac Pro and the old 12-core 2013 Mac Pro.
“Performance-competitive with pro Macs” was not high on my prediction list for a Mac Mini update, but here we are.
As the rate of CPU advancement has slowed dramatically over the last few years, Apple has found other ways to improve performance. The T2 is great for lots of security reasons — I wouldn’t buy a new Mac these days without it — but what you’re seeing here is its strength as a ridiculously fast SSD controller.
This Mac Mini builds my app, Overcast, much faster than my maxed-out 13-inch MacBook Pro, and about as quickly as my 10-core iMac Pro! Obviously, to achieve this result with only 6 cores, it’s not maxing out the CPU 100% of the time — it hits it in bursts while juggling a lot between the SSD and memory — but the result is that it’s incredibly fast as a development machine.
The Blackmagick Disk Speed Test shows that the raw SSD performance is effectively identical to the other T2 Macs shipped to date, and a huge improvement over the four-year-old Mac Mini.
A lot of people use Mac Minis as media or Plex servers, so I ran an H.265 transcoding test with ffmpeg. This maxes out all CPU cores, so the results predictably scale with the core count: the 6-core Mac Mini was much faster than the 4-core MacBook Pro, but the 10-core iMac Pro beat them both.
But if an app supports the T2’s hardware HEVC encoder,3 it can go much faster. And since every T2 so far performs identically, all T2 machines — from the 2018 MacBook Air to the iMac Pro — encode HEVC this way at the same speed, and all in complete silence because they’re barely touching the CPU.
I wasn’t able to notice any quality differences between the videos encoded with x265 and the T2’s hardware acceleration.
The only spec that lets it down is the Intel GPU. It’s fast enough for common tasks, but if your workload benefits from a strong GPU, you’re better off going for an iMac or a 15-inch MacBook Pro, or considering an eGPU setup.
Many Mac lines rely on Intel’s integrated GPUs to fit their physical and thermal needs, and Intel has been incredibly inconsistent over the last few years in delivering updated CPU-GPU combinations that would be suitable for many Macs.
We often blame Intel’s CPU roadmap (or Apple’s seeming indifference) for the lack of updates to certain Mac lines, but Intel’s GPU offerings are often the bigger issue. This is Intel’s fault, but it’s Apple’s problem — and Apple passes that problem right along to its customers.
But that’s it — aside from price, that’s the only downside. The GPU sucks. Everything else is awesome.
If you don’t need a strong GPU — and honestly, most Mac Mini use-cases don’t — this is a solid pick for a general-purpose Mac, even at the base-level configuration. Spec it up, and it’s more like a mini-Mac Pro.
A few assorted notes, with apologies for stealing Gruber’s format:
It’s silent at idle. The i7’s fan noise does become clearly audible when it’s under heavy load: it’s in the ballpark of a modern MacBook Pro, but quieter.
Interestingly, I disabled Turbo Boost to simulate the base i3 model’s thermals, and couldn’t get the fan to spin up audibly, no matter what I did. Those who prioritize silence under heavy loads should probably stick with the i3.
This is the first non-iMac desktop Mac that lets you plug in a 5K display, at full quality, without dual cables or other unreliable hacks. We finally have 5K Retina Mac options beyond the iMac! Unfortunately, we still don’t have any great standalone 5K displays. (The LG UltraFine isn’t.)
You can upgrade the RAM again! I never would’ve guessed this was coming, and I believe it’s the first time in a long time that an Apple product’s direct successor became more upgradeable and serviceable.
I still recommend getting it with the right amount of RAM from Apple if possible, since third-party RAM has historically been a mess of unreliability and finger-pointing, but if you need that, it’s back. (The security screws inside — TR6? — still need some iFixit tools to get past.)
I Can’t Believe The Mac Mini Is This Awesome, I Can’t Even Say “Again” Because It Never Was
A new Mac Mini could’ve been so much worse. At many times in its past, it has seemed unloved, neglected, and downright punitive — a similar pattern to Apple’s other headless desktop, the Mac Pro. It seemed for a while that Apple lacked any interest in making Macs anymore, especially desktops.
Last year, with the introduction of the absolutely stellar iMac Pro, Apple showed us a glimpse of a potential new direction. It was downright perfect — a love letter to the Mac and its pro desktop users, and a clear turnaround in the way the company views the Mac for the better.
We didn’t know until now whether the iMac Pro’s greatness was a fluke. But now we have another data point: the last two desktops out of Apple have been incredible. After this, I have faith that they’re going to do the new Mac Pro justice when it finally ships next year.
The new Mac Mini is a great update, out of nowhere, to a product we thought would never be updated again.
Of course, with Apple’s track record on the Mac Mini, it may never be updated after this. This is either the first in a series of regular updates with which Apple proves that they care about the Mac Mini again, or it’s the last Mac Mini that will ever exist and we’ll all be hoarding them in a few years. We can’t know yet.
But today, this is a great update, a wonderful all-arounder for lots of potential needs, and just a fantastic little computer.
I do this via iSCSI, but I wouldn’t recommend it. It breaks and requires a new $200+ iSCSI initiator with almost every macOS update — which is why my Mac Mini still runs Sierra. In the near future, I’ll just directly attach some giant external hard drives to the Mac Mini and stop using the NAS. ↩︎
Unless you used optical audio, audio input, or the SD-card reader. (Shit, I use optical in and out.) ↩︎
ffmpeg can do it by specifying -c:v hevc_videotoolbox instead of -c:v x265. I also needed -vtag hvc1 for the output MP4s with either codec to be playable on macOS.
Compressor uses the T2’s HEVC acceleration when encoding 8-bit HEVC, but not 10-bit. ↩︎
I’ve configured mine acceptably, but Utility is still far more legible for telling the time at a quick glance:
Infograph suffers from two major issues:
The center complications reduce the contrast between the dial and hands, often making the hands hard to locate. This is avoidable with customization, although the defaults should be much more conservative.
It takes too much cognitive effort (and therefore time) to distinguish the current hour. This is simply a flawed design.
It’s faster and easier to read analog time with the 1–12 numerals displayed on a watch, but many people prefer the cleaner look of a watch that uses lines, dots, or other shapes as hour markers instead. (Watch people call these “indices”.)
And it’s absolutely possible to design a highly legible dial with hour indices in many different styles. Here are some classics and modern takes:1
Across a wide variety of brands, styles, and price points, a few key design principles are clear:
The hour markers for 12 (and often 3/6/9) are more prominent.
The hour indices are much larger than the minute markings.
The hour hands nearly touch the hour indices.
These all improve legibility by making it as fast and easy as possible to know which hour is being indicated (and minimize the chance of an off-by-one error), first by orienting your eyes to the current rotation with the 12 marker, then by minimizing the distance between the hour hand and the indices it’s between.
Apple Watch’s analog faces all fail to achieve these principles:2
Color, Simple, Explorer
Color, Simple, and Explorer have easily distinguished hour markers, but Explorer’s are a bit too far from its hour hand.
None of them have distinguished 12 markers to aid in orientation.
While Explorer omits minute markings altogether, Simple bafflingly uses 30-second markings in place of its minute track, making time-telling even harder. I’ve never seen another watch with sub-minute markings identical to its minute markings.
Activity Analog, Utility, and Infograph without most complications
Activity Analog’s hour markers are faint and far from its hour hand, and the central activity rings quickly eliminate the hands’ contrast against the dial as they progress.
Utility (when configured without numbers) improves legibility slightly with its bold hour indices, but they’re still too small and too far from its hour hand, and there’s no differentiation for the 12 index.
Infograph is similar, but even worse: its hour indices are more faint, it uses 30-second markings instead of minute markings, and its default Calendar display wipes out the top three indices. (At least you can tell which way is up.)
Even with almost no complications, the basic essence of the Infograph dial has poor time legibility.
When it’s being used as Apple seems to intend, time-telling at a glance is so difficult that many people have actually suggested setting the digital time as the center complication, at which point the hands are just a nuisance and we should stop pretending it’s an analog face.
It’s great for Apple to offer a wide variety of Apple Watch faces, but most of them are short-lived novelties at best. We’re three years and four generations into the Apple Watch, and almost every Watch owner I know still uses the same handful of “good” faces.
If you want digital time with a good deal of complications, Modular is your only good choice (or Infograph Modular on the Series 4).3 If you want analog time with numerals, Utility is the only good option. If you want indices instead of numerals — probably the most popular analog watch style in the world — I don’t think there is a good option.
By now, we’ve seen Apple’s design range that they’re willing to ship as Watch faces, and while it seems broad at first glance, it’s actually pretty narrow.
And we’re restricted to the handful of good watch faces that Apple makes, because other developers aren’t allowed to make custom Watch faces.
The Apple Watch is an amazing feat of technology. It’s a computer. It can display anything. With no mechanical or physical limitations to hold us back, any watch-face design from anyone could plausibly be built, enabling a range of creativity, style, and usefulness that no single company could ever design on its own.
But they won’t let us. In a time when personal expression and innovation in watch fashion should be booming, they’re instead being eroded, as everyone in the room is increasingly wearing the same watch with the same two faces.
After a very busy summer, standalone Apple Watch playback is back in Overcast, and it’s actually good this time!
It’s not perfect:
No cellular. Apple hasn’t released a good way to do cellular audio streaming in watchOS, and the bad ways wouldn’t be very useful.
Sending podcasts to the Watch is slow. Overcast shrinks them to reduce the transfer time, but when (and how quickly) podcasts transfer is tightly controlled by watchOS to preserve battery life. Transfers still sometimes wait forever or silently fail.
Programmers like me can’t accept that something is just slow, so I’ve decided to make transfer speed irrelevant. Nobody cares how slowly podcasts transfer if it happens while they’re asleep!
Auto-Sync to Watch automatically tries to send your most recent podcasts to your Apple Watch whenever it gets a chance.1 You can still send episodes manually from the queue button on an episode (≡+), but in my testing, I never needed to. Just pick up your Watch and go, and it’ll already have plenty of podcasts for your outing, all without having to manually sync anything or wait for slow transfers.
The Overcast 5.0.1 update, due out in a few days, makes Watch transfers even more reliable. (Sorry. Found a better way after 5.0 was approved.)
And Watch-crown volume control! Finally, the best way to use Overcast from your Apple Watch isn’t to delete it, letting the Now Playing app show up instead.
That’s where the other half of my summer workload began.
The watchOS volume widget offers minimal customization: just the color of the circle. I couldn’t make the line width a little narrower to match the rest of Overcast’s thin-line aesthetic. But that iOS 7-era thin-line aesthetic looked dated, and I’d wanted a design refresh for a while.
I decided to start modernizing the app’s design, screen by screen. I couldn’t do it all in one summer, so I started with the screen that needed the most help: Now Playing.
The previous Now Playing screen in Overcast 4.
The biggest problem of the previous design was the center artwork area, a scrollable set of “pages” that had speed and effects controls offscreen to the left, and the episode notes offscreen to the right.
Nobody ever found them. I’ve been getting emails almost every day from people asking where the speed controls were because they set them once and couldn’t find them again, or saying how they’d really like my app more if it offered speed controls. The only indication in the interface was three “page dots” below the scrollable area, but that wasn’t enough.
The new design maintains the same scrollable pages, but now as obvious, tactile cards. In my testing, everyone figured these out immediately.
Put differently, it’s like you’re navigating this through a phone-shaped window in the middle:
This design is not only more discoverable, but it allows me to fit more controls on screen, and in more reachable areas. Unlike the previous design, I can also fit the same controls on all devices, from the iPhone SE to the iPad Pro.
Designing a good Now Playing screen for a music or podcast app that’s nice, clean, and highly discoverable is incredibly difficult. I think I’ve finally found a good balance.
I’ve given chapters (when present) their own card with durations and inline progress bars. I’ve also finally revamped the sleep timer to ditch the ugly alert sheet, give it a proper UI for fast input, and show the remaining time in more useful ways:
There are lots of other improvements throughout the app as well. Some of the highlights:
Search your podcasts and current episodes from the main screen, or go into a podcast’s screen to search its entire archive.
Refreshed the podcast screen a little. (More to come.)
Siri Shortcuts support, of course.
Plus smaller fixes and improvements:
CarPlay performance is much better, especially for people with large collections.
Podcasts now display their estimated release frequency (daily, weekly, etc.) if it can be inferred.
Laptop battery life is decreasingly relevant to me as more airplanes offer power outlets. But sometimes you lose that lottery, as I did on my latest 8-hour daytime flight.
Apple’s “Up to 10 hours” claim doesn’t apply to my work,1 which is usually a mix of Xcode, web browsing, and social time-wasting, so I knew I’d have to seriously conserve power.
Sometimes, you just need Low Power Mode: the switch added to iOS a few years ago to conserve battery life when you need it, at the expense of full performance and background tasks.
There’s no such feature on Mac laptops, but there should be. It could:
Disable the discrete GPU on 15-inch models unless required for hardware reasons2
Pause Photos syncing and analysis
Pause Spotlight indexing
Reduce the frequency of Time Machine backups
Don’t download or install software updates
Don’t download new content in iTunes
Auto-dim the screen after a shorter time
Let third-party apps detect Low Power Mode and reduce their background operations to only essential work
And the big one:
Reduce the processor’s maximum wattage or disable Turbo Boost
Back in 2015, I experimented with disabling Turbo Boost and discovered that it reduced performance by about a third, but also boosted battery life by almost as much. Since then, I’ve been running Turbo Boost Switcher Pro to automatically disable Turbo Boost when I’m running on battery power, and it has been wonderful: I made it through that 8-hour flight only because Turbo Boost was off.
Over the last few days, I’ve run battery tests on my 2018 13-inch MacBook Pro with the (awesome) 2.7 GHz i7 and my 2015 2.2 GHz 15-inch3 to see how far I could push the battery life using Volta, which can disable Turbo Boost and/or set wattage limits on the CPU.
My test was based on the “Heavy” script from last time, but using xcodebuild every few minutes with Overcast’s current codebase (which is larger and includes some Swift). Improvements are in green and performance reductions are in red:
15-inch 2015 MacBook Pro (2.2 GHz quad-core i7)
13-inch 2018 MacBook Pro (2.7 GHz quad-core i7)
It’s impressive how much faster this new 13-inch model is than the best laptop ever made due to significant CPU and SSD improvements.
Dropping the wattage to 6W, the thermal limit of the fanless 12-inch MacBook, interestingly (but not surprisingly) makes it perform effectively identically to the best 12-inch MacBook in Geekbench. This is an extreme option, but one I’d occasionally take if offered. It roughly doubles compilation times, but also doubles the battery life.
This ratio holds for most other configurations: the gain in battery life is about as large as the loss in heavy-workload performance. That’s a trade-off I’d gladly make when I need to maximize runtime.
The best bang-for-the-buck option is still to just disable Turbo Boost. Single-threaded performance hurts more than with wattage-limiting, but it’s able to maintain better multi-threaded performance and more consistent thermals, and gets a larger battery gain relative to its performance loss.
And Volta, which offers both wattage limits and Turbo disabling, requires disabling System Integrity Protection to install an unsigned kernel extension, which I really don’t recommend. Turbo Boost Switcher, which doesn’t offer wattage control, works with SIP using a signed extension and its Pro version has more convenient features for automatic toggling.
For now, I’m going to continue to happily run Turbo Boost Switcher Pro to selectively give myself better battery life, and I recommend it for anyone else with the same need.
But what I ultimately want is for a true Low Power Mode built into macOS that could provide this sort of CPU throttling and software changes, which would ultimately achieve even greater gains.
Whose work does get 10 hours out of a MacBook Pro? None of the use-cases on the marketing page — Photography, Coding, Video Editing, 3D Graphics, and Gaming — are likely to achieve even half of that in practice. ↩︎
I’ve heard that 15-inch models are wired such that the discrete GPU is required when external displays are connected. Otherwise, whether it’s used or not is a software decision, and gfxCardStatus can override it in certain conditions. ↩︎
It’s not brand new, so it’s not a perfect comparison, but the battery only had 90 cycles before this test. ↩︎
Overcast has offered anonymous sync accounts since 2014. They’re fully functional, but they lack email addresses or passwords, so they can’t log into the website. A login token is stored in iCloud so the account can be accessed after a restore or upgrade, or from other devices you own.
Previously, the login screen pushed email logins. But with four years of perspective, feedback, and usage data, I now think that’s the wrong move. Only a single-digit percentage of customers use the website, and the iCloud token-sync method solves cross-device logins for almost everyone.
Your personal data isn’t my business — it’s a liability. I want as little as possible. I don’t even log IP addresses anymore.
If I don’t need your email address, I really don’t want it.
68% of Overcast accounts have email addresses today. To reduce that as much as possible, I’ve made major changes to account handling:
The previous login screen (left) and the new one.
In Overcast 4.2, the login screen now prominently encourages anonymous accounts by default.
If you already have an account in iCloud, it’ll pop up a dialog box over this screen asking if you want to use it.
And the first time you launch 4.2, people with email-based accounts will be encouraged to migrate them to anonymous accounts:
The migration prompt that shows on the first run.
Finally, you can now change your account between email-based and anonymous whenever you want.
Blocking ad-tracking images
In most podcast apps, podcasts are downloaded automatically in the background. The only data sent to a podcast’s publisher about you or your behavior is your IP address and the app’s name. The IP address lets them derive your approximate region, but not much else.
They don’t know exactly who you are, whether you listened, when you listened, how far you listened, or whether you skipped certain parts.
Some large podcast producers are trying very hard to change that.
Big data ruined the web, and I’m not going to help bring it to podcasts. Publishers already get enough from Apple to inform ad rates and make content decisions — they don’t need more data from my customers. Podcasting has thrived, grown, and made tons of money for tons of people under the current model for over a decade. We already have all the data we need.
One of the ways publishers try to get around the limitations of the current model is by embedding remote images or invisible “tracking pixels” in each episode’s HTML show notes. When displayed in most apps, the images are automatically loaded from an analytics server, which can then record and track more information about you.
In Overcast 4.2, much like Mail (and for the same reason), remote images don’t load by default. A tappable placeholder shows you where each image will load from, and you can decide whether to load it or not.
Overcast 4.2 also includes a bunch of minor fixes, and two big ones:
Fixed the major slowdowns and high battery usage that resulted from extremely large podcast artwork.
Password-protected episodes are now supported on password-protected feeds.
It jumps back by up to a few seconds after having been paused to help remind you of the conversation.
It slightly adjusts resumes and seeks to fall in the silences between spoken words when reasonably possible.
Both are subtle but noticeable benefits (my favorite kind), especially when you’re being interrupted a lot, such as while following turn-by-turn navigation directions.
Smart Resume is on by default, and can be turned off in Nitpicky Details.
Delete episodes 24 hours after completion: Before, episodes could either be auto-deleted immediately upon completion, or not at all. There’s now a third option, auto-deleting 24 hours after completion, which will soon be the default for new accounts.
The 24-hour threshold is only enforced after a successful sync, so it won’t auto-delete anything in the middle of an extended offline period, such as a long flight.
Auto-deletion, either immediate or after 24 hours, also no longer applies to Premium subscribers’ Uploads.
Password-protected podcasts: Some private podcast feeds, including many paid and members-only podcasts, require a username and password via HTTP Basic Auth. You can now add these in the Add URL screen.
Password-protected podcasts, and other private feeds such as Patreon bonus feeds and anything using the <itunes:block> tag, do not show up in search or recommendations.
Noteworthy bug fixes:
Resuming playback after quitting in the background, especially on very long podcasts and/or when using AirPods, no longer occasionally results in glitchy noises and incorrect durations.
Playback under certain conditions no longer stalls, requiring pausing and playing again.
Downloads now fail less often.
Playback controls no longer disappear occasionally.
Smart Speed total savings now appear at the bottom of the Settings screen for locales that use commas as their decimal separator.1
Extremely large playlists now only show the most/least-recent 500 episodes to improve app performance for users with very high subscription counts.
There’s also one removal: rotation support on iPhone. (The iPad app still rotates.) iPhone rotation has always been disabled by default, and had been buried in Nitpicky Details for a long time, so very few people have ever used it. Meanwhile, it has become increasingly difficult to support and maintain, especially with the modern complexities of rotation and the dramatically increased workload of supporting the iPhone X in landscape.
iPhone rotation has simply proven far too costly to maintain for its extremely low usage, and it had to go to free up more of my time for more highly demanded features. I apologize to the few people who did use it, and I hope this isn’t too disruptive for you.
In the next update, I’ll be addressing the biggest design failure of Overcast 4: the non-discoverability of the Effects and Notes pages in the Now Playing screen. Expect the return of an ancient user-interface tool known as “buttons”.
This was Overcast’s oldest known bug, which had been there since 1.0: some users, mostly in central Europe, wouldn’t see Smart Speed totals. It turned out to be one of the most interesting and obscure bugs I’ve seen.
The total-time-saved value is stored on-device as it accumulates, then gets sent to the server to be combined with any listening you do on other devices. The overall total is read back from the server, and the local total is reset, on each sync.
I was using an NSNumberFormatter to read the total value from Overcast’s server as a double. My server always sends values with U.S.-style number formatting, using a period as the decimal separator (e.g. “1234.5”). But by default, NSNumberFormatter uses the device’s locale, so in countries that use a comma as the decimal separator (e.g. “1234,5”), it was interpreting the server’s numbers with periods as invalid and returning zero. So the Settings screen thought they hadn’t saved any time, and hid the time-saved label.
Fortunately, it was an easy fix: setting that NSNumberFormatter locale to en_US to match what the server was sending. And since the accumulated local totals were still being sent and added properly, the correct historical data is there — it just wasn’t being displayed correctly. ↩︎
In the original 2007 iPhone introduction, Steve Jobs famously derided other smartphones at the time for running “baby” software and the “baby” internet. He was right.
Developers weren’t given access to make native apps until the iPhone’s second year. Before the native development kit was ready, Apple tried to pass off web apps as a “sweet solution” for third-party apps, but nobody was fooled.
Apple wasn’t using web apps for their own built-in iPhone apps — they were using native code and frameworks to make real apps.1 Developers like me did our best with web apps, but they sucked. We simply couldn’t make great apps without access to the real frameworks.
Apps were terrible, and didn’t take off, until we had access to the same native tools that Apple used.
* * *
Developing Apple Watch apps is extremely frustrating and limited for one big reason: unlike on iOS, Apple doesn’t give app developers access to the same watchOS frameworks that they use on Apple Watch.
Instead, we’re only allowed to use WatchKit, a baby UI framework that would’ve seemed rudimentary to developers even in the 1990s. But unlike the iPhone’s web apps, WatchKit doesn’t appear to be a stopgap — it seems to be Apple’s long-term solution to third-party app development on the Apple Watch.
The separation of Apple’s internally-used frameworks from WatchKit has two huge problems:
Apple doesn’t feel WatchKit’s limitations. Since they’re not using it, it’s too easy for Apple’s developers and evangelists to forget or never know what’s possible, what isn’t, what’s easy, and what’s hard. The bugs and limitations I report to them are usually met with shock and surprise — they have no idea.
WatchKit is buggy as hell. Since Apple doesn’t use it and there are relatively few third-party Watch apps of value, WatchKit is far more buggy, and seems far less tested, than any other Apple API I’ve ever worked with.2
Apple will never have a very good idea of where WatchKit needs to improve if they’re not using it. But this sweet solution is the only choice anyone else has to make Apple Watch apps.
WatchKit only lets us create “baby” apps. That’s all it will ever let us create.
WatchKit needs to be discontinued and replaced.
No focus on quality or expansion of WatchKit will fix this. There are only two ways to meaningfully improve Watch apps, spur third-party innovation, and unlock the true potential of the Apple Watch.
One solution is for Apple to reimplement all of its own Watch apps with WatchKit instead of their internal frameworks, which will force them to fix WatchKit’s many bugs and dramatically expand it.
The much better solution, and the one I hope they take, is for Apple to expose its real watchOS UI and media frameworks to third-party developers, as it has done on iOS.
Defensive web developers who object to my “real” classification, remember this was 2007 hardware with 2007 cellular speeds and 2007 browser capabilities. You don’t realize how good you have it today. (But most apps should still be native.) ↩︎
Here’s one from today for WKAudioFilePlayer, an abysmal, demoralizing API that I lost weeks of my life battling that feels like it had literally zero testing at Apple. I’d bet money that nobody at Apple has ever tried to build an app with it. ↩︎
App developers sometimes ask me what they should do when their features, designs, or entire apps are copied by competitors.
Legally, there’s not a lot you can do about it:
Copyright protects your icon, images, other creative resources, and source code. You automatically have copyright protection, but it’s easy to evade with minor variations.1 App stores don’t enforce it easily unless resources have been copied exactly.
Trademarks protect names, logos, and slogans. They cover minor variations as well, and app stores enforce trademarks more easily, but they’re costly to register and only apply in narrow areas.2
Only assholes get patents. They can be a huge PR mistake, and they’re a fool’s errand: even if you get one ($20,000+ later), you can’t afford to use it against any adversary big enough to matter.
Don’t be an asshole or a fool. Don’t get software patents.
If someone literally copied your assets or got too close to your trademarked name, you need to file takedowns or legal complaints, but that’s rarely done by anyone big enough to matter. If a competitor just adds a feature or design similar to one of yours, you usually can’t do anything.
You can publicly call out a copy, but you won’t come out of it looking good:
If they’re more successful than you, it’s envy and sour grapes.
If they’re less successful than you, it’s jealousy and punching down (and giving them attention!).
The public may have a very different opinion on whether you’re really being copied from, whether you were really the first to do it, or whether you deserve to “own” it.
These disputes are best kept private, or not fought at all.
Nobody else will care as much as you do. Nobody cares who was first, and nobody cares who copied who. The public won’t defend you.
The instant someone else has the same feature or design as you, the public and press see it as a collective checkbox feature, or a “standard” or “obvious” design, that apps in this category just have. It’s no longer yours.
You can try to “educate” the public, but you’ll lose.
This feels unfair when it happens to you, but it’s just how it goes, and the entire ecosystem benefits. Every app — even yours — includes countless “standard” and “obvious” features and designs that, at one time, weren’t. Everything is a remix.
A great design or feature can give you a competitive advantage for a little while, but it’s always temporary. Compete on marketing, quality, and what you can do next, not the assumption that nobody can copy what you made.
Setting the roadmap for competitors is a satisfying accomplishment, but only a personal one. You know you’ve done it. That has to be enough.
For instance, nobody else can make an app that uses Overcast’s exact icon, or anything clearly derivative of it, but I can’t stop anyone from making a different-looking, originally-drawn orange icon with a radio tower in it. ↩︎
For instance, nobody else can make an audio player named Overcast or anything similar to it, but I can’t stop anyone from making a weather app with that name. And other podcast players can’t make features named Smart Speed or Voice Boost, but I can’t stop them from making similar features with different-enough names. ↩︎
Having attended (and sometimes spoken at) many of these conferences over the years, I can’t deny the feeling I’ve had in the last couple of years that the era of the small Apple-ish developer-ish conference is mostly or entirely behind us.
I don’t think that’s a bad thing. This style of conference had a great run, but it always had major and inherent limitations, challenges, and inefficiencies:
Cost: With flights, lodging, and the ticket adding up to thousands of dollars per conference, most people are priced out. The vast majority of attendees’ money isn’t even going to the conference organizers or speakers — it’s going to venues, hotels, and airlines.
Size: There’s no good size for a conference. Small conferences exclude too many people; big conferences impede socialization and logistics.
Logistics: Planning and executing a conference takes such a toll on the organizers that few of them have ever lasted more than a few years.
Format: Preparing formal talks with slide decks is a massively inefficient use of the speakers’ time compared to other modern methods of communicating ideas, and sitting there listening to blocks of talks for long stretches while you’re trying to stay awake after lunch is a pretty inefficient way to hear ideas.
It’s getting increasingly difficult for organizers to sell tickets, in part because it’s hard to get big-name speakers without the budget to pay them much (which would significantly drive up ticket costs, which exacerbates other problems), but also because conferences now have much bigger competition in connecting people to their colleagues or audiences.
There’s no single factor that has made it so difficult, but the explosion of podcasts and YouTube over the last few years must have contributed significantly. Podcasts are a vastly more time-efficient way for people to communicate ideas than writing conference talks, and people who prefer crafting their message as a produced piece or with multimedia can do the same thing (and more) on YouTube. Both are much easier and more versatile for people to consume than conference talks, and they can reach and benefit far more people.
Ten years ago, you had to go to conferences to hear most prominent people in our industry speak in their own voice, or to get more content than an occasional blog post. Today, anyone who could headline a conference probably has a podcast or YouTube channel with hours of their thoughts and ideas available to anyone, anywhere in the world, anytime, for free.
But all of that media can’t really replace the socializing, networking, and simply fun that happened as part of (or sometimes despite) the conference formula.
I don’t know how to fix conferences, but the first place I’d start on that whiteboard is by getting rid of all of the talks, then trying to find different ways to bring people together — and far more of them than before.
Or maybe we’ve already solved these problems with social networks, Slack groups, podcasts, and YouTube, and we just haven’t fully realized it yet.
There’s a lot to like about the new MacBook Pros, but they need some changes to be truly great and up to Apple’s standards.
Here’s what I’m hoping to see in the next MacBook Pro that I believe is technically possible, reasonable, widely agreeable, and likely for Apple to actually do, in descending order of importance:
Butterfly keyswitches are a design failure that should be abandoned. They’ve been controversial, fatally unreliable, and expensive to repair since their introduction on the first 12” MacBook in early 2015. Their flaws were evident immediately, yet Apple brought them to the entire MacBook Pro lineup in late 2016.
After three significant revisions, Apple’s butterfly keyswitches remain as controversial and unreliable as ever. At best, they’re a compromise acceptable only on the ultra-thin 12” MacBook, and only if nothing else fits. They have no place in Apple’s mainstream or pro computers.
The MacBook Pro must return to scissor keyswitches. If Apple only changes one thing about the next MacBook Pro, it should be this. It’s far more important than anything else on this list.
Fans of the butterfly keyboard’s feel need not worry — this doesn’t mean we need the old MacBook Pro keyboard, exactly.
The Magic Keyboard’s scissor switches feel similar, but with a bit more travel, and all of the reliability and resilience of previous keyboard generations. They’re a much better, more reliable, and more repairable balance of thinness and typing feel likely to appeal to far more people — even those who like the butterfly keyboards.
The Magic Keyboard only needs one change to be perfect for the MacBook Pro: returning to the “inverted-T” arrow-key arrangement by making the left- and right-arrow keys half-height again. This arrangement is much more natural and less error-prone because we can align our fingers by feeling the “T” shape, a crucial affordance for such frequently used keys that are so far from the home row.
Great first-party USB-C hubs
The MacBook Pro bet heavily on the USB-C ecosystem, but it hasn’t developed enough on its own.
When people can’t get what they need from Apple at all, or at a remotely competitive price, they’ll go to cheap third-party products, which are often unreliable or cause other problems. When these critical accessories aren’t flawless, it reflects poorly on Apple, as it harms the overall real-world experience of using these computers.
If a third-party hub or dongle is flaky, the owner doesn’t blame it — they blame their expensive new Apple computer for needing it.
Apple needs to step up with its own solid offerings to offer more ports for people who need them.
Apple’s most full-featured USB-C accessory is downright punitive in its unnecessary minimalism: one USB-C passthrough, one USB-A (a.k.a. regular/old USB), and an HDMI port that doesn’t even do 4K at 60 Hz — all for the shameless price of $80.
Instead of giving us the least that we might possibly need, this type of product should give us the most that can fit within reasonable size, cost, and bandwidth constraints. I’d like to see at least two USB-C ports, at least two USB-A ports, and HDMI that can do 4K60. An SD-card reader would be a nice bonus.
To make it easier to go all-USB-C on our peripherals and cables, I’d also like to see a true USB-C hub: one USB-C in and at least three USB-C out, with power passthrough on one.
And just as we learned that the need for pro displays shouldn’t be outsourced to LG, Apple should stop outsourcing critical adapters and hubs to Belkin. They’re not as good as Apple’s, and they never will be.
USB-C is great, but being limited to 2 or 4 total ports (including power) simply isn’t enough. Even if you adopt the USB-C ecosystem, these MacBook Pros are more limited than their predecessors:
The 13” MacBook Air can connect to power, two USB devices, Thunderbolt, and an SD card simultaneously. Its replacement, the 13” MacBook “Escape” (without Touch Bar), can only connect to two total devices on battery, or one when powered.
The 2015 13” and 15” MacBook Pros can connect to power, two USB devices, two Thunderbolt devices, HDMI output, and an SD card simultaneously. Their replacements can only connect to four devices on battery, or three when powered.
If there’s not enough Thunderbolt or PCIe bandwidth to have more USB-C ports, that’s fine — not every port needs to be USB-C with Thunderbolt. All of that cost and bandwidth is unnecessary for most common real-world uses of laptop ports (power in, charging iPhones, external keyboards, etc.).
Dongles should be the exception, not the norm, in real-world use — most owners should need zero. But HDMI and USB-A are still far too widely used to have been removed completely, and neither are likely to fade away anytime soon regardless of how Apple configures their laptops. Re-adding HDMI and at least one USB-A port would reduce or eliminate many people’s dongle needs, which I bet would dramatically improve their satisfaction.
Finally, Apple should give serious consideration to bringing back the SD-card slot. SD cards are more widely used than ever in photography, video, audio, and other specialized equipment, and they provide excellent options for fast, reliable storage expansion and data transfer. And they’re going to be around for a while — Wi-Fi and cables don’t or can’t replace most current uses in practice.
Back away from the Touch Bar
Sorry, it’s a flop. It was a solid try at something new, but it didn’t work out. There’s no shame in that — Apple should just recognize this, learn from it, and move on.
The Touch Bar should either be discontinued or made optional for all MacBook Pro sizes and configurations.
Touch ID is the only part of the Touch Bar worth saving, but the future is clearly Face ID. If we can’t have that yet, the ideal setup is Touch ID without the Touch Bar. We’d retain the Secure Enclave’s protection for the camera and microphones, and hopefully get the iMac Pro’s boot protection, too.
USB-C PD charging and replaceable charging cables are great advances that should be kept. USB-C PD is the reason I didn’t include battery life in this list — occasional needs for extended battery life can be achieved with inexpensive USB-C PD batteries.
But Apple could make their chargers and cables so much nicer — and they only need to look to their own recent past.
I’d like to see them bring back the charging LED on the end of the cable, and the cable-management arms on the brick. These weren’t superfluous — they served important, useful functions, and their removal made real-world usability worse for small, unnecessary gains.
MagSafe would be nice, but I don’t think it’s essential. MagSafe 2 wasn’t universally loved because it detached with too little vertical pressure when used on laps, couches, or beds, but maybe it could be moved to a splitting module along the cable, a few inches from the laptop end, like the original Xbox’s controller cables?
The move to a detachable, “standard” USB-C cable doesn’t preclude any of this. It’s already a specialized, dedicated power-only cable in practice (high-wattage USB PD support, but no Thunderbolt, and limited to USB 2.0 speeds). Third-party cables could still work — Apple’s could just be nicer.
Keeping what’s great
There’s a lot about the current MacBook Pro that’s great — fast internals, quieter fans, Touch ID, P3 screens, Thunderbolt 3, USB-C PD charging, and space gray, to name a few.
We shouldn’t have to choose between what’s better about the previous generation — connectivity, reliability, and versatility — and what’s great about this one.
Apple has made many great laptops, but the 15-inch Retina MacBook Pro (2012–2015) is the epitome of usefulness, elegance, practicality, and power for an overall package that still hasn’t been (and may never be) surpassed.
Introduced in 2012, less than a year after Steve Jobs died, I see it as the peak of Jobs’ vision for the Mac.
It was the debut of high-DPI Macs, starting down the long road (which we still haven’t finished) to an all-Retina lineup. And with all-SSD storage, quad-core i7 processors, and a healthy amount of RAM all standard, every configuration was fast, capable, and pleasant to use.
At its introduction, it was criticized only for ditching the optical drive and Ethernet port, but these were defensible, well-timed removals: neither could’ve even come close to physically fitting in the new design, very few MacBook Pro users were still using either on a regular basis, and almost none of us needed to buy external optical drives or Ethernet adapters to fit the new laptop into our lives. In exchange for those removals, we got substantial reductions in thickness and weight, and a huge new battery.
There were no other downsides. Everything else about this machine was an upgrade: thinner, lighter, faster, better battery life, quieter fans, better speakers, better microphones, a second Thunderbolt port, and a convenient new HDMI port.
The MagSafe 2 power adapter breaks away safely if it’s tripped over, and the LED on the connector quickly, clearly, and silently indicates whether it’s charging and when the battery is fully charged.
The pair of Thunderbolt (later Thunderbolt 2) ports gave us high-end, high-speed connectivity when we needed it, and the pair of standard USB 3 ports — one on each side — let us connect or charge our world of standard USB devices.
The headphone jack was thoughtfully located on the left side, because nearly all headphones run their cables down from the left earcup. (External-mouse users also appreciate this frequently-used cable not intruding in their right-side mousing area.)
The keyboard was completely unremarkable, in the best possible way. The crowd-pleasing design was neither fanatically loved nor widely despised. It quietly and reliably did its job, as all great tools should, and nobody ever really had to think about it.
The trackpad struck a great balance between size and usability. It provided ample room for multitouch gestures, but without being too large or close to the keyboard, so people’s fingers wouldn’t inadvertently brush against it while typing.
Not every owner needed the SD-card slot or HDMI port, but both were provided for times when we might. This greatly increased the versatility and convenience of this MacBook Pro, as many pro customers use A/V gear that records to SD cards or occasionally need to plug into a TV or projector. The SD-card slot could also serve as inexpensive storage expansion.
The power adapter’s built-in cable management keeps bags tidy. And if you need a longer cable, the extension comes in the box at no additional charge.
Versatile USB-A ports allow travelers to standardize on just one type of charging cable that can charge their iPhones and iPads from the laptop itself, multi-port wall or car chargers, portable batteries, airplanes, many outlets, and nearly all other chargers likely to be found in the world around them.
The 2015 revision brought the modern Force Touch trackpad and used the space savings to increase the battery to 99.5 Wh, just under the 100 Wh carry-on limit for most commercial airlines. When paired with the integrated-only GPU base configuration, this offered an unparalleled option for great battery life without giving up the large Retina screen.
And I like the backlit Apple logo on the lid. Maybe I’m old-fashioned, or maybe I just miss Steve, but it — along with the MagSafe LED and the startup chime — reminds me of a time when Mac designs celebrated personality, humanity, and whimsy.
* * *
I recently returned to the 2015 15-inch MacBook Pro after a year away.
Apple still sells this model, brand new, just limited to the integrated-only GPU option (which I prefer as a non-gamer for its battery, heat, and longevity advantages), but I got mine lightly used for over $1000 less.
I thought it would feel like a downgrade, or like going back in time. I feared that it would feel thick, heavy, and cumbersome. I expected it to just look impossibly old.
It feels as delightful as when I first got one in 2012. It’s fast, capable, and reliable. It gracefully does what I need it to do. It’s barely heavier or thicker, and I got to remove so many accessories from my travel bag that I think I’m actually coming out ahead.
It feels like a professional tool, made by people who love and need computers, at the top of their game.
It’s designed for us, rather than asking us to adapt ourselves to it.
It helps us perform our work, rather than adding to our workload.
This is the peak. This is the best laptop that has ever existed.
I hope it’s not the best laptop that will ever exist.
I love the idea of USB-C: one port and one cable that can replace all other ports and cables. It sounds so simple, straightforward, and unified.
In practice, it’s not even close.
USB-C normally transfers data by the USB protocol, but it also supports Thunderbolt… sometimes. The 12-inch MacBook has a USB-C port, but it doesn’t support Thunderbolt at all. All other modern MacBook models support Thunderbolt over their USB-C ports… but if you have a 13-inch model, and it has a Touch Bar, then the right-side ports don’t have full Thunderbolt bandwidth.
If you bought a USB-C cable, it might support Thunderbolt, or it might not. There’s no way to tell by looking at it. There’s usually no way to tell whether a given USB-C device requires Thunderbolt, either — you just need to plug it in and see if it works.
Much of USB-C’s awesome capability comes from Thunderbolt and other Alternate Modes. But due to their potential bandwidth demands, computers can’t have very many USB-C ports, making it especially wasteful to lose one to a laptop’s own power cable. The severe port shortage, along with the need to connect to non-USB-C devices, inevitably leads many people to need annoying, inelegant, and expensive dongles and hubs.
While a wide variety of USB-C dongles are available, most use the same handful of unreliable, mediocre chips inside. Some USB-A dongles make Wi-Fi drop on MacBook Pros. Some USB-A devices don’t work properly when adapted to USB-C, or only work in certain ports. Some devices only work when plugged directly into a laptop’s precious few USB-C ports, rather than any hubs or dongles. And reliable HDMI output seems nearly impossible in practice.
Very few hubs exist to add more USB-C ports, so if you have more than a few peripherals, you can’t just replace all of their cables with USB-C versions. You’ll need a hub that provides multiple USB-A ports instead, and you’ll need to keep your USB-A cables for when you’re plugged into the hub — but also keep USB-C cables or dongles around for everything you might ever need to plug directly into the computer’s ports.
Hubs with additional USB-C ports might pass Thunderbolt through to them, but usually don’t. Sometimes, they add a USB-C port that can only be used for power passthrough. Many hubs with power passthrough have lower wattage limits than a 13-inch or 15-inch laptop needs.
Fortunately, USB-C is a great charging standard. Well, it’s more of a collection of standards. USB-C devices can charge via the slow old USB rates, but for higher-powered devices or faster charging, that’s not enough current.
Many Android phones support Qualcomm’s Quick Charge over USB-C, which is different — usually — from the official, better, newer USB-C Power Delivery (PD) standard. Apple products, some Android phones, and the Nintendo Switch use USB-C PD. Quick Charge devices don’t get any benefit — usually — from PD chargers, and vice versa.
Your charger, cable, and any standalone batteries you want to use all must support the same charging standard for it to work at full speed.
Some cables don’t support USB-C PD at all, and most don’t support laptop wattages. Apple’s cable supports USB-C PD charging at high wattages… unless you bought the earlier version that doesn’t. Most standalone batteries sold to date don’t support USB-C PD — there are only a handful on the market so far, and most of them can’t charge a laptop at full speed, unless it’s the 12-inch MacBook.
You can use USB-C PD to fast-charge an iPhone 8 or iPad Pro with a USB-C to Lightning cable. But it doesn’t work with every USB-PD battery or charger, or every USB-C to Lightning cable, or every iPad Pro.
And, of course, there’s usually no way to tell at a glance whether a given cable, charger, battery, or device supports USB-C PD or at what wattages.
It’s comforting to think that over time, this will all settle down and we’ll finally achieve the dream of a single cable and port for everything. But that’s not how technology really works.
Before today’s USB-C can become ubiquitous and homogeneous, the next protocol or port will come out. We’ll have new, faster USB 4.0 and Thunderbolt 4 standards over the same-looking USB-C ports. We’ll want to move to an even thinner USB-D port. The press will call it “the future” and Apple will celebrate its new laptops that only have a USB-D port — two, if we’re lucky.
And we’ll have to start over again, buying all new cables, dongles, hubs, chargers, batteries, and displays to adapt it to what we really need.
Maybe next time, we’ll get it right. But probably not.
The Apple Watch desperately needs standalone podcast playback, especially with the LTE-equipped Series 3, which was designed specifically for exercising without an iPhone.
Believe me, I’ve tried. But limitations in watchOS 4 make it impossible to deliver standalone podcast playback with the basic functionality and quality that people expect.
Deal-breaker: Progress sync
Unlike on iOS, Watch apps aren’t allowed to play audio in the background and continue running.1
The only way to continue playback in the background on watchOS 4 is to use the WKAudioFilePlayer API. This is unsuitable for podcast players in its current state for one big reason:
It takes audio playback out-of-process, suspending the host app indefinitely during playback, and does not wake up the host app to notify it of playback progress or other relevant events like pausing, seeking, or reaching the end of an episode.
Since most podcast listeners also listen on their iPhone, the Watch needs to sync each episode’s listening progress with its iPhone app or a web service. But if you reach the end of a workout and pause playback without launching the podcast app, such as with a headphone “pause” button, turning off your headphones, removing your AirPods, or using the Now Playing app on the Watch, there’s no guarantee that the podcast app will be notified of your progress anytime soon. So when the user later goes to the iPhone app to continue playback, progress will be lost, or episodes’ state (played, deleted, recommended, etc.) will be wrong.
Minimum fix: During WKAudioFilePlayer playback, wake the host app to let it record progress periodically (ideally at least every minute) and on state-change events, such as pausing, seeking, and reaching the end of a file.
Better fix: Let apps continue running in the background indefinitely while they’re playing audio with WKAudioFilePlayer, just as workout apps can, so they can track their own state.2
To achieve the minimum experience-quality level that Apple and Overcast customers expect, watchOS and WKAudioFilePlayer also need a few more changes:
Volume control API or widget
Overcast’s top request for the Watch app by far is volume control via the Digital Crown, both for iPhone and Watch playback (when I offered it). It’s especially necessary for standalone Watch playback, as there’s very little access anywhere in watchOS to the concept of the system volume level.
Fix: An API to set the volume level, or a system UI widget for volume control like iOS’ MPVolumeView.
The lack of volume control is especially damaging with watchOS 4’s great new “Auto-launch Audio Apps” setting. If you’re playing audio from an iPhone app and have its corresponding Watch app installed, that Watch app shows by default when your Watch screen activates. If you don’t have its Watch app installed, the built-in Now Playing app shows instead.
In the last few days since watchOS 4’s launch, I’ve had dozens of users tell me that they’ve uninstalled Overcast’s Watch app just to force the Now Playing screen to auto-launch instead, just so they could have quick access to volume control.
Output-device presence, switching
WKAudioFilePlayer will not play to the Watch’s built-in speaker — it only plays to headphones connected to the Watch via Bluetooth. If playback is attempted without headphones connected, WKAudioFilePlayer just silently fails to play, without returning any errors.
Making matters worse, there appears to be no way to reliably detect the presence or absence of a suitable Bluetooth output device to avoid this.
Another common user request for Watch audio apps is an AirPlay output control. The rise of AirPods has increased this need and exacerbated the output-device-presence issue, as their multi-device sharing behavior leads to less certainty by the user about which device they’re currently connected to, and a more frequent need to manually select them on the current device.
Minimum fix: Fix the error-reporting behavior of WKAudioFilePlayer when suitable play conditions aren’t met, and provide a way to detect the presence or absence of a suitable audio-playback device so our apps can relay this information to the user.
Better fix: Also provide a standard AirPlay UI control, possibly integrated with the volume control, again like MPVolumeView on iOS.
Podcast listeners expect previous- and next-track buttons on headphones, cars, and the Now Playing app to perform 30-second seek operations instead of changing episodes completely. On iOS, MPRemoteCommandCenter lets apps respond to these commands however they want.
WKAudioFileQueuePlayer provides no such customization, ignores previous-track commands, and forces next-track commands to skip to the next audio file, losing any progress in the current one — and if there isn’t a next file in the queue, it stops playback completely. And all of this happens without waking the host app.
Minimum fix: Wake the host app whenever the current queue item changes in WKAudioFileQueuePlayer.
Better fix: Bring MPRemoteCommandCenter or an equivalent to watchOS, and if the host app adds its own command handlers, disable the built-in WKAudioFileQueuePlayer behavior for previous-/next-track commands.
Data-transfer progress, speed
While some apps may be able to perform direct downloads of podcast episodes from the internet to the Watch, many will rely on transferring audio files from the iPhone to the Watch to ensure compatible formats, consistent timestamps, small files, or audio-processing features.
Transferring a podcast file to the Watch is a long-running task, often taking at least a few minutes per episode (and sometimes much longer), but the WCSessionFileTransfer class provides no progress information. So there’s no way for apps to inform users how long the transfers may take, or if they’re currently moving at all.
Minimum fix: Add a progress API on WCSessionFileTransfer.
Better fix: Add a progress API on WCSessionFileTransfer and provide actionable information if the transfer is currently paused or waiting for something, such as having other transfers ahead of it in a queue, or needing a different power or connectivity state.3
Additionally: Wi-Fi and LTE transfers to the Watch are currently much faster than Bluetooth, often by an order of magnitude, but the Watch seems to send all WCSessionFileTransfer data over Bluetooth even when connected to a power source. File transfers should use Wi-Fi when power allows.
Nice-to-have: Streaming audio playback
One of the most compelling features of the Series 3 Watch with LTE is streaming Apple Music playback, but there’s no streaming audio-playback API available to developers on watchOS today. Every method requires locally downloaded files.
I recognize this is a big task. That’s why it’s a “nice-to-have”.
Enhancement: Bring a relevant subset of AVPlayer to watchOS, or expose streaming-audio playback via some other method.
There’s one elaborate exception that we discussed in Under The Radar #98: workout apps, which are allowed to run in the background and play audio. So this all becomes possible if you combine a standalone podcast player with a workout app, and only allow podcast playback while a workout is active that was started from that app. But this forces the combination of two completely different app types, and users would find the workout-during-playback requirement confusing, inexplicable, and limiting.
Requiring podcast apps to also be workout apps is a user- and developer-hostile hack that Apple probably doesn’t intend. ↩︎
This could also allow the use of the more capable in-process APIs such as AVAudioPlayer, which appeared to work well in watchOS 3. ↩︎
While I have you, please also add this reporting for paused or waiting background NSURLSessionDownloadTask transfers. ↩︎
I’m sorry that I missed the iOS 11 launch for my fancy drag-and-drop update. It’s coming soon, but it’s not ready yet.
In Hello Internet episode 4, CGP Grey introduced a metaphor for work-life balance as four light bulbs — work, friends, family, and health — between which one can allocate 100 watts, total. So it’s possible to shine brightly in one area at significant cost to the others, or to try to have a mediocre spread between all of them.
Usually, I prioritize family and work, in that order, and my friends are pretty tolerant of my general neglect, but health gets left as a pretty low priority.
This summer, I decided I finally needed to devote significant time to health, and since my family always comes first, that mostly came at the expense of reduced work time.1 And iOS 11 has ended up requiring more changes and fixes than I expected.
So I have a great Overcast update for iOS 11 and iPhone X in progress, but it’s not done yet. I appreciate your patience, and I hope you’ll find it worth the wait.
I’m fine. I just finally realized that the correct amount of exercise for a 35-year-old was probably not zero. ↩︎
Many Apple fans were amused when Phil Schiller explained the removal of the headphone jack on last year’s iPhone as “courage”. But that was nothing compared to what happened last week.
For ten years, the iPhone looked like this:
A rounded rectangle, bars on top and bottom, and a circle centered in the bottom bar. If you want to get fancy, put a line in the top bar, too.
It’s so simple that even when children draw it, it’s instantly recognizable as an iPhone to most of the world’s population. Not just any phone — an iPhone, specifically.
As an app developer and fan, I was hoping that the long-rumored edge-to-edge iPhone screen would still be a rectangle, possibly even with room for a Home button on a narrower bezel, so I wouldn’t have to change my habits (or my app’s layout):
But that’s the unmistakable image of an Android phone. (Or a generic smartphone — same thing.)
Apple would’ve lost what the iPhone has had since its introduction: a unique, recognizable shape that distinguishes itself from all of the other boring rectangles out there.
Many are now speculating that Apple will find a way to get rid of the iPhone X’s top “notch” (officially called the “sensor housing”) as soon as they can, and that this is a temporary design meant only for a few years. But I don’t think so.
Many app developers are planning to hide the notch in the UI with black bars. But Apple explicitly says not to.
This is the new shape of the iPhone. As long as the notch is clearly present and of approximately these proportions, it’s unique, simple, and recognizable.
It’s probably not going to significantly change for a long time, and Apple needs to make sure that the entire world recognizes it as well as we could recognize previous iPhones.
That’s why Apple has made no effort to hide the notch in software, and why app developers are being told to embrace it in our designs.
That’s why the HomePod software leak depicted the iPhone X like this: it’s the new basic, recognizable form of the iPhone.
Apple just completely changed the fundamental shape of the most important, most successful, and most recognizable tech product that the world has ever seen.