Posts in stories

The MacStories Selects 2022 Lifetime Achievement Award

Drafts

When we chose the second annual lifetime achievement award winner, there was no doubt in my mind that it should be Drafts. Developed and maintained by Greg Pierce of Agile Tortoise, Drafts has been the place where text starts on iOS for nearly a decade now. Times have certainly changed, but Drafts remains. Through the years, it has evolved into so much more than the simple text utility it once was.

While it has evolved, the most beautiful thing about Drafts has been the fervent dedication to its original mission statement. If you are about to type some text – any text — on your iPhone or iPad (and even, in modern times, your Mac), you should open Drafts. The app is so focused on text capture that it defaults to opening a new blank “draft” every time you open the app.

Writing text is only as useful as what you do with it, so the second pillar of the Drafts mission is its action menu; an infinitely customizable list of actions that allow you manipulate and send text from the app to essentially anywhere else you can think of. From random web services to other native apps on your devices, Drafts can almost certainly deliver your text. As your words get delivered throughout your entire digital life, you can take comfort in knowing that you can always search for and find anything you’ve written simply by looking up its record in Drafts.

Drafts in 2022. From left: the editing view, the action menu, and the filtering view.

Drafts in 2022. From left: the editing view, the action menu, and the filtering view.

It amazes me that after hearing that pitch (and even personally writing about it) again and again for over a decade, I still find it to be an alluring idea. Drafts’ longevity is a testament to the prescience of Pierce’s original vision. It pleases me immensely to see this app carrying on for so long, and it’s an honor to award it MacStories’ Lifetime Achievement award.

Read more

Making ActivityPub Your Social Media Hub for Mastodon and Other Decentralized Services

For many people who have stepped away from Twitter, Mastodon is their first experience with a decentralized social network. There’s a lot that can be said about the pros and cons of decentralization, but I want to focus on one very specific technical feature that Mastodon shares with a growing list of other services: ActivityPub.

ActivityPub is a W3C-recommended standard that was published by its Social Web Working Group almost five years ago and defines a decentralized social networking protocol for client apps and servers that connect them. The benefit to users is interoperability among services that adopt the protocol.

In practice, that means users of one ActivityPub service can follow and interact with users of a different service, which opens up some interesting possibilities. Tumblr seems to agree. The company plans to add ActivityPub support, so its users can interact with Mastodon’s users. That news piqued my interest in ActivityPub, but I’m not patient enough to wait for Tumblr to add support. I wanted to take two ActivityPub services for a spin now, so I set up a Pixelfed account on pixelfed.social.

Following Federico using Mastodon's web app (left) and my Pixelfed profile viewed from Tapbots' Ivory Mastodon app (right).

Following Federico using Mastodon’s web app (left) and my Pixelfed profile viewed from Tapbots’ Ivory Mastodon app (right).

Pixelfed is sort of like a decentralized version of Instagram that has adopted the ActivityPub protocol. Users can post photos, follow other users, and send each other messages. The service recently started beta testing an iOS app that is available on TestFlight, so I downloaded it, set up an account, and posted about it on Mastodon.

Because Pixelfed and Mastodon servers both comply with ActivityPub, anyone can follow my Pixelfed account from Mastodon without having to create a Pixelfed account or download the app, which is exactly what Federico did:

In practice, following someone’s Pixelfed feed is even easier. Instead of searching for my username, Federico could have searched for the URL for my Pixelfed profile in a Mastodon app and followed me that way. It’s worth noting, though, that not all Mastodon apps support searching for non-Mastodon servers. If you have trouble adding someone to your Mastodon feed, try Mastodon’s web app, which I’ve tried and know works. Also, be patient because some Pixelfed servers like pixelfed.social are struggling with an influx of new users that have hurt its reliability.

Photos posted from Mastodon (left) appear in the Pixelfed app too (right).

Photos posted from Mastodon (left) appear in the Pixelfed app too (right).

