Part II -- Apple at 50: The Mac’s Unfinished AEC Story

Opinion by Anthony Frausto-Robledo, AIA, NCARB, LEED AP

Last week: Part I at upfrontezine.substack.com/p/apple-at-50-macs-unfinished-aec-story.

Architosh’s Own Evolution

Architosh changed course over time. Once Apple’s survival was no longer in doubt, the online publication in 2008 moved from its original role of community-centered advocacy towards a broader, vendor-neutral coverage of AEC technology. The shift made sense editorially. The site grew into a widely-respected publication covering the AEC [architecture, engineering, construction] software landscape globally, across platforms, devices, cloud applications, and emerging workflows.

But something was lost in the transition. As Apple receded from the site’s explicit focus, so too did the sense that there was a visible, organized, Mac community in architecture worth serving and defending. In hindsight, Architosh’s move away from community-building may have signaled that the long fight for the Mac in architecture was entering a quiet phase, perhaps a less hopeful one.

Still, the evolution mirrored the market itself. By the 2010s, the most important AEC story was no longer whether the Mac had a constituency. It was whether Apple would remain relevant, while the industry’s center-of-gravity moved elsewhere decisively.

Rise of Revit, and the New Strategic Problem

That ‘elsewhere’ was Revit.

Revit can run on on MacOS with Windows emulators

If AutoCAD’s departure from the Mac was the first major break in Apple’s AEC story, then the rise of Revit became the deeper, long-term challenge. Apple was succeeding brilliantly in consumer electronics, with the iPad becoming enormously influential on construction sites, but Revit was consolidating its place as the dominant BIM [building information modeling] platform across much of the AEC industry.

This mattered more than any single cycle in hardware. By the early 2010s, architecture and construction were being shaped by BIM-centered workflows, with Revit sitting at the center of the shift. A Windows-only application become the defining platform of modern AEC production.

Revit’s importance reshaped the Mac debate. The question no longer simply was whether Apple could recover lost ground through general design affinity or improved hardware. The question became whether the Mac could remain strategically viable in architecture, without native access to the industry’s most important BIM environment.

Architosh covering the Open Letters

Autodesk seemed aware of the pressure. Revit was long one of the most requested Autodesk applications for the Mac. When the Open Letter controversies [source] emerged in 2020 [opposing Autodesk’s lack of flexibility], Architosh became a central publication covering the customer fallout and the wider question about Revit’s future [source]. Although the debates were not primarily about the Mac, they again exposed an important truth: The long-term future of AEC platforms could not be discussed without also discussing Apple.

The “Pro” Problem at Apple

Unfortunately, these years coincided with one of Apple’s weakest periods in professional desktop strategy. From 2013 to 2019, professional users endured the notoriously-compromised “trash can” Mac Pro or else were pushed toward less ideal alternatives such as iMacs. Many creative professionals came to believe that Apple had forgotten the needs of high-end users entirely.

Mac Pro mocked for looking like a trashcan (image source batterymap.co.nz)

The criticism was not limited to AEC, but architecture felt it acutely. CAD and BIM users care deeply about responsiveness, reliability, graphics, and raw compute performance. They also care about stability and confidence that platform vendors actually understand professional demands. During this period, Apple did little to reassure them.

Then Apple Silicon arrived.

Apple Silicon, and the Return of Possibility

Apple’s 2020 transition of its CPU architecture to its own design, called Silicon and based on ARM, changed the conversation more dramatically than anything Apple had done for the Mac in years. Once again, Apple forced third-party software developers through a processor transition. But this time the shift was welcomed, because the underlying technology was so compelling.

Apple Silicon brought exceptional performance per watt, outstanding integration, and industry-leading single-core performance. For AEC users, that last point matters enormously. Nearly all CAD and BIM operations run on a single CPU thread, so they benefit primarily from strong single-thread responsiveness, even in today’s multicore world. For the first time in a long time, Apple did not merely have an elegant or attractive machine for architects, it had a machine with a serious and sustained technical advantage in the kind of performance many design applications value most.

[Apple this year announced no more Mac Pros will be released (source); the Mac Studio should be considered the replacement (source)].

This creates new strategic openings.

The first possibility is computer ecosystem-convergence to ARM. All Android and Chromebook machines run on ARM CPUs. Microsoft is championing the Windows ecosystem on ARM. Apple now runs on ARM.

As a result, software vendors may find it easier to bring applications to macOS, because the architectural gap between platforms is narrowed. In such a scenario, the Apple Silicon era could become a second chance for the Mac in AEC — similar in strategic importance to Apple’s CPU transition from PowerPC to Intel, but potentially larger in consequence.

