Streamlining the Presentation Kit - Amaz-Play Mobile Projector and Wapow Lightening to HDMI Cable

As a part of my work I give talks and do training many times a year. One of the things I learned long ago was that you cannot rely on the training venue to have all of the equipment you need to do your presentation. This is true in general - you can bank on the fact that they will fail to have a proper cable or connector or to offer an outlet for your device. The worst example of this was the "conference center" where I asked whether they had a projector I could rent, and they took me to a very dusty closet and said "you mean one of these?"

They were pointing at an overhead projector - the kind that people of a certain age will remember their teachers putting transparencies on to throw them up on a screen. This would almost be forgivable, except it was earlier this year - 2017.

Although it is getting better, historically things became even more complicated if you were bringing along your own equipment to hook up. Many places would happily direct you to the Windows laptop they have hooked up, and ask for your flash drive. I cannot count the number of times I’ve seen the smile first freeze, and then fade from their faces when I’ve pulled out my MacBook or, more recently, iPad, and indicated that I’d be plugging that in instead.

For those reasons I have, for a very long time, maintained my own presentation kit. The composition of this has varied a bit over the years, but the mainstays of it have been:

• An Apple TV (third generation) and its remote control
• A power strip with a 10’ cord
• A projector - specifically a ViewSonic PJD5133
• HDMI Cable
• VGA Cable
• Power cords for the ATV and the projector
• An Anker 5-port USB charger

(The iPad and iPhone are a part of the mix, but they are always with me instead of being part of the kit).

By far the biggest item in this kit is the projector. It has served me well over the past five years, but it is nearly a foot wide, three inches thick, and weighs more than five and a half pounds. The combination of the projector and the power strip have functionally necessitated that I maintain my presentation kit in a separate bag (in my case, an old Trager Backpack). This means that, whenever I go somewhere to do training, I’m hauling in at least two backpacks. It’s a first world problem, to be sure, but a problem nonetheless.

Given that the projector is the largest part of the problem (no pun intended), that seemed a reasonable place to start. Pica projectors have been around for a while, but they typically have very low light outputs (making them hard to see in anything but a very dark room), and they had historically been expensive. However, it had been several years since I’d looked at them, so I thought I’d give it a shot.

I landed on the Amaz-Play Mobile Pico Projector.

This device had a few key benefits for what I was looking for:

• It’s small - it will fit in your hand
• It comes with its own tripod and it will mount to a standard camera tripod
• It’s powered thru a micro-usb cable. This last part means that I can plug it in to the Anker USB charger rather than needing a slot in the power strip (I otherwise only use two slots - one for iPad and one for iPhone)

And while I was searching for the projector, I also came across this Wapow cable that sends from lightening to HDMI and also plugs in to power.

What the cable offered was the potential ability to plug my iOS device - iPhone or iPad - directly into the projector. This meant that I could also pull the Apple TV from the kit and that everything I was using was powered thru USB, so I could also pull the power strip out and just go with the Anker charger. Even with everything plugged in I would still have two ports to spare. The direct HDMI connector also means that it will work in those cases where I’m plugging into a television rather than a projector.

By way of comparison, these are the bare essentials of the old and new projector setups side by side:

I’ve had the kit out a couple of times since putting it together, and so far it is working well. The Amaz-Play projector is not as bright as the ViewSonic (of course), but it does seem to be bright enough. Because I tend to be cautious with such things - don’t want a presentation to fail for lack of equipment - I’ve brought the old kit along in its backpack for each of the trainings so far. However, I haven’t needed anything out of it, so it’s looking like that will be able to be left back in the office going forward.

There is a fan in the projector, and it does make some noise, but not anything significant. It does have a speaker, but it’s small, as one might expect. If your presentation includes audio, you may want to plug in a separate speaker (and it does have an output for that). It apparently offers wireless connectivity using WiFi, and there is purportedly an app for that, but I have not used it. The reviews on Amazon mentioning that feature are not kind, and it wasn’t something I planned on using. I typically plug in one iOS device and use the other as the remote over Keynote.