As the owner of a Pixelfed account, ActivityPub provides me some additional benefits too. First, I added my Pixelfed account to Ivory, the Tapbots Mastodon app that’s currently in alpha testing. That lets me post photos and respond to followers in the same app I’m using for Mastodon, which is nice. I’ve also followed my Pixelfed account from my Mastodon account, which allows me to view my posts from my Mastodon feed and boost them to my Mastodon followers, creating the equivalent of cross-posting on two services without actually posting separately to both.

Although there are a growing number of services that support ActivityPub, including PeerTube, a YouTube alternative for video, micro.blog, which supports parts of the protocol, and many others, it’s still early days for the protocol. However, with Twitter reminding users of the peril of relying on a centralized service provider, the pace of ActivityPub adoption is picking up, which should make 2023 a very interesting year for the open web.

iPadOS 16.2 and Stage Manager for External Displays: Work in Progress, But Worth the Wait

Stage Manager in iPadOS 16.2.

Stage Manager in iPadOS 16.2.

Ever since I last wrote about iPadOS 16, I have continued using Stage Manager on my iPad Pro. As I wrote in October, I like the idea behind Stage Manager more than its implementation. Despite the flawed design of its multitasking concepts and bugs I still encounter on a daily basis, it’s undeniable that Stage Manager lets me get more things done on my iPad by virtue of its concurrent app windows.

With today’s release of iPadOS 16.2, the idea behind Stage Manager achieves the full vision first presented in June, while its design and technical implementation remain stuck in an unpolished, half-baked state. Which is to say: conceptually, I love that Stage Manager in iPadOS 16.2 allows me to extend my iPad to an external display and put four additional windows on it; I’ve waited years for this feature, and it’s finally here. Technically speaking, however, the performance of this mode leaves a lot to be desired, with frequent crashes on my iPad Pro and an oft-confusing design that, I will reiterate, needs a rethinking.

Over the past couple of months, I’ve learned to live with Stage Manager, accept its quirks, and use what’s good about it to my advantage. As I recently wrote for Club MacStories members, I’ve put my money where my mouth is: I’ve gone all-in with Stage Manager on my iPad Pro and completely rebuilt my work setup around the M2 iPad Pro and Apple Studio Display, using Universal Control to seamlessly control iPadOS from a nearby Mac mini. (You can read the full story here.) After all, no other device in Apple’s ecosystem can effortlessly turn from a tablet into a laptop and into a desktop workstation like the iPad Pro can.

I’ve been working toward this vision for iPad modularity and contextual computing for the past several years. So now that Stage Manager has unlocked the final piece of the puzzle with external display integration, how good is it in practice?

And more importantly: was it worth the wait?

Read more

Resident Evil Village, Featuring Metal 3, Debuts on the Mac App Store

Apple spent a considerable amount of time during June’s WWDC talking about Metal 3, the latest iteration of the company’s graphics frameworks for videogames. The suite of technologies offers numerous technologies and tools for developers, including hardware-accelerated graphics, MetalFX Upscaling, which render scenes faster by taking advantage of upscaling and anti-aliasing, fast resource loading that uses asynchronous I/O techniques to speed up the delivery of data to Metal textures, and more. With the release of macOS Ventura, Metal 3 gaming is now available to all Mac users.

Resident Evil Village at WWDC.

Resident Evil Village at WWDC.

At WWDC, Apple announced three games that would be coming to the Mac later in the year that will take advantage of Metal 3:

The first of the games to be released publicly is Resident Evil Village, which is available in the Mac App Store now. I’ve had a chance to test the game in advance of its release for a few days, and from what I’ve seen in my limited time with the game, what Metal 3 enables is impressive.

