When Updates Create Problems: UX Lessons from iOS Liquid Glass

Silent Failures with Real Consequences

The Phone app navigation feels different for the sake of being different. The alarm snooze screen is oversimplified with oversized buttons that aren't the sleek design we've come to expect from Apple.

In India, my sister had calls from unknown numbers automatically silenced after the update. The result? Package delivery disruptions—drivers couldn't reach her, and she missed time-sensitive communications.

In Qatar, all messages from "unknown" numbers—including account debit alerts and OTPs—automatically went to Spam. I called my bank and visited my service provider to troubleshoot. The employee's response? "It could be the annoying new update."

The Bigger Questions

Did such a major issue slip through QA? Or was the assumption that all unknown numbers need to be blocked—without giving users an upfront choice—simply not validated?

These aren't edge cases. OTPs and delivery calls are fundamental to how people live and transact, especially in markets like India and the Middle East where communication patterns differ from the US.

What Startups Get Right

This experience made me appreciate how small startups—surviving on caffeine and fighting for bandwidth while drowning in Jira tickets—are able to focus on discovering and solving real pain points.

They don't have the luxury of revamping UI or features that weren't broken. They can't afford to create new pain points, friction, or aesthetic displeasure in the process. Every change has to earn its place.

The Core UX Failure

We eventually found the settings to manage this. But as busy users, we shouldn't have to dig around just to make sure an OTP or package delivery call arrives.

Turning this on by default, without consent or even a heads up, created unnecessary friction.

The principles violated:

Takeaway for Product Builders

Before shipping changes that affect core user workflows: