My blind guess: due to the rewrite of the iBooks app in Swift, they did not find a swift way to take over the performance critical code in Objective C for the page flipping animation.
My blind guess: due to the rewrite of the iBooks app in Swift, they did not find a swift way to take over the performance critical code in Objective C for the page flipping animation.
I have no inside knowledge but I would be shocked if it was anything other than an aesthetic choice to eliminate the page curl.
The redesign of System Preferences / Settings in macOS 13 shows that they do not care about any details any more at all. It looks like some manager said: "Make it look like on iPad", and some overworked dev changed the UI in the way that was the least amount of effort, and they shipped it without checking if the result is usable at all.
Is it technically possible? Yes. is it easy? Maybe not.
1 https://www.apple.com/newsroom/2020/06/apple-reveals-lineup-...
Sure, they could put more people on any particular project, if they thought it was important. But that's not necessarily going to make a UI decision any better.
Nobody outside Apple is likely to know how these decisions were made. We just see the results.
You can blame companies for making bad decisions -- you can even describe them as "lazy" -- even if you don't know the exact details of the process the company uses to make bad decisions.
The logical conclusion of your argument is Apple has lots of money therefore they should have finished everything already.
The small team assigned to port Books to iOS16 probably decided that spending a lot of effort porting the one animation is not worth the opportunity cost that could be spent on literally anything else.
It's pretty easy and basically required to do anything useful if you need to support iOS 14, or god forbid, iOS 13
Every browser nowadays can imitate page flip with CSS only.