For those unfamiliar, Resident Evil Village from Capcom was first released in mid-2021 and is available on every major platform. The eighth game in the Resident Evil horror series, Village follows the story of Ethan, whose wife has been assassinated and child abducted. Ethan is abducted, too, but escapes from his captors after their vehicle crashes. In short order, Ethan finds himself in a European village terrorized by zombie-like creatures.

I don’t have a lot to say about the game itself because I’ve only been playing it for a few days and horror games generally aren’t one of my favorite genres. Instead, I spent my time testing the game at various settings to get a sense of what Metal 3 can do, repeating the same section of the game multiple times at different resolutions and with other settings enabled.

I started the game on my M1 Max Mac Studio and Studio Display at 2560 x 1440 with the game’s Prioritize Graphics preset enabled. At those settings, Village generally maintained 60-70 fps with a rare dip into the 50s during one particularly intense scene. Next, I enabled MetalFX Upscaling, which helped hold the frames above 60 and allowed me to increase other settings, like mesh quality, while maintaining 60fps.

At higher resolutions, the frame rates took a hit. For example, 2880 x 1620 dropped the frame rate to around 50 fps. However, once I enabled MetalFX Upscaling, I was right back up to 60 fps. I was even able to maintain a steady 60 fps when I bumped the resolution to 3840 x 2160 and switched the MetalFX Upscaling from the Quality to Performance setting. Bumping up other settings like the shadow and mesh quality didn’t significantly degrade performance either.

I also ran some tests with the game running on my M1 MacBook Air, where I was able to use the same sort of settings tweaks to maintain around 30 fps. The experience wasn’t bad, but Village definitely looked nicer, running on more powerful hardware paired with a Studio Display.

Overall, my first impressions of Metal 3’s enhancements to gaming on the Mac are positive. The results aren’t in the same league as a gaming PC with a dedicated graphics card. For example, I’ve seen benchmarks for Resident Evil Village running with an NVIDIA 3080 card that can run the game at over 120 fps. That’s double what I saw with my Mac Studio, but it’s still better than I’ve experienced in the past with games as recent as Village.

Metal 3 is promising. With just one big-name game taking advantage of it at the moment, it’s too early to judge its impact on Mac gaming, but it’s a step in the right direction. Hopefully, more game publishers will adopt the technology and bring their games to the Mac soon.

Resident Evil Village is available on the Mac App Store for $39.99.

macOS Ventura: The MacStories Review

macOS Ventura is a hard release to pin down. I’ve been running it for months, and it’s been running well for all my everyday work and personal tasks. Features like Continuity Camera, iCloud Shared Photo Library, and the many system app updates have, on the whole, been stable, worked as advertised, and helped me do more with my Mac. So, from an everyday workflow standpoint, Ventura is an excellent release that delivers on the promise of an OS that moves in step with Apple’s other OSes and erases artificial barriers to users coming from iOS and iPadOS. And yet, I worry about the clouds on the horizon.

The release of Ventura is just one moment in time along macOS’s evolutionary path, but it’s an important one. Each fall release is a marker laid down by Apple that says something about where the Mac has been and where it’s going.

The story of macOS Ventura didn’t begin at WWDC in June. As I wrote in last year’s macOS Monterey review, it started five years ago:

For the past few years, no narrative thread has been more important to the Mac and its operating system than their realignment within Apple’s product lineup. It’s a fundamental transformation of both hardware and software that has taken shape over years, beginning publicly with Craig Federighi’s WWDC Sneak Peek in 2018.

Before Mac Catalyst, there was Craig Federighi's 2018 Sneak Peek.

Before Mac Catalyst, there was Craig Federighi’s 2018 Sneak Peek.

Last year’s release of Monterey went a long way toward validating what came before with Catalina and Big Sur:

Monterey is one of the most tangible, user-facing payoffs of the past three years of transition. More than ever before, Apple is advancing system apps across all of its platforms at the same time. Finally, everything is everywhere.

