121–130 of 337 posts
But no mouse support. :(
> Mouse support in iPad is real. In accessibility. Also full keyboard control for the entire UI (opposite of Voice Control.)
https://twitter.com/reneritchie/status/1135643633690992640
Update: Here it is in action: https://twitter.com/stroughtonsmith/status/11356536361455902...
Earlier quoted context omitted.
Is this really such a big issue though? There are hundreds of free calculator apps you can download through the app store.
The one you want is PCalc. It isn't free, but it's not expensive either.
Earlier quoted context omitted.
Huh. All these years I've never thought to do that, always thought it was just a four function calculator. Even the scientific calculator would look pretty silly blown up that large though.
IIRC phone-mode apps that allow it can run on an iPad in a framed mode so they don't look too weird. I get why they don't do that with the calculator because it'd be "poor UX" but "what do you mean I spent $1200 on this and there's no fucking calculator, my Apple phone and laptop both have one, you mean I gotta go sort through the app store to find something that's not gonna show me ads, then probably pay some more m…
I am nervous this means Apple will hold back features from iOS to get people to buy an iPad. For example, they announced the new Files app with iPadOS but there is no reason that shouldn't all be available on an iPhone.
iOS is getting files and gamepad support: https://www.apple.com/ios/ios-13-preview/features/
I have a 30$ 8BitDo Bluetooth controller (that works on PS4, Xbox, Switch, Windows, MacOs) that I'd love to just throw in my travel bag with my iPad when I'm on the road.
This feels like it could become a repeat of Android Honeycomb, but iOS is a much more mature operating system now than Android was at the time, so I guess we'll have to wait and see.
Consider that most of the iPadOS features shown are refinements of or much-asked-for enhancements of existing features:
- Multi-document Split View
- Slide Over app switcher
- Network share and external media support in the Files app
etc.
[edit: props to snazz, who corrected me on the iOS split view release.]
the multi-tasking/multi-window looks incredibly complicated, full of hidden gestures/commands that aren't really discoverable
(And why on Earth does iOS allow me to split a portrait mode vertically, creating two thin strips that are seemingly useless for any work?)
Earlier quoted context omitted.
Weird. As a developer I haven't found Apple to be thumbing their nose at me. Many of their features are genuinely useful for my development e.g. TouchBar.
Genuinely curious: how have you found TouchBar useful for development? I think you're the first dev I've seen say that.
SIDECAR!!
Earlier quoted context omitted.
What happened with Honeycomb?
AFAIK, Honeycomb was primarily for tablets due to the (then current) UI scaling terribly and primarily being for portrait orientation. This was the era of 320x240 screens, after all, so there was bound to be some issues when scaling that up to tablet resolutions. Since most of the improvements ended up being useful for the upcoming "phablets" as much as tablets, Google just merged those features into Jelly Bean and g…
No, not at all. Android's UI has scaled exceptionally well since long before then, and nobody on Android was using 320x240 screens at that time. Android had already long since done the high DPI jump from 320x480 (HTC G1) to 480x800 (Nexus One).
You need a UI that takes advantage of the extra screen real-estate, yes, but there was nothing about Android's core UI toolkit that failed to handle that in any way.
> Since most of the improvements ended up being useful for the upcoming "phablets" as much as tablets, Google just merged those features into Jelly Bean and gave up on a separate tablet UI.
Google never actually forked Android for tablets, so there was nothing to "merge." They just focused on the tablet UIs & devices such that the phone ones had bugs. You can boot up Honeycomb on a phone-sized device and poke about. Everything's basically there, it's just super buggy.