![]() The biggest question, of course, is whether Safari on iPadOS is actually “desktop class” in the way that Chrome OS or Safari on the Mac are. It probably doesn’t matter unless one of the answers there means a speed hit on slower or older iPads. I don’t know whether the touch optimization is part of that or if it’s another layer on top. Now, questions: to optimize these sites for touch, Apple says it is doing some re-rendering of the website on the fly to ensure they work on the iPad’s screen. So it was pretty easy to hit all of Google Docs’ menu buttons, and keyboard shortcuts were no problem. After that, though, Apple is optimizing that site to work with touch (and the iPad’s keyboard). That means websites won’t default to serving their mobile versions because they see an iOS-based browser. ![]() Still, this is leaps and bounds better than any Google Docs experience on the iPad before and will be a huge boon for anybody who depends on it for their work.Īs for how Apple pulled this off, I have a few answers and a lot of questions.Īnswers first: Apple is setting the “user agent” (the thing browsers use to tell websites what they are) to the desktop version of Safari. ![]() Since native apps generally work better than web apps on the iPad, I would still probably prefer Google fix its app. What exactly is Apple doing to make Safari “desktop class”?
0 Comments
Leave a Reply. |