Ventura is, in many ways, a continuation of Monterey’s storyline. Apple has delivered a second year of parallel development across its system apps, with the notable exception of Shortcuts, which I’ll cover later. That’s a big win for Mac users who, in previous years, waited multiple releases for apps like Maps and Books to catch up with their iOS and iPadOS counterparts.

The familiar interface and feature set across multiple platforms are one of the biggest and most tangible achievements of the past few years.

The familiar interface and feature set across multiple platforms are one of the biggest and most tangible achievements of the past few years.

So, with Monterey’s success of moving system apps forward in unison across all OSes looking more like a trend than a one-off novelty, what are the clouds I’m seeing on the horizon? There are three:

  • Stage Manager: Stage Manager is in far better technical shape on the Mac than on the iPad. In fact, I’ve been using it every day since WWDC and will continue to do so. There’s lots of room for improvement, which I’ll cover below, but my concern extends beyond the Mac-specific issues to what the feature’s problems on the iPad mean for Mac users long-term, which is something I covered last month for Club MacStories members and will expand on below.
  • Shortcuts: Shortcuts was in rough shape when it launched on the Mac last year. The app is in a much better place today, although bugs continue to be a problem. More concerning to me, though, is the lack of new system-level actions on the Mac. A lot of resources undoubtedly went into stabilizing Shortcuts on the Mac over the past year, which is understandable, but unfortunately, those efforts seem to have been at the expense of introducing new system-level actions or maintaining parity with new actions on iOS and iPadOS.
  • System Settings: So much of the design work we saw introduced with Big Sur was so carefully considered to harmonize macOS with iPadOS while retaining its Mac nature that System Settings is a shock to, well, the system. System Preferences was long overdue for a refresh, but System Settings isn’t the redesign we needed. Instead, it’s a clear example of why you can’t just graft iOS or iPadOS design onto macOS and call it quits.

Although each of the items above concerns me, it’s equally important to put them in context. For most users, macOS is in a very good place. My day-to-day work on the Mac isn’t affected by whether the iPadOS version of Stage Manager is buggy. I may feel constrained by the lack of some actions in Shortcuts on my Mac, but at the same time, I’ve got Shortcuts on the Mac, something I’d hoped for for years. And Systems Settings are, after all, just settings that may not be great to look at, but they still work.

However, while the issues with Ventura may not be immediate, they’re still important because they threaten the viability of the Mac in the midst of its hardware renaissance. I want to see the Mac continue to grow and flourish, and I’m convinced more than ever that aligning it and the iPad is one of the ways to accomplish that. Unfortunately, Ventura doesn’t move that ball forward in a meaningful way.

With Apple firing on all cylinders when it comes to hardware, now is no time to let macOS stall. Source: Apple.

With Apple firing on all cylinders when it comes to hardware, now is no time to let macOS stall. Source: Apple.

By tying the two together, Apple has set the stage for a healthier third-party app ecosystem that benefits both platforms by making it more economical for developers to create apps for both. I’m sent a lot of apps to try, and I can tell you that this is absolutely happening already. The vast majority of the apps I’m sent today aren’t Mac-only or iPad-only – they’re universal apps that work on both and usually the iPhone and Apple Watch too.

However, the work and the story that started with Federighi’s Sneak Peek aren’t finished. For the Mac and iPad to thrive, now is not the time for Apple to take its foot off the gas. Yet, that’s what Ventura feels like after several years of foundational changes to macOS. It’s not a bad update. There’s a lot to like among the system apps and other changes, but I can’t shake the nagging sense that Apple has taken its eye off the long-term vision for macOS with Ventura. That won’t affect your day-to-day use of the OS, but it’s certainly something worth keeping a close eye on as Ventura is updated and WWDC rolls around again next summer.

Read more

Stage Manager in iPadOS 16: At the Intersection of Bugs, Missing Features, and Flawed Design

Stage Manager in iPadOS 16.1.

Stage Manager in iPadOS 16.1.

This article wasn’t supposed to go like this.

