[Software] Apple’s Mac Software Strategy Is More Confusing Than Ever

[#Hassan.]

Apple’s Mac app strategy has become more confusing than ever as the company revives its computer hardware line. Also: The car project goes full-throttle, Apple will let consumers repair their own devices, and the company sets its return-to-office deadline.

I’ve been using a new MacBook Pro with an M1 Max chip since its release last month, and it has certainly been worth the wait. Prior to this laptop, I had been using its 16-inch predecessor from 2019. From the beginning, that “Pro” computer really couldn’t handle simple everyday tasks like simultaneously having dozens of web tabs open at once, communicating on Slack and Messages, watching video, and scrolling through Twitter. The experience on that previous Mac, which had an Intel Corp. chip, was so subpar that I often switched to an iPad. This was the ultimate First World problem, of course, but it was surprising how slow and loud the Intel 16-inch MacBook Pro was during two years of ownership. My experience so far with the new MacBook Pro couldn’t be more different. The new chip powers through everything I need to do daily. The fans also don’t run as loud as a 747 airplane (I haven’t heard them once), and I don’t need to worry about the machine heating up my legs. So, the hardware is great. But there remains one key Mac problem that I hope the company will address next: its app ecosystem. Apple has made strides with the Mac App Store in recent years, and it’s no longer the ghost town it once was. But it’s also become a bit of a muddle. Apple and third parties now offer several different ways to make Mac apps, creating confusion in the developer community and sometimes for consumers. In addition, Apple’s cross-platform app development strategy—which lets developers optimize their iPad apps for the Mac or run iPhone apps unmodified on the desktop—hasn’t taken off as quickly as Apple may have hoped.

Here are all the avenues that developers can use to build and distribute apps on the Mac (compared with iOS and Apple’s other platforms, which essentially have one): Running iOS apps on the Mac unmodified: This feature lets developers ship completely unmodified iPhone and iPad apps on Macs with in-house chips. Catalyst apps with an iPad-like interface: This technology lets developers modify their iPad apps and run them on the Mac with some optimizations. An example of this is Apple’s mediocre Mac Home app. Catalyst apps with a Mac-optimized interface: This goes a step further, with developers using the same underlying technology and code from their iOS app, but fully optimizing the app’s interface for macOS. The Mac’s well-received Messages, Swift Playgrounds, Find My and Maps apps are examples. AppKit apps: These are standard, native Mac apps built for the desktop first using Apple’s standard development technologies. This list includes Safari, Calendar, Mail and the Photos apps, plus more intricate software like Final Cut Pro. Electron apps: This method is the only one not made by Apple, but it’s still pretty po[CENSORED]r because of its reliance on simpler web development technology. This app engine is used by Slack, WhatsApp and Visual Studio Code and is more easily deployable across both Mac and Windows. The jumble of options means there’s inconsistency across the Mac software ecosystem. Some apps are simply mirror images of existing iPhone and iPad apps and have no optimization. Some are slightly tweaked iPad programs. And others—like Slack and WhatsApp—behave like web apps and could drag down performance. Running unmodified iOS apps on the Mac seemed promising when Apple first debuted the feature last year alongside its own Mac chips, but that means the Mac now supports a bevy of iPhone apps that don’t function well on desktops and laptops. At the same time, big-name apps that would make sense on the Mac aren’t being made available by their developers. The ability to load up the Netflix, Instagram, Nest, Postmates or ESPN iOS app on my Mac would be ideal. On the plus side, Apple is now giving developers a bevy of options—something many of them appreciate. Developers have complained in the past about needing to make changes at the drop of a hat every time Apple adopts new technologies. Now that’s less of a problem.

Apple is also offering new tools like the SwiftUI framework, which is a more modern way of developing native Mac apps. It can be used by both AppKit and Catalyst developers. And the company recently rolled out TestFlight for Mac (finally) to let developers better test their apps before shipping. The sweet spot for first- and third-party Mac development in 2021 is Catalyst apps with Mac-optimized interfaces. Those apps are optimized for high-performing machines and standard Mac input devices like keyboards and trackpads. They’re also often simpler to develop than native AppKit apps and rely heavily on existing iOS code. That means programmers can share code between their iOS and Mac apps, speeding up development while creating consistency for customers. The problem is that Apple hasn’t even fully embraced that technology, leading some developers to question which route they should take for their own software. While the majority of Apple’s new apps are built with Catalyst—including Voice Memos and Stocks—many of them still use AppKit. If the company wants to push developers to use Catalyst technology, it should convert the rest of its software to that option. I expect this to happen over the next few years. This will speed up Apple’s own development timelines, and the company won’t have to write completely different Mac and iOS versions of apps like Safari and Photos. This shift would free up engineering resources to develop new platforms and provide more consistent apps for users. While Apple’s Mac hardware is stronger than ever, the company must now focus on unifying its Mac software ecosystem—for the benefit of its own products, third-party app developers, and, of course, consumers. The Bench Apple’s car project goes full-throttle. Kevin Lynch, the Apple Watch software chief, began overseeing the company’s car effort in recent weeks. Now he’s pushing the team behind the project to accelerate its development, with an eye on debuting a car as early 2025. He also wants the first version of the vehicle to be fully autonomous and lack a steering wheel or pedals. It’s an ambitious and aggressive plan and certainly fascinating to follow. If you haven’t already, read my in-depth look at what’s happening inside Apple’s car division as the company aims to take on Tesla Inc.

link : https://www.bloomberg.com/news/newsletters/2021-11-21/why-is-apple-s-aapl-strategy-for-developing-mac-apps-so-confusing-kw9lv17j