Duet Display Offers Tethered Solution to Turn an iPad into an Extra Display for Mac [Updated]
While there are several apps designed to turn the iPad or iPhone into a secondary display for a Mac, the most popular options use Wi-Fi, which can render them all but unusable at times due to unavoidable lag. A new app from developer and former Apple Engineer Rahul Dewan aims to solve these lag problems with a tethered solution that turns an iOS device into a more reliable secondary display.
Duet Display, which is launching today, is the one of the first apps that transforms the iPad and the iPhone into an extra display for the Mac using a Lightning or 30-pin cable. By sending data over a cable instead of Wi-Fi, Duet Display is able to greatly improve on the lag is typically present when an iOS device is used as a secondary display.
Duet Display offers both a Retina mode and a non-Retina mode, along with options for 30 or 60 frames per second, and it's easy to install and setup, requiring just the Mac app, the iOS app, and a cable to connect the two devices.
The Duet Display app is inarguably an improvement over other options today, but it is not a perfect solution. As detailed in the video walkthrough of the app below, MacRumors experienced some issues when testing the app. On a 2012 Retina MacBook Pro, Duet Display's Retina mode caused a significant amount of cursor lag, rendering the app nearly unusable, and the CPU usage climbed to well over 200 percent.
Non-Retina mode (which is enabled in the app by default) offered a more lag free experience, but the trade off caused the secondary iPad Air 2 display to look fuzzy -- a disappointment given the inherent clarity of the screen on Apple's newest tablet. Non-Retina mode in Duet Display degrades the quality of all Retina displays to a noticeable degree.
According to the developer, performance is better on Macs released in 2013 or later, and users who only want to view one static window may not have any problems. Furthermore, many users may find the utility of a secondary iPad or iPhone display to be enough to outweigh the lack of a Retina experience.
Though the iPad Air 2 and other Retina devices don't look good in non-Retina mode, Duet Display is a great solution for older iPads that people might have little use for. An original iPad or iPad 2 does not have a Retina screen, and will work well with older Macs as secondary displays. iOS 5.1.1 is not yet compatible with Duet Display, but the developer is working on a fix.
Along with the Retina issue, potential buyers should be aware of some other small issues that we ran into. Even in non-Retina mode, on a 2012 Retina MacBook Pro, there was some slight cursor lag, and we also had problems with visual artifacts on some apps. When watching YouTube videos, for example, there were some occasional performance blips.
The developer assures us that he is working on improving Duet Display, and he plans to release iterative updates in the months to come to clear up lingering problems. As he suggests, it's better to have an app that works most of the time with just a few problems rather than one of the existing Wi-Fi solutions that can be almost non-functional.
The Duet website claims that all Macs using OS X 10.9 or later work with the app, as well as all iPads and iPhones, but MacRumors was unable to get the software to work with a 2010 MacBook Air running OS X 10.10.2. According to the developer, the issue was due to the 10.10.2 beta software, which does not work with the app.
Duet Display may not provide the perfect secondary display experience, but in our testing, we found that it was more reliable than current Wi-Fi options, and we believe it's a fantastic way to make good use of older iOS devices.
Duet Display for the Mac can be downloaded from the Duet website for free. The accompanying iOS app can purchased from the App Store for $9.99 for 24 hours, and then the price will go up to $14.99. [Direct Link]
Update 12PM PT: Some of our forum members have not been able to get Duet Display to work on an iPad running iOS 5.1.1, and the developer has asked people who want to use it with an iPad running iOS 5.1.1 to wait for an upcoming update before purchasing.
Top Rated Comments
Add your iPhone for the MacSreenOctopus for even more engagement!
Spaces is nice; but Spaces is a fundamentally different solution since it does not allow you to view the content of two Spaces simultaneously the way you can with multiple displays.
As someone who works remotely, this app was built for me. I do software development and most of the time have Xcode open in fullscreen, with two panes on my main display and documentation/tasks/email open on another (virtual) desktop. At home I am fine as I use an iMac with a second display attached. While i'm working anywhere else I lose that ability. I've tried things like AirDisplay, but they are way too inconsistent and laggy, especially on crappy wifi networks.
Working at a hotel for example. Or at my works actual office space, which is in another state - I no longer have to be confined to a single display when working on my laptop.
I'm trying it out right now and it isn't perfect, there is a slight lag that you can definitely feel, but as a small secondary display for $9.99 on your existing iPad I don't see why people in this thread are complaining about this.
The multi-level marketing person who hangs out at starbucks every day isn't the only person who would use this app :rolleyes:
- working on stuff while watching email or task list on iPad screen
- developing and having documentation windows on iPad screen
- doing architecture modeling work - the current model I'm editing on the main screen, and other models I'm referencing on the smaller screen
- ... kind of an endless list really... did you really need to ask why multiple monitors can be useful?
Btw why would you need 2 screens "on the go"? OSX solved this already with multiple desktops.
I remember the days when you ran beta software it actually meant something - It can always break and no heart feelings when it breaks because - its beta for a reason. Especially running a Beta OS and trying to run a new App which is (If you are a developer running on a beta OS you know if you install an app like this which is "whanky" by the nature of it) that it can easily break the OS. I dont mean whanky as a bad thing but installing lets say "virtual" display drivers is a kind of its own.
And no, app developers do not have to write on their product page a big DONT RUN THIS ON THE NEWEST BETA RELEASES. Other Developers running a beta OS should already know it or research it. And the public doesnt have to care.