iPadOS 16 is launching to the public today, and it carries a lot of expectations on its shoulders: for the first time since the introduction of the original iPad in 2010, Apple is embracing a Mac-like windowing system that lets you use up to four windows at the same time on the iPad’s screen. You can even resize them and make them overlap. If you’ve been following the evolution of the iPad for a while, you know that’s very unusual.

But the reason this story was meant to be different isn’t to be found in Apple’s design philosophy for iPadOS 16. Typically, MacStories readers would expect a full-blown ‘The MacStories Review’ to go alongside a new version of iPadOS. That’s what I’ve been doing for over seven years at this point, and I don’t like breaking my writing patterns. When something works, I want to keep writing. That’s precisely why I had to stop writing about iPadOS earlier in the summer and until last week.

Stage Manager, the marquee addition to iPadOS that lets you multitask with floating windows, started crashing on my M1 iPad Pro in mid-July and it was only fixed in early October. When I say “crashing”, I mean I couldn’t go for longer than 10 minutes without iPadOS kicking me back to my Lock Screen and resetting my workspaces. And that was only the tip of the iceberg. For nearly two months, I couldn’t type with Apple’s Magic Keyboard or use keyboard shortcuts when Stage Manager was active. Before it was pulled by Apple and delayed to a future release, external display support in Stage Manager was impossible to rely on for production work. The list goes on and on and on.

Normally, I would use the introduction of my iOS and iPadOS reviews to tell you how I’ve been living and working with the new operating system every day for the past three months. I’ve always tried to publish annual OS reviews that are informed by practical, consistent usage of a new operating system which, I hope, has led to highly opinionated, well-researched stories that can stand the test of time. That kind of story hasn’t been possible for me to produce with iPadOS 16 yet.

Effectively, I’ve only been able to sort-of use iPadOS 16 with Stage Manager on my M1 iPad Pro again for the past two weeks. Before that, it’s not that I didn’t want to use iPadOS 16 and Stage Manager because I hate progress; I literally couldn’t unless I was okay with my iPad crashing every 10 minutes. So, at some point over the summer, I made the call to revert to Split View and Slide Over – which are still the iPad’s default multitasking mode in iPadOS 16 – and I’d check back in on Stage Manager on each beta of iPadOS 16. It was only around two weeks ago that, despite some lingering bugs I’ll cover later, I was able to finally leave Stage Manager enabled and go back to where I was when I published my iPadOS 16 first impressions article in July.

Think about my position this way: there’s a hole from early August to early October in my typical “reviewer summer” during which I couldn’t use the biggest addition to iPadOS 16 at all. The fact that Apple delayed, slimmed down, and kept iterating on Stage Manager until the very last minute seems to suggest I wasn’t the only one desperately trying to make it work.

I started using iPadOS 16 and Stage Manager again two weeks ago; what kind of “review” should this be?

Read more

iOS 16 Lock Screen Widgets: The MacStories Roundup

As the release of iOS 16 approached, I felt a strong sense of déjà vu. TestFlight betas with Lock Screen widgets came pouring in. It felt like 2020’s debut of Home Screen widgets all over again. This time, though, those betas have been all about Lock Screen widgets.

As Federico covered in his iOS 16 review, Apple’s approach to Lock Screen widget support in its own apps is different than its approach to Home Screen widgets was. There are far fewer Lock Screen widgets available for system apps than there were when Home Screen widgets were launched with iOS 14. Part of the difference is undoubtedly because Lock Screen widgets are smaller and monochrome, but there remain gaps that aren’t so easily explained away. Fortunately for us, third-party developers have stepped into the breach with a long list of innovative widgets.

With so many choices and only three to five Lock Screen widget slots to fill, it’s hard to know where to start, so I’ve compiled a list of my top recommendations from the over 40 I’ve tried so far. Of course, this list doesn’t include the apps I already covered last week, but it goes without saying that Widgetsmith, Lock Screen One, LockFlow, and CARROT Weather would be also be included in this list if I hadn’t already written about them.