The WAPOW connector does get warm around the HDMI connector but so far that does not seem to be an issue. It does bear mentioning that the connector works for screen mirroring and playing slide decks (Keynote or PowerPoint), but it won’t play protected video content. This means that you can show video thru the YouTube app, but attempts to play Netflix, Hulu, Amazon Video, or anything from iTunes is going to fail. This didn’t matter to me, but it might be a limitation for others.

Files, iWork, and Dropbox - Resolved

At the beginning of the month I wrote about an issue with using Dropbox in the iOS 11 Files app with iWork documents in a shared Dropbox folder (yup - that’s a long, complex sentence to parse, made longer still by this parenthetical observation about it... sorry).

This issue appears to be resolved with the most recent update to the iOS Dropbox app, version 70.2.2,which came out earlier this week. I’ve had a chance to play with it for a few days now, including doing actual work, and it appears to be functioning perfectly.

What this means is that one can now open, edit, and save-in-place documents from iWork files that are stored in Dropbox on an iOS device. This seems a relatively simple thing - we’ve been doing it on computers for years prior to the development of the iPhone and iPad. However, it has been one of the key remaining limitations to the iPad when using it for work activities, particularly in conjunction with Dropbox. As I mentioned when I brought up this issue earlier in the month, the process for using these documents has looked like this:

Depending upon the app one uses, for much of the history of Dropbox on iOS, if one has wanted to work on a file stored in Dropbox, it’s been a multiple step process:

• Export the file from Dropbox into the app (which typically opens a copy of the file in the app)
• Perform the edits one wishes
• Export (copy) the edited file back to Dropbox
• Delete the copy from the app

The long dark winter of toiling at copy deletion on the iPad has finally come to a close!

Too dramatic?

Probably so, but in reality, it is actually a pretty significant change. I have been using an iPad for work since 2010. Initially it worked as a laptop replacement, but at this point it has largely replaced both my laptop and my desktop. I have a handful of tasks - mostly legacy activities that simply require older machines to run on - that I still need a Mac for, but the overwhelming majority of my work is done on an iPad or an iPhone. And to be clear, the multi-step process above wasn’t something that was preventing the use of these devices for work, but it was the rare, remaining activity in my regular workflow that was more complicated on iOS than on OS X.

Files, iWork, and Dropbox Issues

One of the banner features of iOS 11 is the addition of the new Files app, which works in a fashion similar to the Finder in Mac OS, and offers the promise of giving a central location for all of your file access needs in iOS. For those of us who have been shepherding around files from app to app ove the past seven years, this is an exciting prospect.

It is often the case that other developers aren’t ready to take advantage of the new features in iOS on day one. Sure enough, Dropbox was not ready to fully integrate into the files app on the iOS release date. However, I was pleasantly surprised to see that Dropbox shipped an update within a week of the emergence of iOS 11, promising to integrate with Files and, perhaps more importantly, allowing save-in-place.

What does this mean?

Depending upon the app one uses, for much of the history of Dropbox on iOS, if one has wanted to work on a file stored in Dropbox, it’s been a multiple step process:

• Export the file from Dropbox into the app (which typically opens a copy of the file in the app)
• Perform the edits one wishes
• Export (copy) the edited file back to Dropbox
• Delete the copy from the app

Much more complicated than the simple open-edit-save routine that one would prefer. What’s more, it’s easy to omit the last step in the routine, and end up with a batch of leftover files in the app, visually clogging up the works. To be fair, Dropbox has offered an API to allow apps to save into Dropbox - 1Writer, the text editor I use to write these posts, is an example of this. But Dropbox has never before embraced save-in-place for apps like Apple’s iWork office suite, which I use routinely for work. This means I’ve been routinely doing the dance I described above for the past several years. To say I was excited about the prospect of no longer doing this would be an understatement.

Unfortunately, it doesn’t work.

Let me dial that back just a bit. Strictly speaking, it does work to open an iWork file from Dropbox using the files app, and that file saves back to the same location in Dropbox when you close it. Just the simple open-edit-save routine that one hopes for.

