Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

iOS 27, iPadOS 27, and macOS 27

apple.com

Post reply on HN
Print view View original

161–170 of 496 posts

Re: iOS 27, iPadOS 27, and macOS 27

#161

Post by tensor »

Hamuko wrote: post #137

Updated my iPad to iPadOS 27 and disabled Reduce Transparency because I figured that they’ve fixed Liquid Glass. The notifications on the lock screen are still completely unreadable. What the fuck is Apple doing? Can’t even be happy about the bug fixes because my biggest one, Spotlight not getting keyboard focus when you use it, is still present.

MacOS 26 forced me to give up spotlight for Raycast. It would do this thing where new delayed results would steal highlight focus so hitting the enter button to select something from the list became a lottery. Would you select the thing you see or would something else replace it in the time you press the button.

I use Raycast now and it's 1000x better simply because it actually selects the highlighted thing.

Re: iOS 27, iPadOS 27, and macOS 27

#162

Post by teekert »

Hamuko wrote: post #146
GeekyBear wrote: post #106

Earlier quoted context omitted.

They literally give you a new slider to increase or reduce the Liquid Glass effect to align with your personal preferences.

Unfortunately the slider does not fix Liquid Glass. Notifications are still unreadable even when you go full opaque. You need to also toggle Reduce Transparency to actually get the UI to be opaque enough to be readable.

Jeez, it's an accessibility feature and they just turned it off!

I don't mind liquid glass and can handle the transparency mostly, but the notifications are just god-awful and difficult to read (white on light glass, using dark mode, who comes up with this stuff?).

But reducing transparency is a much harder setting now (should be "removing transparency"), I don't like it anymore, it also messes with the wallpaper. The previous setting was just right for me. Now the app squares are just black, very bad with dark icons.

Re: iOS 27, iPadOS 27, and macOS 27

#164

Post by samename »

jhickok wrote: post #128
Agingcoder wrote: post #59

I don’t want a new screen time experience , I just want it to work. Much to my surprise, it’s extraordinarily brittle, to such an extent that it’s virtually useless.

As a parent of kids with iThings, the parental controls/screen time experience is incredibly bad. I have no idea why they are not interested in having it work.

The more time kids spend on the device, the more revenue Apple generates. They don’t have any incentive for it to really work.

Re: iOS 27, iPadOS 27, and macOS 27

#165

Post by rwz »

I've just installed macOS 27 on my personal laptop and I'm losing my mind. My OrbStack app is now permanently stuck in Dock showing as "Running in Background"

There appears to be no way to keep it from the Dock without actually killing it or disallowing the "Running in Background" permission for it.

This is the stupidest forced opt-in feature I've ever seen.

Re: iOS 27, iPadOS 27, and macOS 27

#166

Post by bayindirh »

asimovDev wrote: post #159
bayindirh wrote: post #152

Earlier quoted context omitted.

I bet it will, because cross-platform virtualization and containerization is a boon for Apple. Also, Rosetta will stay for older programs (esp. games) and some Intel specific frameworks per Apple's docs. I bet with all the transistor count increase, that circuitry is a blip.

oh right, forgot about virtualization. Apple probably still need those customers that spend half of their day in Parallels Desktop

Also, being able to run x86 Linux binaries is important for developers:

https://developer.apple.com/documentation/virtualization/run...

Re: iOS 27, iPadOS 27, and macOS 27

#167

Post by Y-bar »

For the first time in years I will upgrade early. Apple Support required me to update to iOS 26 back in November or else they refused to troubleshoot an iCloud issue. The issue remains to this day and I regularly regret upgrading. But it seems many things about the interface has improved. Hoping for the best now.

Re: iOS 27, iPadOS 27, and macOS 27

#168

Post by kayodelycaon »

sippeangelo wrote: post #86
swinglock wrote: post #21

Earlier quoted context omitted.

How is the keyboard broken? Maybe I'm so used to whatever it is that I'm blind to it.

They have some nasty "dynamic tap zones" algorithm that dynamically resizes the hitbox for keys based on what it predicts you will type in order to reduce miss-taps. Anecdotally, it has just steadily been getting worse with every update. I swear I can be pressing the center of a key and it will select the next one over and immediately autocorrect to a completely different word than what I typed. I had the pleasure of…

Oh wonderful. That’s what’s happening to me. I’m an author and Apple‘s dictionary appears to be missing about half the more uncommon words in the English language. It’ll never recognize “prescient” in dictation for example. Some words it marks in red because it thinks it’s a spelling error. I know it’s not because I’ve used it, read it, and it’s in online dictionaries.

At least I’m macOS I can use Talon instead of the system dictation.

Re: iOS 27, iPadOS 27, and macOS 27

#169

Post by asaddhamani »

Someone1234 wrote: post #17

I've been using it for several months since the developer beta came out; overall I'm extremely positive on it. One of their better releases that seemingly focused more on quality and refinements than new-features. Siri is definitely worth using now, even if it remains still a work-in-progress/needs continued refinement. It can surprise you in good ways, but it isn't consistently good yet. The keyboard remains unfixed…

In my experience new Siri has been better only marginally. Still tons of I didn’t understand the query responses

Re: iOS 27, iPadOS 27, and macOS 27

#170

Post by lynndotpy »

GreekPete wrote: post #111
sippeangelo wrote: post #86

Earlier quoted context omitted.

They have some nasty "dynamic tap zones" algorithm that dynamically resizes the hitbox for keys based on what it predicts you will type in order to reduce miss-taps. Anecdotally, it has just steadily been getting worse with every update. I swear I can be pressing the center of a key and it will select the next one over and immediately autocorrect to a completely different word than what I typed. I had the pleasure of…

Ah, so that’s why that happens? I was gaslighting myself.

Yep; this has been the case since the very first iPhone, it can't be disabled, and there is no feedback it happens other than the typos. It is very crazy making and mind boggling.
Post reply on HN