Read more

iOS 16: All the Things I Didn’t Like

Earlier this week, I published my review of iOS 16. As you may have seen, throughout the eight chapters of the story, I pointed out some of the flaws of iOS 16 and aspects I didn’t particularly like. That gave me an idea.

First, however, allow me to thank to everyone who read, enjoyed, and recommended the review. I’m glad the story resonated with MacStories readers. I take my responsibility to work on these annual reviews very seriously, and I’m excited about having found a format that lets me review a sprawling operating system such as iOS in a review that’s still approachable and fun to write.

Anyway: as I was writing the review, I realized that I had several complaints about things I didn’t like in iOS 16 (shocker, I know). So I had an idea: I asked Finn Voorhees1 to work on an update to my Obsidian plugin that lets me compile chapters of the review into a single Markdown file. This update, which will be released for Club MacStories+ and Premier members this Saturday, enabled me to mark specific passages of the review as “complaints” and extract them all at once. You will be able to use this new plugin option however you want: it’s going to work for any kind of text you want to highlight from a long-form story in Obsidian.

That being said, I compiled all my iOS 16-related complaints, organized them into sections, and you can find them below.

Here are all the things I didn’t like in iOS 16, which I hope Apple will fix in the future.

Read more

watchOS 9: The MacStories Review

As we enter the ninth iteration of watchOS, I must admit that I sometimes find myself looking back wistfully on the computer watch that the Apple Watch once was. My inner tech nerd misses the wild, blind shots at digital connection and interface design which we were gifted by an Apple that had not yet figured out what the mass market wanted from this device.

In many ways, the early days of the Apple Watch feel like echoes from a bygone era of Apple; an era in which it was more willing to throw things at the wall just to see what stuck. This is, after all, the company which brought us the buttonless iPod shuffle, the hockey puck mouse, brushed metal, the tape-recorder Podcast app, and so much more. We tend to call it Apple’s sense of “whimsy”, and early watchOS had plenty of it.

Time Traveling in watchOS 2.

Time Traveling in watchOS 2.

In watchOS 2, Apple shipped a feature called Time Travel where you could spin the Digital Crown to “travel backwards and forwards in time”. Complications would move alongside the watch hands to reflect their past or predicted future values. Time Travel was demoted to a setting in watchOS 3, and quietly removed entirely some time later.

There was also the concept of Glances beginning all the way back in watchOS 1. Glances were single-page app interfaces accessible by swiping up from the watch face, then swiping side-to-side to switch between them. Third-party apps could create these, and the watch supported up to 20 of them. Glances were also canned in watchOS 3. They were replaced by the Dock, which never quite managed to capture the same energy.

For years, Apple seemed particularly interested in the potential of the Apple Watch to be a core hub for personal communication. Until watchOS 3, the hardware side button on the device was dedicated to opening the Friends interface. When interacting with your friends, you could send giant animated emojis — perhaps a very early precursor to the Memoji that we have today. And of course, no one could forget Digital Touch. Who among us did not feel more connected to our loved ones when tapping out pings and drawing shapes on their wrists1?

The Friends interface in watchOS 2.

The Friends interface in watchOS 2.

What leaves me feeling so conflicted is that, ultimately, all of the above features were pretty bad. No one used the Friends interface, Time Travel wasn’t particularly useful, third-party Glances were kneecapped by their lack of interactivity, and communicating from an Apple Watch has always just been way more work than pulling out your iPhone. Apple was right to kill all of these features in their time, but I still can’t stop missing the days when my Apple Watch was searching for more variety in purpose than it exists with today.

Read more

  1. I imagine Digital Touch is unfazed by my mockery; likely too busy feeling satisfied that it is the only one of the features described above which has (somehow) endured into modern iterations of watchOS. ↩︎