Portable iPhone workstation (stand, keyboard)

I’ve been using an ancient (2004?) Think Outside XTBT01 (a/k/a iGo Stowaway) Bluetooth pocket keyboard, and it does the job well enough. I like that it uses AAA batteries and won’t be eWaste when the battery chemistry eventually degrades past the point of usability. But. It’s kind of a cramped keyboard, the “Del” key being right next to the right arrow key f’s with my muscle memory, and it’s rare and expensive enough I think twice about taking it places where it might genuinely be useful. So. When I found the Rovinda Foldable Bluetooth Keyboard for $25 on Amazon, I decided to give it a spin. (I really wanted to try the ROYAL KLUDGE F68 for the low profile mechanical switches, but the 12" length meant it wouldn’t fit in a Loungefly, and it would be otherwise pretty awkward to carry out and about in most circumstances.)

I like it well enough. I need to re-learn how to type (using the home row this time, not whatever it is I’m doing now). It folds up nicely, it’s compact and light weight, and it’s not bad to type on. For an on-the-go device for, e.g., writing up the agenda for a board of directors meeting while waiting for brunch at the River Belle Terrace, it’ll do the job.

Unlike the iGo Stowaway, the Rovinda does not come with any sort of stand for the phone, so I also picked up this JSAUX Foldable Aluminum Adjustable Travel Phone Holder for $7. I wanted something that would fold up flat and this does the trick. It has a bit more surface area than a credit card, and is about as thick as 5 credit cards stacked, so it’s very portable. Seems well built too. This plus the keyboard and I should have a viable “get things done no matter where I am” setup.

iPhone 14 Pro on JSAUX stand with Rovinda keyboard
iPhone 14 Pro on JSAUX stand with Rovinda keyboard

Oh, one thing I found I had to do for my sanity: Go into Accessibility in the iPhone’s settings and under Keyboard, turn off Full Keyboard Access. Maybe there’s a way to use it that doesn’t involve my pulling my hair out in frustration, but for now, simpler just to kill that functionality entirely.


Comments