Where the problem comes in is that this only works in an unshared Dropbox folder. Use a shared folder - arguably a primary reason for Dropbox’s existence - and things go directly south. It is possible to open an iWork document from a shared Dropbox folder using Files, but that’s where the joy ends. It is not possible to modify the file and save back.

When one opens a document under these circumstances one is greeted by a warning indicating "Couldn’t connect to iCloud".

Disregard that warning, and attempt to make any change at all to the document, and you’ll interrupted by a warning indicating "Couldn’t Connect: Pages [or Numbers] couldn’t connect to iCloud. There may be a problem with the server or network" or "Couldn’t Connect: Pages couldn't Connect to iCloud. Try editing this shared document later, or edit a copy."

The second warning suggests that the app (Pages, in this case) thinks this is a shared document - one that is being shared by multiple people using iCloud. It’s not - the only shared thing in the scenario is the Dropbox folder it is resting in.

Turn off the integration between Files and Dropbox and things continue to work the way they did before iOS 11 (well - except for Keynote Files, which now inexplicably cannot be uploaded to Dropbox from the iOS app at all, but that is outside this discussion). It’s possible that this issue is only occurring on my devices, but I suspect this is not the case. I’ve filed but reports with both Dropbox and Apple, and I’m hoping others experiencing this will do the same to get this issue addressed quickly - I’d really like to see this work as promised.

A Brief Flirtation with Google Drive

As is true for most of us, I have my systems for doing things, and I get comfortable in those systems. Still, it is good to periodically check out other options to make sure one is not missing out on something better.

I've recently been exploring the possibility of changing my email service, and I was considering the option of using Google's email service - not basic gmail, but rather the email thru their G Suite service, which allows you to use email addresses based in your domain (e.g. that end with your own address rather than "gmail.com").

G Suite, as the name implies, doesn't just offer email, but an entire office suite of features, many of which present the option of potentially replacing systems I already use. They have a secure video conferencing service (Hangouts Meet), they have their suite of office software, and they have an online file storage service, Google Drive.

Some of these things are of interest to me, while others are not. For example, I'm open to exploring Hangouts Meet as an alternative to our current service, but prior experience leaves me with exactly zero interest in Google Docs, Sheets, or Slides. The feature set in Apple's iWork suite is perfect for me, and it's integration into iOS devices, particularly the iPad, makes it a solid winner for me every time. I also am well aware, both from personal experience and from the reports of others, that Google has historically been slow to update the iOS versions of their products to use the features available on the iPad.

Among the products in G Suite is Google Drive. Aside from looking up documents from my kid's school, I had very little experience with this service. I'm a long-term user of Dropbox, but as I said at the beginning, it's good not to let comfort keep one from exploring other, potentially better options. Since, like most of the free world, I have a personal Google account, I also technically have a personal Google Drive. I decided to play with it a bit and see what I thought.

I downloaded the app to my iPad and made a couple of documents to put into the drive for testing purposes. Some of what I found was what one might expect. It handled PDF documents just fine - you can render a preview of the document, export it to another location, etc, just as you might expect.

The iWork files were another story entirely.

I specifically made up a Pages document for the test. What I found initially was that there is no preview option for a Pages file - rather, Google Drive just tells you that it is an "unsupported file type".

This isn't entirely surprising in and of itself. iWork files, as I understand them, are actually packages, and in the past that has confused some file systems. But it is inconvenient if you want to take a quick look at the document before opening it to make sure it is what you want. Dropbox and iCloud (naturally) readily render previews of these files.

While this is inconvenient, it is not necessarily a deal-breaker. I'd prefer to be able to preview my iWork files, since I use them regularly, but there isn't that much confusion between one file name and another for me.

But then something else happened: The Pages document that I had entered into Google Drive started duplicating itself. The first time I tried the app it multiplied the file into some 40 or 50 copies, and I said to myself "well, that's that, then" and deleted the app from my iPad. After a few days, and a little bit of thought, I considered the possibility that the experience might have been a fluke, so I tried it again, this time bringing files into the app in multiple ways. When I sent a copy to the app directly from Pages using "Send a Copy", it did not appear to make duplicates (though it did, inexplicably, append "-1" to the file name, despite there being no other file with that name in the folder). However, when importing from Dropbox what I found was that, it after it was sitting in Google Drive for a few minutes, it began to make multiple copies of that file without being asked to do so.

