Apple Explores Using An iPhone, iPad To Power a Laptop (appleinsider.com)

According to the U.S. Patent and Trademark Office, Apple has filed a patent for an "Electronic accessory device." It describes a "thin" accessory that contains traditional laptop hardware like a large display, physical keyboard, GPU, ports and more -- all of which is powered by an iPhone or iPad. The device powering the hardware would fit into a slot built into the accessory. AppleInsider reports: While the accessory can take many forms, the document for the most part remains limited in scope to housings that mimic laptop form factors. In some embodiments, for example, the accessory includes a port shaped to accommodate a host iPhone or iPad. Located in the base portion, this slot might also incorporate a communications interface and a means of power transfer, perhaps Lightning or a Smart Connector. Alternatively, a host device might transfer data and commands to the accessory via Wi-Fi, Bluetooth or other wireless protocol. Onboard memory modules would further extend an iOS device's capabilities. Though the document fails to delve into details, accessory memory would presumably allow an iPhone or iPad to write and read app data. In other cases, a secondary operating system or firmware might be installed to imitate a laptop environment or store laptop-ready versions of iOS apps. In addition to crunching numbers, a host device might also double as a touch input. For example, an iPhone positioned below the accessory's keyboard can serve as the unit's multitouch touchpad, complete with Force Touch input and haptic feedback. Coincidentally, the surface area of a 5.5-inch iPhone 7 Plus is very similar to that of the enlarged trackpad on Apple's new MacBook Pro models. Some embodiments also allow for the accessory to carry an internal GPU, helping a host device power the larger display or facilitate graphics rendering not possible on iPhone or iPad alone. Since the accessory is technically powered by iOS, its built-in display is touch-capable, an oft-requested feature for Mac. Alternatively, certain embodiments have an iPad serving as the accessory's screen, with keyboard, memory, GPU and other operating guts located in the attached base portion. This latter design resembles a beefed up version of Apple's Smart Case for iPad.

Comments

You mean like my 6 year old Atrix

[Anonymous Coward]

Granted the Atrix was under powered, but we were doing that a long time ago. I ran a full linux desktop on my Atrix (hacked the webtop) and was running OpenOffice (before libreoffice was cool).

I had expected back in the day before they made the grand announcement of the iPad that apple would do something smart and do what this article suggests - but instead we got an iPad - a near complete duplication of the phone form factor - and now that phones are a little better everybody is ditching their iPads. Would've been nice if they had just done this from the beginning.

Totally abandoning their core userbase

[Solandri]

There are two primary reasons graphics professionals love Macs.

• Support for color profiles. Profiles are important not just for accurate screen colors, but for previewing how something will look when printed. Like newspaper and magazine editors need to do. Like poster and billboard advertisers need to do. Like packaging artists need to do. Windows' support for color profiles is half-hearted. It still dumps your loaded color profile if the damn UAC elevation prompt pops up (their method of darkening the screen outside the dialog seems to do it). It's done this since Win 7 and Microsoft still hasn't bothered fixing it. The companies which make color profiling equipment have had to make software work-arounds for it. On the Macs it just works.
• Resolution-agnostic fonts. This has been a part of Macs since their inception, and Apple developed Postscript based on the same concept. When you plug a monitor into a Mac, the Mac queries it for its model and dimensions. Then based on the screen size and resolution, it automatically scales fonts so that e.g. a 11 point font is the correct size. This is why layout artists love the Macs - what they see on the screen is exactly what it'll look like when printed, not just in terms of layout but also size. Postscript does the same thing except for fonts on printers. Windows doesn't even try to do this. You get that silly 100%-200% scaling option, where 100% is based entirely on resolution without any regard for screen size. This is why OS X had no problems switching to high-PPI "Retina" screens, while Windows still has problems with it. On the Macs it just works.

1) iOS doesn't support color profiles. While Apple does calibrate the screens, there's no way for users to add their own color profile. No way to add a printer profile. No way to switch to AdobeRGB if/when the iOS devices get OLED screens and you want to edit the full color information captured by your DSLR.

2) iOS relies on a fixed resolution. That's why when they increased resolution on the iPhone and iPad, they had to do it by doubling the resolution. It was the only way to insure that apps written with the old resolution would still display properly. Basically they have the same problem with old apps on high-PPI screens as Windows does. (Ironically, Android does support arbitrary scaling based on PPI. So Android is more more like MacOS and OS X in this respect than iOS is.)

An iOS-based laptop may suit the needs of the casual user (browser, facebook, office apps). But it's totally unsuitable for graphics/photo/video professionals.

Re:Totally abandoning their core userbase

[0100010001010011]

They're putting short term profits ahead of the long game. Long before the iPhone came out OS X came bundled with XCode. Anyone wanting to learn to code for the Mac could do it out of the box starting with 10.3. For a college student that wasn't quite ready to get started in Linux (And this was Linux 2003 mind you) it was amazing that I could compile stuff out of the box without dealing with cygwin on Windows XP.

If you coded in XCode the PPC-64, x86 and x86-64 migrations were relatively painless. When the iPhone finally got a dev kit the tools had been out for 5+ years. People were able to hop in to iPhone development. Distributed builds over ZeroConf have been supported for a while as well. Have a dozen machines sitting idle? Hit compile and distribute the load.

Apple has fallen completely on their face supporting the people that make the pretty widget iPhone apps. Unless they start churning out development tools there isn't going to be a machine to do iOS n+2 development on.