I recently read an article asking “why do we need this?” – Liquid Glass. Why?. It’s a fair question—but there are plenty of reasons why users, developers, and Apple all benefit from Liquid Glass. In the ongoing battle between native APIs and web APIs, native tools offer clear advantages. But to make those advantages visible and compelling, aesthetics can play help.
Apple understands what’s at stake. This isn’t just a technical debate—it’s a fight for platform dominance. Over 20 years ago, Joel Spolsky’s essay, How Microsoft Lost the API War, explained how Microsoft lost developer loyalty by failing to keep its native APIs relevant. Apple doesn’t want to repeat that mistake.
Native vs. Web: More Than Just Performance
Web APIs have improved significantly, offering cross-platform convenience and fast deployment. But when it comes to building apps that are faster, more private, and visually refined, native APIs still lead. They give developers direct access to system capabilities—hardware acceleration, secure data handling, and rich UI interactions that web layers can’t match. Liquid Glass is a clear example of what native APIs can do. It makes interfaces feel responsive, immersive, and deeply integrated with the OS. It’s the difference between a webpage mimicking an app and an app that feels truly native.
Modern mobile devices have powerful CPUs and GPUs—why not use them? Why insert a heavy browser layer and constant server communication between that power and the user’s experience? It’s a waste of resources. Native APIs allow developers to adapt effects to device capabilities, ensuring smooth performance across the board. And for many users, style is part of performance—it shapes how fast and polished an app feels.
The Case for Transparency and Privacy
As users and developers, we should champion Liquid Glass not just because it looks good, but because it’s a symbol of what native development can offer: speed, security, elegance, and emotional resonance. In a world where users are bombarded with generic, cookie-cutter interfaces, Liquid Glass is a breath of fresh air—a reminder that software can be both powerful and elegant.
Let’s embrace transparency—not just in design, but in philosophy. No data moving behind the scene, no sites spying on users.
One of the most overlooked advantages of native APIs is privacy. When you build with native tools, you’re not relying on third-party runtimes or browser sandboxes. You control the data flow, the permissions, and the user experience. Liquid Glass, as a native visual layer, reinforces this trust. It’s not rendered by a contrived engine—it’s part of the OS, part of the promise that your app respects the user’s environment.
Not Just Apple
Apple is investing heavily in native frameworks like SwiftUI, Metal, and Core Animation—and promoting design languages like Liquid Glass. This isn’t just about style; it’s about keeping developers and users engaged and ensuring that the best apps are built using Apple’s tools.
But this isn’t just Apple’s responsibility. As developers and users, we should push for better performance, stronger privacy, and less energy waste across all platforms. Native development enables that—and Liquid Glass helps showcase it.
Conclusion: A Call to Build Better
Liquid Glass is more than a visual effect. It’s a symbol of what native development can achieve: speed, privacy, elegance, and integration. In a world full of generic, web-wrapped interfaces, it reminds us that software can be both efficient and expressive.
Let’s use the tools that make our apps feel alive. Let’s build with transparency—in design, in data, and in intent.