I'm not sure why this would occur, but if I were to consider Google Drive as an option for me, it would be in place of Dropbox, which would mean that I'd be sending a lot of files from Dropbox to Drive. I love The Tick), but I certainly don't need a replay of the attack of Multiple Santa to occur in my file storage.

Of course, there is also iCloud Drive on the iPad. What I found there was that any attempt to import a Pages document into Google Drive from iCloud Drive caused the file to simply hang there, with its progress bar seeming to be finished, and yet never fully resolving. This was only true for the iWork file. I was able, for example, to import a PDF from iCloud into Google Drive just fine.

One could argue that I was functionally warned up front that Google Drive wasn't going to play well with my files with the indication that the Pages document was an unsupported file type. I suppose that is true, to some degree. It's worth noting, however, that the iWork suite - Pages, Numbers, and Keynote - has been around now for over a decade, and it comes free with the iPad - this isn't a new product, nor is it obscure, so it seems reasonable to ask why a product that presents as a general storage tool would not be prepared to support these file formats properly. One suspects, if one is conspiratorially minded (as one might be) that it is because Google would prefer one to use their office suite.

A quick check of the weather finds that Hell has not, in fact, frozen over yet, so that won't be happening on my iPad.

So, as the title says, this was a brief flirtation with the product. I might have been able to live without the ability to preview my iWork files - though in retrospect, I do use that feature quiet frequently. Not being able to reliably import my files, and finding them duplicating like bunnies, however, largely seals (or, rather, breaks) the deal.

Orphan Apps

Like anyone else with a smartphone, I have a lot of apps on my devices - 145 on my iPhone 6s+, 165 on my iPad Pro. Some of these are apps I use every day, some routinely, and others only on rare occasion. And - lets be honest - a few of them are leftovers from a bygone era. Did I really download and play Heads Up!, the app from the Ellen Degeneris show? I guess I did, because here it stares at me. And I'm sure I'll play Plants Vs. Zombies again, so I'll just go ahead and keep it there in my games folder...

Some of the apps on my phone, as it turns out, have become orphans - applications that are still there, that I may use with some regularity, but which are no longer being actively developed by their creators.

When one goes searching for a given type of application there are often dozens of options to choose from in each category, and prices range from free to much farther up the spectrum, with options across that price range within every category. The array of choices can make selecting an app challenging - when you have dozens of versions of the same basic thing, which do you choose? Do you go with price, with features, with...?

I've begun to select apps based, at least in part, on a pair of different features: Longevity and active development. All other things being equal, I will prefer an app that has been around for a while and which has been actively and readily updated. In iOS, this information is available in the App Store on a given item if you scroll down a bit:

PC Calc, an advanced calculator app for the iPhone and iPad has been around for a long time - it's on its third major upgrade version (e.g. Version 3.5.3), and it's been updated as recently as March of this year. This is a clear example of an app being actively maintained by a developer who has demonstrated longevity in the iOS app market. In relative terms it's not an inexpensive app - $9.99 for a calculator app will seem to many a high price when there are multiple free options in the same category. But for my money a part of what these variables indicate is that the app will be much less likely to become an orphan in future updates of the operating system.

Unfortunately this perspective comes from experience. I have one app, for example - AccuFuel, a Mileage Tracker by a company called Appigo, which also makes a fairly popular to-do productivity app called "Todo" - that I've been entering mileage into since 2007, all told, and since 2011 for my current vehicle. All told, I have nearly four years worth of mileage data entered into this app (I am, shall we say, mildly fond of data).

Unfortunately, the company stopped updating the app back in 2010 and, while it continued to work for some time, it didn't make the transition to iOS 8. Since that update the entry interface is buggy (although it works), and it is impossible to export data out of the app. The company was aware of the problem, and claimed they were working on an update to the app.. Still - that was over a year ago, and nothing has happened with it. The company could have, at the very least, honestly admitted to users that they didn't intend to update or, ideally, provided an update that at least allowed the export to work so a user could get his or her mileage data out of the the app. Instead, it's clear the app is an orphan. I've given up up on it, and set up a spreadsheet for mileage in Numbers instead. While I like to support independent developers, it seemed best to move this task to an app developed by a more stable company.

