Julio Biason is a user on functional.cafe. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

Personally, that didn't seem like a huge , although people with Macs will beat me for not calling "dark mode" huge.

As Google is doing, Apple is focusing on their assistant, and seem to keep a safe distance from the "creepy" factor -- something Google ignored and went way above the threshold with duplex.

Not huge steps on iOS, some QoL on macOS and watchOS... And I guess that's it.

Julio Biason @juliobiason

Oh, almost missed a really important point of :

The "not merging" macOS and iOS.

Apple may scream as much as they want, but building common libraries for all their platforms (ARKit, Metal, AppKit, WebKit, etc) is *merging* the platform. Also consider that they use the same programming language (Swift) and soon enough you will be able to build macOS and iOS apps from the same source.

Sure, it's not same *binary*, but still its the same thing.

· Web · 0 · 0

And don't forget that, on platforms, you define the application interface with Storyboards.

So you can have the same code, responding to the same button (click or tap), by simply creating different Storyboards for macOS and iOS.

And those storyboards can reside inside the same source, without conflict.