@johnvoorhees I think you're right.
For primarily-iOS apps, letting your app run in iPad-compatibility mode on a Mac is MUCH less work than maintaining a Catalyst app, which itself is massively less work than having a separate AppKit app.
@marcoarment @johnvoorhees Was the Pocket Mac app any good? I'd try it but it looks they already pulled it from the Mac App Store. I'm guessing it wasn't any good, so they might as well just rely on the iPad version.
On the Mac, Pocket seems like the sort of thing that makes sense to use in your web browser. Even Apple's own News app is built with Catalyst, and every single time I use Apple News on the Mac I wind up wishing I were reading the article in Safari instead.
@gruber @marcoarment @johnvoorhees 👋 I was the maintainer of the Pocket macOS app up until this change. It was a nice app, and a good codebase, but it was getting pretty long in the tooth, and falling behind on features.
@gruber @marcoarment @johnvoorhees My biggest complaint about the iPad app on macOS is the SafariViewController => Safari bridge, which throws up a clunky “this link is being opened in Safari” window every time you view web content. I accept the underlying conceit, but it’s a pretty rude kludge.