The second possibility is more paradoxical. Apple Silicon has become so powerful that running Windows applications in virtualization is surprisingly viable. In some cases, the Mac’s raw performance advantage can offset the virtualization speed penalty enough to make Windows software usable at an impressive level. That raises a provocative question: If Windows applications already run well enough on powerful Macs, will then some vendors decide there is no need to port?

That tension captures the current moment. Apple now has the strongest technical case for the Mac in years, perhaps ever, yet the software question remains unresolved.

Performance, Trajectory, and Meaning

There is a temptation to reduce Apple Silicon’s significance to benchmark bragging rights, but a larger point is more practical. Apple now has something it has rarely possessed so clearly in its competition with Wintel: Not just design appeal or efficiency, but a credible claim to sustained leadership in the performance characteristics that matter to many professional users.

Single-core gains are not abstract in CAD and BIM. They are felt decisively in responsiveness, regeneration speed, modeling fluidity, and the general sense that software is reacting instantly, rather than grudgingly. In the world of design tools, that matters.

Apple’s performance trajectory in recent years suggests that the company may maintain a meaningful advantage for years to come, particularly if future chip generations continue to widen the gap, or even simply preserve it. If so, the historical contradiction at the center of this article becomes harder to ignore. The Mac may now offer some of the most compelling hardware in the world for certain AEC workloads at a moment when the industry’s most essential software remains largely tied to Windows.

That is not just ironic. It is strategically unsustainable.

The Question at 50

At 50, Apple has the strongest silicon story in the history of the Mac and, in many respects, the best hardware case it could ever present to serious design and professional computing. Yet, in AEC, the central contradiction remains: Some of the hardware most attractive to CAD, 3D, and BIM users continues to lack native access to some of the industry’s most important software.

This has been Apple’s long struggle in architecture. The company has never had much trouble convincing architects that the Mac is desirable. It has struggled to convince the software industry that the platform is too important to ignore.

That challenge has defined every major phase of Apple’s relationship with AEC, from the early Mac years, to the loss of AutoCAD, to the rise of Windows-only Revit, to the current Apple Silicon era. The details have changed, but the basic conflict has not: Apple keeps building machines that make sense for designers, while the industry’s software center of gravity remains elsewhere.

If that finally changes, Apple’s next era in the architecture discipline could look very different from its first 50 years. If it does not, Apple will remain what it has so often been in AEC, the maker of extraordinary machines standing just outside the industry’s most important doors.

Postscript

A final note is necessary here. To speak of Apple’s long software struggle in AEC is not to say that the Mac lacks serious architectural tools. It does not.

Archicad and Vectorworks, both part of the Nemetschek Group, have for years stood as powerful native alternatives on macOS — competitive with Revit, and in important respects ahead of it. They remind us that the Mac story in architecture is not only a story of absence and missed opportunity. It is also a story of enduring strengths, loyal developer support, and software makers that recognized long ago that architects on the Mac were worth building for.

User interface showing ArchiCAD, the first BIM design software (image source Graphisoft)

That point extends beyond BIM authoring tools. The Mac has long been exceptionally well served in 3D modeling and visualization, with leading solutions across those domains running natively and running well on macOS.

These remain among the most important parts of the design pipeline: Tools that help win work, shape design intent, and carry projects toward final resolution. Even many Revit-based firms rely heavily on such tools in these phases, especially Trimble SketchUp, and McNeel’s Rhino and Grasshopper, the latter of which remain deeply embedded in architecture schools and design-forward practices around the world. All of these run beautifully on the Mac.

Grasshopper programmatically designing shapes for Rhino (image source McNeel)

Looking beyond desktop software, the AEC landscape has shifted toward the cloud. Numerous solutions now operate largely through the Web browser, including common data environments and collaboration platforms from some of the industry’s biggest players, Autodesk among them. That evolution matters, because it reduces the degree to which professional practice is tied to one operating system.

It is important to add this postscript, because Web-enabled apps do not sufficiently credit the many AEC developers who supported the Mac faithfully and well. To leave them unnamed risks flattening the story and overstating the role of what is missing.

The larger point of my thesis remains unchanged: The Mac’s AEC story is unfinished, especially when seen through the lens of Architosh’s origin story, and the editorial and community ambitions that defined its first nine years. But unfinished does not mean unbuilt, and it certainly does not mean unsupported.

We hope companies such as Nemetschek, Trimble, McNeel, and others understand that editorial choice in context.

---

[Anthony Frausto-Robledo is founder and editor-in-chief of Architosh at architosh.com. This article is reprinted with permission.]