{"id":48840,"date":"2025-08-08T15:14:19","date_gmt":"2025-08-08T19:14:19","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=48840"},"modified":"2025-08-13T16:31:29","modified_gmt":"2025-08-13T20:31:29","slug":"no-part-2","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2025\/08\/08\/no-part-2\/","title":{"rendered":"“No” Part 2"},"content":{"rendered":"

Steve Troughton-Smith<\/a>:<\/p>\n

“Are you merging iOS and macOS?” “…No! Of course not”<\/p>

Yet seven years later it is incredibly clear that there is a point of convergence coming in the very near future where iPadOS and macOS look effectively identical and run basically the same apps — and at that point, why do you need two sets of everything? Yes, they both ‘feel’ different, and they draw different lines in the sand re capabilities (today). But that doesn’t mean you truly need two operating systems.<\/p><\/blockquote>\n\n

Matt Birchler<\/a>:<\/p>\n

Yesterday I wrote about<\/a> how macOS and iPadOS apps are really merging into one unified experience. That was a quick post, but I wanted to hit on this again with some specific examples. The message was basically that while Apple hasn’t technically “merged” the operating system, they have merged the experience of actually using apps on each platform. Maybe in the early 2010s there were distinct app experiences built for the iPad and Mac, but that ship has long sailed. In 2025, Apple wants you to make Apple apps, and the experience of using those apps on each platform is the same. Here’s some examples.<\/p><\/blockquote>\n\n

It’s great that iPadOS can do more now and can also still be an older, simpler iPad if you want. But it feels like macOS has been held back for the last decade or so. The ceiling for desktop apps should be higher.<\/p>\n\n

Max Oakland<\/a>:<\/p>\n

\n

Making them look and act the same is bad design. They should reflect the machines they run on and the ways people use them.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n