4 ms·
> Combining the iPad and Macbook is equivalent to rolling the iPod into the iPhone. It really isn't, Apple is right that the interaction models are too differe
by simonh 10y ago
> Combining the iPad and Macbook is equivalent to rolling the iPod into the iPhone.
It really isn't, Apple is right that the interaction models are too different.
The argument Microsoft make that you can have your cake and eat it, have a device that's an ideal tablet and an ideal laptop, has failed. The compromises are too great. Desktop software has interaction targets that are too small for a touch interface and the mouse interaction model doesn't map across to touch. But supporting both touch apps and desktop apps on the same device is a non starter. You can't require all your app developers to implement two different UIs every time.
The iPad Pro optional keyboard doesn't prove anything in this regard. It's just a dedicated text input device, not an alernate primary interaction mode.
Note that MS and Apple approach this from opposite directions. The MS solution is primarily a keyboard interface with touch as an ancillary mode. The iPad Pro is primarily a touch device with an ancillary keyboard mode.
But desktop software on the Surface is next to unusable in tablet mode. Meanwhile iPad software is perfectly usable with the keyboard attached. But it achieves this by decidedly not taking full advantage of the horizontal interface. There is no trackpad on the iPad Pro keyboard and no mouse support. For iPad software, they serve no purpose. That's why even with keyboard attached the iPad is decidedly not a converged device. The keyboard is not a primary interface, it's really just a text input peripheral with some convenience UI interaction options. There will never be iPad software that requires the physical keyboard.
- dfcowell 10y agoThe point isn't that you can use all of your desktop apps on a touchscreen, it's that the device can adapt to context. I'll never use Affinity Designer on my Surface without it either plugged in to my 34" display or, at a stretch, the Type Cover. The UI doesn't work for touch input. Doesn't matter. I likewise will probably never use Drawboard PDF with a keyboard and mouse. Again, doesn't matter. It's so quick to transition from touch/pen to keyboard/mouse that it's a nonissue. You can always use the input method most suited to the task at hand.
- simonh 10y agoThe only world in which the 'device adapts to me' model works is where the software adapts as well. If I have software that only works well in tablet mode and other software that only works well in laptop mode, I'm the one who has to do all the adapting to switch between them. In all Honesty, I'd rather carry two different devices completely optimised for the different interaction models than deal with all the compromises of a toasterfridge solution.
- spronkey 10y agoLet's reset the expectations, and answer the question again. If you could buy an iPad Pro, that runs all the iPad apps, has a touchscreen with the awesome pen digitiser, that was also as fast as a Surface Pro, and could run all the desktop apps within the same OS as well (even though the desktop interactions might by in large require a keyboard and mouse/trackpad), would you do this in preference to either the current iPad Pro or the current Surface Pro? Yes, yes I think you would. Developers shouldn't be asked to build hybrid apps. They should be given the option to build hybrid apps, desktop apps, or tablet apps, and have all of those solutions deploy on the same hardware.
- simonh 10y agoIf it didn't compromise the device design, didn't compromise the OS design in either mode and also provided strong and clear incentives to app developers on both the desktop and tablet mode apps without tradeoffs, and also was crystal clear about app discovery and acquisition for each mode, sure maybe. I just don't think those are achievable goals in practice. So trying to achieve them is a fool's errand. On the hardware side compromise is inevitable. On the software side look at the problems Apple has with pushing forward both the Mac and the iOS platforms. They're actually doing a fairly decent job pushing forward the Mac with new hardware features, radical designs and annual OS updates. Even so there are cracks. The App Store model is a sore point, the pro desktops are woefully out of date and there are widely-voiced concerns over the general quality of their desktop software and tardiness with iWork and other app development. How would strapping iOS and MacOS together in one device help this? When one side of the system is lagging behind and suffering from issues, you still have the other side to prop it up, right? Actually that's a horrible pit trap. The more successful side of the system will suck user focus, developer attention and platform owner resources away from the side that's struggling. Why put resources there when the other side of the system is doing so well? Rather than prop up the weak side, it pretty much guarantees condemning it to a death spiral. So no, I would not like to both have my cake and eat it, because I know that is not possible without compromises and risks that I am not prepared to accept.
- partiallypro 10y ago> The argument Microsoft make that you can have your cake and eat it, have a device that's an ideal tablet and an ideal laptop, has failed. Wait, it has? It has evolved, and continues to evolve; but I see no evidence that it has "failed." The Surface line has swelled to over $1 Billion, and hybrid devices are the fastest growing segment of the OEM market (the only growing segment, really.) The design process of apps is changing, in the same that is changed for the web. Apps will become responsive, and change with use input and share the same codebase. That's Microsoft's vision, and I think it makes the most sense. Even Google is starting to bend to this. Apple will be next. And in the same context, some apps don't need to evolve with input. Some apps just aren't meant to work with touch or vice versa, and that's ok. No one is going to run their IDE in touch, and no one is going to run their drawing program with a mouse. But the ability to dock and switch with the same device is appealing to customers and businesses. It saves money on device costs, and it has the possibility to save money on the development of software that wants to live in multiple worlds with multiple inputs.
- simonh 10y agoHybrid devices are selling well, but they're overwhelmingly not being used as hybrid devices. Only a tiny minority of users ever actually use the devices in tablet mode. See my reply to spronkey below on why this is a terrible sign. I get why MS and Google are doing this. Their tablet strategies have largely failed so they're trying to leverage desktop/laptop success to prop up the tablet side. I contend that it will have the opposite effect because it will cause an accelerated tapping away of attention and resources from the struggling platform to the more successful one.
- partiallypro 10y agoDo you have any data to back up the idea that touch input is not used commonly on hybrid devices running Windows? I'd love to see that data, because I don't believe it exists. There's a difference between running windows in "tablet mode" and just using touch casually as an input. I never put my Surface in tablet mode, but I have set my parents to always be in tablet mode because it's the only mode of operation they use. I dock my Surface and use it as my work station, but when I'm at home I use it strictly as a tablet. I have a strong feeling that others do similar. I also don't buy your notion that this is a "toasterfridge" solution. That's an Apple talking point.
- rz2k 10y agoI don't have an iPad Pro, but I occasionally use an iPad Air with a bluetooth keyboard. Command-tab for switching between apps is much, much more convenient than the touch interface. Using command-space then typing for launching apps is also more convenient that swiping then typing. Compared to general content consumption, I think that a large portion of work-like interactions with computers or tablets involves keyboards rather than either pointing devices or touch interfaces. I don't entirely disagree that there remains a large difference between the types of device for now. However, I do think the keyboard is a more significant differentiator than the type of pointing. For example, whenever I am doing much with Excel I use Windows in VirtualBox, because even though it probably cuts the CPU performance in half, I can use the Excel-for-Windows keyboard shortcuts and combinations rather than having to constantly shift to a mouse or trackpad.
- mrep 10y agoIpads will also need to add extra monitor support as a buying a macbrook pro and some monitors is worth the extra cost versus developing on the small screen real estate of an ipad. In addition, IOS app development is only supported on mac which will not be trivial to port to IOS. As @simonh said, touch and mouse UX are quite different and I don't see them being combined optimally in any near future.
- mrep 10y agoIdea extension: VR to enable users to maximize visual field for productivity, Magic leap type interaction which could bridge the gap between touch and mouse (pointing/"touching" at objects in a users visual field would require less effort than actually trying to tap the screens of multiple monitors) might be that synergy that will be able to bridge those gaps * . * keyboards are still probably going to be used for a long time though.
- adiabatty 10y agoI was watching an episode of Star Trek: Enterprise where Trip was staring at four PADDs in the mess hall while trying to rewrite warp-drive equations. Sometimes I wonder if multiple simultaneous iPad use is in the future of computing.