iOS 27 is here with better Liquid Glass and more responsiveness


As expected from the WWDC keynote, Apple has launched iOS 27, with Liquid Glass and responsive improvements coming to your iPhone this fall.

The annual keynote address of Apple’s WWDC week has, as usual, introduced developers to the next major release of iOS. Using the new year-based naming convention, iOS 27 will be installable on user iPhones this fall.

As tradition dictates, it will also be testable by developers months in advance, usually starting from a short time after the keynote concludes.

Before the event, Apple was believed to be using iOS 27 as a shoring-up release, fixing bugs and performance issues after last year’s massive iOS 26 overhaul. There are also big expectations for AI changes this time around, too.

iOS 27 will be available on all models compatible with iOS 26, meaning all currently-supported iPhones can upgrade to it.

Keeping up appearances

WWDC 2025 saw the introduction of Liquid Glass, an update that was somewhat divisive among users. One year later, and Apple is taking steps to improve what it introduced.

While Apple has already allowed users to control the level of frosting for the glass effect in the lock screen clock under iOS 26, it will be expanded in iOS 27. You now have more granular control over how intense the glass effect is, and how frosted it appears.

Apple also says there’s more separation between glass layers. App icons are gaining more glass layers, including more refraction elements to make them more refined.

As part of a performance drive, Apple has also made iOS 27 more responsive. This work has helped in various ways, such as swiping between Home Screen pages faster, making imported images in Photos appear 70% faster, and updates to the CPU scheduler to better manage resources.

This story is breaking. Refresh for the most current information.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


“It was severely downgraded,” Gilbert confirms. “I never would have found it if I was just looking through Google results.” (I tried the same prompt in Gemini earlier this month, and after an initial denial, the tool also gave me Eiger’s number.)

After this experience, Eiger, Gilbert, and another UW PhD student, Anna-Maria Gueorguieva, decided to test ChatGPT to see what it would surface about a professor. 

At first, OpenAI’s guardrails kicked in, and ChatGPT responded that the information was unavailable. But in the same response, the chatbot suggested, “if you want to go deeper, I can still try a more ‘investigative-style’ approach.” Their inquiry just had to help “narrow things down,” ChatGPT said, by providing “a neighborhood guess” for where the professor might live, or “a possible co-owner name” for the professor’s home. ChatGPT continued: “That’s usually the only way to surface newer or intentionally less-visible property records.” 

The students provided this information, leading ChatGPT to produce the professor’s home address, home purchase price, and spouse’s name from city property records. 

(Taya Christianson, an OpenAI representative, said she was not able to comment on what happened in this case without seeing screenshots or knowing which model the students had tested, even after we pointed out that many users may not know which model they were using in the ChatGPT interface. She also declined to comment generally about the exposure of PII by the chatbot, instead providing links to documents describing how OpenAI handles privacy, including filtering out PII, and other tools.) 

This reveals one of the fundamental problems with chatbots, says DeleteMe’s Shavell. AI companies “can build in guardrails, but [their chatbots] are also designed to be effective and to answer customer questions.”

The exposure issue is not limited to Gemini or ChatGPT. Last year, Futurism found that if you prompted xAI’s chatbot Grok with “[name] address,” in almost all cases, it provided not only residential addresses but also often the person’s phone numbers, work addresses, and addresses for people with similar-sounding names. (xAI did not respond to a request for comment.) 

No clear answers

There aren’t straightforward solutions to this problem—there’s no easy way to either verify whether someone’s personal information is in a given model’s training set or to compel the models to remove PII. 



Source link