Apple has made a visible change to the design of iOS 26, based on what the company calls Liquid Glass. Should this be seen as a response to the numerous mockeries from Internet users?
You can't please everyone. An adage that big tech companies surely have in mind every time they offer something likely to divide the crowds. The removal of a feature or service, the modification of an option... Inevitably, some people will complain. Sometimes they are a minority, but sometimes, almost everyone gets involved. Apple saw this clearly when the company revealed the graphical interface of the future iOS 26, based on what it calls Liquid Glass.
The transparent design did not fail to provoke a reaction from Samsung and Microsoft, who saw it as a pale copy of what they offered years ago. But beyond these digs between competitors, many users expressed their disappointment, even their aversion, at the choice of the brand with the bitten apple. Not to mention those who simply do not like the aesthetics of Liquid Glass, several feedback points to a major problem. So much so that Apple has reacted very concretely.
iOS 26 changes its design, Apple backtracks slightly with its Liquid Glass interface
If you have installed beta 1 of iOS 26, available since the beginning of June 2025, you probably frowned when you opened your iPhone's Control Center. The icons and other sliders on the latter stand out very little from the background despite the blur effect applied to them. You can see it on the left in the following image: readability is clearly not there. Fortunately, Apple has corrected this with beta 2, as 9to5Mac points out.
The background blur is much more pronounced, while the background has been increased to better highlight what the Control Center displays. The whole thing is much more pleasant to the eye, and we no longer need to squint to know what we're pressing. Should we see this as proof that Apple is listening to user feedback? It's impossible to say for sure. It's likely that internal testing already raised the issue, and that the change made here was already planned for the release of beta 1.
0 Comments