And I'll be unlikely to use anything produced by Appigo in the future.

In other cases there is a middle ground, where I can see the orphan status in the cards. I have a speedometer app called aSmart HUD by Atoll Ordenadores. The app hasn't been updated for a year and a half, and while it works under iOS 9, some features are buggy (trip time sometimes starts in the negative numbers, which makes me seem faster than I am, I suppose, but cuts down on accuracy). The developer no longer lists the original app on the website (though it does have updated versions of it), and has provided no communication regarding intention on providing further updates or supporting this version of the app going forward. It looks like this apps parents are, metaphorically speaking, preparing to drop this app off at the orphanage.

Overall, the lesson in all of this is that I've found that it pays dividends to make some evaluation of the level of support and stability of the company producing the applications you use, particularly if I they are things that you intend to use over the longer term.

Old Soldiers

For the past decade we have been an Apple household. Among the reasons for this - and one that continues to surprise me - is the longevity of these machines. I may have mentioned before that my first Mac, a 2005 Power PC Mac Mini, continues to soldier on as our media server, a decade after I bought it and several years after it reached the end of its service as a work machine.

The Mini was replaced by a late 2006 iMac, which served for several years before being placed into retirement as a machine for my daughter to use for school. Still, longevity and all aside, it appeared over the past year that the iMac had finally reached the end of its useful life. It was having trouble running for any significant period of time without locking up, and varying white lines across the display suggested to me that the graphics card was on its way out. It was set off to the side, and replaced with a lightly used and well-cared for 2012 MacBook Air that I purchased from Dan Benjamin at the 5by5 Podcast network.

By "set it off to the side" I essentially mean literally that. It sat, for months, on the floor beside my desk, waiting for me to have the time to decommission it by wiping the hard drive and sending it off to the recycling center.

I finally got around to it over the weekend before Thanksgiving. I dragged the Snow Leopard disk out of one of my drawers-o'-technology, and used disk utility to do a secure wipe of the hard drive. Done right this takes a while, and I let it run for several hours (and overnight) while I did other things.

When it was done I noticed that, while running off of the install disk, none of the white lines appeared. This, despite the fact that it had been running for hours. Given this, I went ahead and did a clean install of Snow Leopard just to see what I'd get.

The iMac has been running more or less continuously since the Sunday before Turkey Day, a full two weeks now, with only a brief interruption due to a power outage. The screen is free of artifacts. Essentially, it appears that the machine itself was fine, it just needed a clean install to recover from nearly a decade of continual use.

Of course, now this leaves me wondering what to do with it. Its operating system is several generations behind (10.6.8 vs 10.11 for El Capitan), and it doesn't have some of the bells and whistles of the newer systems like Handoff, for example. However, a little exploring after the clean install finds that it does, for example, run the iWork suite just fine through iCloud.com (though, ironically, I had to install Google Chrome to do this). So, it could serve as a backup desktop system for now, I suppose, while it waits to take its turn as a media server when (if?) the Mini finally shuffled off.

Microsoft Office for the iPad? Maybe Not...

This excellent, elegant post at minimalmac does a marvelous job of outlining a reality that must be uncomfortable for Microsoft:

No one really needs Microsoft Office.

My company has been mostly an Apple iWork shop for some time now. Pages is our default word processor and, although we do a lot of training presentations, the truly exceptional capabilities of Keynote has kept my copy of PowerPoint gathering dust for some time.

The only exception has been Excel. We do a metric truckload of spreadsheets and graphs, and our invested time into the platform has made it harder to transition out. However, recent experiences with the "upgrade" to Office 2011 for Mac has us looking very closely at completing that transition. It should never take 45 minutes and a web search to figure out how to make a text box... Not to mention the f$@king ribbon!

For many people, for some time, it's been a common refrain that one must have Office to work on a computer. That refrain may no longer ring true.

(Tip of the hat to Daring Fireball for bringing this link to my attention).