5.11.12. iPad and the Incase Origami Workstation

The iPad writing station experiment continues. The latest addition is the Origami Workstation by Incase. This is a simple case for the Apple Wireless Keyboard that folds out into a supportive structure for holding an iPad. When I started this project, I was using the Apple Smart Cover to support the iPad in a landscape position, like a laptop. The Origami Workstation supports the same thing, but it supports placing the iPad in any orientation. iA Writer looks great in both, and it can be nicer and even more like a piece of paper to type in portrait, which is what I'm trying now.

I have yet to try even commuting with this keyboard, as it's not something I need at work. I use the iPad at the office, but don't do very much typing. Any input that I need on the iPad at work comes in via various cloud/sync solutions like OmniFocus, Notes, and iCloud. Still, I'm going to toss the keyboard and this case in the backpack tomorrow to see how it feels and fits. The aluminum keyboard is not small, and packing it around could start to mitigate the advantages of the iPad. However, I think the case will be a nice occassional throw-in for going to a neighborhood coffee shop (waiting on a new one to open in a couple of months) or maybe travel when I want to do some writing.

This makes me recognize some of the appeal of Microsoft's Surface and Windows 8 strategy, which is to promote a laptop/tablet hybrid. With this keyboard, I'm closer to that situation. I have more thoughts on this that I plan on posting in the future.

For this post regarding the Origami Workstation case and the Apple Wireless Keyboard, the takeaway is that this is a nice piece of kit that seems to compare favorably with other iPad keyboard/case combinations. Some other combinations combine the keyboard into the iPad case, and I don't like those. While I like having a keyboard for my iPad, it's not something I need for most of the day or evening. With the Origami Workstation, my keyboard is protected and put away most of the day and isn't taking up any more space. It does take up more space when it is in the backpack, but again it's not something I plan on taking with me daily. Integrated case-keyboard solutions also tend to force you into landscape mode - even the Microsoft Surface's savvy design does this. While this isn't necessarily bad, I do find that when writing long bits of text, portrait mode can be a much more natural fit. Since the Origami Workstation just unfolds into a supportive triangle, the iPad can be propped in either orientation. The iPad can even stay inside most cases that you can put on it.

It's also pretty easy to pop the keyboard in and out of the case. This is nice since I might want to use the keyboard on my lap while keeping the iPad on my desk. This is like the iMac where I can place the keyboard wherever is comfortable, independent of the display - something you can't do with laptops or integrated keyboard cases.

Finally, the Apple Wireless Keyboard is great. It's what I use on all of my iMacs, and is the same layout as on my (aging) MacBook. I'm used to the feel and spacing of these keys. The Origami Workstation lets me stay with that keyboard while letting me use the iPad like a laptop, desktop, or tablet as much as I want. The main downside is size, as the keyboard is taller than the iPad, and thicker due to its use of AA batteries. Since I expect to mostly use this at home, that's not a big deal. It's still a pretty compact setup.

The cost of the Apple Wireless Keyboard ($69 USD) and Incase Origami Workstation ($29) matches nicely with most of the top integrated keyboard case solutions which seem to average around $99-$129. This pairing is excellent for anyone wanting to do long writing on the iPad.

3.11.12. On iPad Sizes

With the launch of the iPad Mini, Apple's 7.9" iPad, there seems to be a lot of "this is the future of the iPad" or "this is the iPad we'll all use" comments in various reviews I've read. Without having used one, I'll say differently.

When the iPad was announced in January 2010, there seemed to be a lot of discussion about whether the iPad was a device for consumption or creation, and about whether it could be a suitable laptop replacement. Nearly 3 years into the iPad era, there seems to be a consensus that this device is suitable for creation and it can be a laptop replacement or alternative for many. It is also an absolutely terrific machine for consumption of both text and media, but I think that it's usefulness as a creativity machine has surprised many.

I believe this is strongest at the 10" side. I think that the iPad Mini will be a nice creative machine, but early reviews and indications seem to indicate that people are finding it most useful as a "pick up and read/search/view" machine. The Mini is something they can use while pacing around and talking on the phone. It's smaller and lighter, which some say "is exactly what we all want out of our devices" (while at the same time everyone is saying the iPhone remains too small and should be bigger, and the oddly sized Samsung Galaxy Note has a surprisingly good number of fans).

Personally, I want my iPhone to be the size that it is. It fits well in my pocket, where it spends a lot of its time. I can keep it in my pocket when laying on the couch or in bed for a mid afternoon weekend nap, and it does not bother me the way bulky old cell phones did in the past. But I fear that if it were any larger, it would feel uncomfortable like a Moleskine notebook. I think the iPhone is the perfect size.

Likewise, I think the iPad's full size is also perfect for me. Let me list the ways I use my iPad:

• OmniFocus. As a developer, my work desktop has a lot of apps and windows open, and keeping on top of my best laid plans was mildly annoying until the iPad came along. I do my planning on the iMac, entering in things I need to do to get some piece of work done, and then use the iPad as a separate dedicated screen for keeping on top of that list and marking things off. For a while, I was actually using a laptop for this, as that separate, dedicated screen makes it easier to find and reference what needs to be done when there are so many noisy resources needing my attention on my main work machine.
• Reading. I eat at my desk a lot, either with local take-out or sack lunches from home, and the iPad, mounted on my Compass iPad Stand, makes for terrific reading and is a good size for at-desk reading whether using Kindle, iBooks, InstaPaper, DC Comics, The Economist, or the web itself. I know the "mini" size is supposed to be better for reading, but the 10" iPad is great for its placement and distance on my desk at lunch time.
• Twitter. A wonderful, horrible distraction that is just a couple of swipes away while I'm working.
• Writing. I'm writing this on my iPad on a crowded but cozy CB2 metal desk in the kitchen area of my loft. The 10" size works great for writing with iA Writer, Blogsy, the built-in Notes app, etc. The not-much-smaller 7.9" is probably fine, but for me, I no longer need a MacBook Air now that I've finally added a selectively-used keyboard to my iPad. Laptop replacement? You bet. I'm not programming on it, but I know now that I could probably use this with apps like Diet Coda to get some work done from home needed, although I do have good full-computer fallbacks for that.
• Music. There are some terrific music apps for the iPhone and iPad, and the good iPad ones are quite terrific. Again, I find the larger screen works well for those apps. Some apps like the Korg iElectribe come close to matching the physical size of the full Electribe machines. The iPad is not yet an indispensable piece of my music setup, but it's a fun and useful addition on occasion.

There is also a lot of heavy consumption use in the evening as an IMDB and Twitter lookup machine while watching movies or TV that could possibly be served just as well by the iPad Mini, but the occasional video consumption (Netflix, Hulu, iTunes movies, HBO Go) also seem like they're better suited to this larger screen.

So for me, this 10" iPad is just fine. All of this talk about how we'll all be using 7 to 8" tablets is like saying we'll all be using the 11" MacBook Air and no one will use the 13"; or that no one will use a 15" laptop when there is a 13" available; or that no one will use a 42" TV when there is a 32" available. It all depends on need, use, and budget. Or as Horace Dediu says, it depends on the job(s) for which you're hiring the device.

I have never seen so much pointless talk over a device taking on an additional size as with the launch of the iPad Mini. It's just another size. It's not the second coming of the iPad, nor is it the doom. In my mind, there's nothing that exciting about the iPad Mini at all. I'm not saying its a bad device, it's just what it is: a smaller iPad.

Wake me up when there's a 13" iPad and iOS finally grows support for intelligently dealing with different scales and dimensions.

 

12.7.08. iPhone 2.0 and the iTunes Remote

Like many others, I was bit hard by the server failure that crippled the big iPhone 2.0 update process this morning. It robbed me of said morning, and I opted to take the day off work. It's been a bit of a tough week, and last night I did my first show in months, and had company over until past 3AM afterwards. Since things are about to get crazy at work, I decided that I needed a day to catch back up on sleep while waiting for my phone to work again.

A few hours later, the phone worked.

One of the most surprising and enjoyable elements is the iTunes Remote. Full and comprehensive access to my fairly large iTunes library on the iMac: all playlists, etc, with the ability to control volume, jump around in songs, see artwork - just like the 'iPod' iPhone application! Sometimes, particularly in the morning, I might turn on Front Row and carry the nice little Apple Remote around with me to have some control over songs while getting dressed in the upstairs loft, but using the remote from up there often required reaching far over the edges and trying to point the remote in the direction of the iMac, just to be able to skip forward a track or two.

But now, I can control it all from the iPhone, without needing a line of sight! In fact, this might be what pushes me to pick up an Airport Express or two (one for speakers in said upstairs loft, maybe one to bring music out on the patio or the bathroom). Full access and control of 29 and a half days of available music playable out of real speakers and controlled by an untethered iPod size device - beautiful.

10.6.08. Looking to a Snow Leopard Winter.. er... Summer.

I’m a bit excited about Mac OS X “Snow Leopard”. Few user-visible changes, with a focus on fine-tuning and giving developers better access to capabilities of modern hardware. It appears that Apple’s experience in making a lightweight Mac OS X “Core OS” for the iPhone will also drive this release.

One of my favorite operating system releases was OS/2 “Warp” (OS/2 3.0). OS/2 2.0 was a fascinating creature - completely divorced from Microsoft, OS/2 2.0 delivered an aggressively object-oriented runtime built on SOM (a desktop implementation of some of CORBA 1.x, I believe). It was radically different from Window 3.x. It’s hardware requirements were a bit high for the times, but it was a solid OS.

What impressed me about OS/2 3.0 “Warp” was that it’s system requirements were in some cases significantly LESS than OS/2 2.0, while performing better. I don’t know of any majoro user-visible adjustments (this was before operating system releases became the giant dog’n’pony shows that have been expected since both Windows 95 and Mac OS X).

I think that even though desktop and laptop hardware continue to get better, the rapid growth rates seen between 1995 and 2005 are slowing down. Now the pressure is on connectivity, portability, and storage storage storage for all of those mp3s and movies and photos. I think both Windows XP and Vista, along with Mac OS X 10.4 and particularly 10.5 have been a bit cavalier about their usage / expectation of resource availability without doing a good job of cleaning up afterwards. Removing a ‘TemporaryFiles’ folder used by Apple’s “Soundtrack Pro” program gave me back 25 GB of disk space. 25GB! I expect that when doing lossless audio work, I’m going to leave a lot of turds behind. But not that many. That’s an accumulation over only a few months. Now some of that may have been due to crashes brought on by the instability in Mac OS X 10.5.2’s audio subsystem (particularly in relation to some USB audio devices). But still - 25 gig! Over the course of just a couple of months!

I think that Apple is at a good place to do this. Good housekeeping is required - otherwise you end up with situations like Mac OS ‘Classic’ or even Windows Vista, where there is so much old baggage, bad hacks, outdated mentalities, etc, all in play; it makes it difficult to move the platform forward. Some companies and developers have always been mindful of this, electing to keep their products lean and fast, always (see Ableton Live - hands down, the most impressive audio application out there). Other companies don’t support that philosophy for whatever reason - backwards compatibility, rush to market, a combination of the two, etc.

This far into the Mac OS X life cycle, there’s not many new dog’n’pony features to add. The API’s have stabalized, the developer tools offer more than they ever have (Interface Builder 3 is a terrific update), the Finder and Spotlight are actually fast and usable; applications and utilities from both inside and outside of Apple are going to really shine on Mac OS X 10.5 with all that it offers to developers. A new age of PDA’s are upon us, whether it’s a device like an iPhone, an ultra-mobile Asus Eee-PC style portable, or even the Macbook Air: secondary and tertiary devices are really taking off.

I think that an underlying aspect part of the ‘Snow Leopard’ plan is to allow such devices, made by Apple (naturally), to proliferate. When it was announced that the iPhone was built on Mac OS X, I was surprised - Mac OS X has been a pretty wasteful OS - or at least, one that would consume more resources than realized (often for caching, interestingly enough). A standard install is full of crap that may be useful, but often takes up space. How many gigabytes of printer drivers now? To take the fine tuning and resource management ideas from the iPhone variation of OS X into the main system is what I think will allow for Apple to finally make the Eee PC style portable that everyone wanted the Macbook Air to be.

I’m putting my money on some kind of small device, priced around $600-$800, coming out at or around the same time as Snow Leopard. Combined with Mobile Me and Snow Leopard Server’s increasingly Exchange-like feature set (but better priced and more understandable for small organizations), the ubiquitous-data-access capability is there.

Today’s full-featured laptops (MacBooks, Inspirons, whatever) are their own entities; my aging iBook gets used rarely as I just don’t have as much data or software set up on it, and it’s sometimes too big of a pain to keep in sync.

The XO and Eee-PCs (or whatever they’re called) are also separate from the rest of one’s life; useful as a fun or educational toy, or as a geek’s favorite gadget to see what they can get running on such a little device. Most of the other developments I’ve seen in this area have centered around “how cheap and how small can we make a laptop/portable that will run (Linux/Windows XP)”. But outside of education, if this is the only focus being given, then these companies are going to be making nothing more than the next round of casual gadgets that get tossed or buried after a few months - especially if a key factor of what made Palm devices so popular (for a while) is completely neglected.

The Macbook Air is deliberately designed as a complementary computer, using the master’s optical drive even. While sexy, I think the Macbook Air misses the mark on a few items. But I think it’s an indication of things to come - laptops deliberately designed to complement your main machine. Smaller devices, from the Palm to the iPhone, have done this. And they’ll also be designed to work with your (or your company’s) data, which the Blackberry has done (and the iPhone will do when its new ‘enterprise’ support rolls out). Getting this onto other devices, without being constrained to an enterprisey system like Notes or Outlook, is where things really appear to be headed. It’s certainly something that I’d like to have. And the more I look at Snow Leopard, the more I believe that Apple is sneaking ahead of the crowd into delivering this into the hands of consumers. They’re skating to where the puck is going to be.

Granted, Windows “Live Mesh” looks to be heading in the same direction. But after Vista, Microsoft needs to reign in the Windows kernel and distribution. Windows Server 2008 and some of what has been leaked (or speculated) about “Windows 7” seem to indicate that Microsoft is aware of this. And how could they not be? But I think that even with their vast resources, Microsoft has a long ways to go to catch up - even though it appears that they’ve been playing in this area (tablet computing, ultra-mobile pc’s) for a while. A deep cleansing of the Windows core is desparately needed. And then a deep re-implementation of the UI may be needed.

Apple had a terrific luxury (and great idea) with the iPhone. While sharing the same kernel and many same APIs as the desktop (and server) Mac OS X, it has an entirely new UI that is dedicated to its intended use. Windows CE, on the other hand, tried to bring the Windows 95 look and feel to tiny devices and now I’m really not so sure it was a good idea. It allowed Microsoft to punt on some usability and design issues by falling back on the way things work on the desktop. I still see this, even in some of the newest and fanciest “iPhone killers”: some of these have a very fancy launcher app; some even have a very fancy phone and contact app that spins around in 3D and responds to gestures. But then, suddenly, you’re in the tiny-font, tiny-scrollbar, pixelated, stylus-driven world of the interior. It’s like going into a grand building like The Plaza (back when it was a hotel, at least), and finding the inside full of grey linoleum floors, flickering flourescent lights, and cinderblock walls reminiscent of an old hospital or elementary school. Quite the let-down (a lot of courthouses are like this, actually).

I also think Apple was smart to NOT have an SDK at the launch of the iPhone. I bet they would have liked one, but I think the iPhone had to launch when it did, and perhaps not-quite-everything was ready yet. If one looks back at the classic Macintosh and Palm devices and operating systems, you see systems that pulled of very clever hacks to fit within the price and size constraints of the time. The Lisa was much more than a $10,000 Macintosh - it had many features from power management to an OpenDoc style multi-tasking document based UI. But to offer those features, it was priced well out of reach. The Macintosh squeezed as much as it could down into a 128K Ram machine, and the compromises they had to make in order for that to work would end up haunting the company until its near-death. The Palm, too, took the ideas of the Newton and other tablet devices and stripped them down into a size and price point approachable by the masses. And like Apple, the design decisions that were made to make that work have crippled the Palm OS so much that even Palm sells half of its devices with Windows CE (or whatever CE is called these days). Those compromises are bad enough to deal with on your own - but when having to support third party developers and then provide some degree of backwards compatibility, it can just kill you.

By taking the time to put the SDK into beta, to polish up the OS and its APIs, I think Apple will avoid a repeat of that story. Instead of having to support every little exposed compromise that may have been made to get the iPhones out the door last June, Apple could tidy them up. By using a beta period for the SDK and next major release of the software, Apple can respond to feedback and make changes and adjustments before they become permanent.

1.11.07. AppleScripting Across the Universe

After a long day at work, I wrote a long message in Basecamp about what I had accomplished, how to access it, etc. But I forgot to submit the message! Crud. I wanted to send it out before morning and didn’t want to go into the office. I couldn’t get any screen sharing connection to go between the machines. I just had a handful of SSH leaps.

AppleScript to the rescue!

This is probably the most AppleScript that I’ve ever written. Fortunately, Safari supports the command do JavaScript ... in tab. After some floundering around with a similar setup on my local machine, I finally figured out AppleScript’s interesting reference notation and was able to ferret out the window and tab containing the unsent message, add some text to the message’s textarea element, submit the form, and return the extended value.

tell application "Safari"
    set message_tab to current tab of window named "Web site > New message"

    set extended to ".... Fun fact - i wrote this before i left the office and forgot to submit it. as a result, i now know how to submit forms like this via AppleScript."
    set post_body_value to "$('post_body').value"
    set extend_value to post_body_value & " += '" & extended & "';"

    do JavaScript extend_value in message_tab
    set body_value to do JavaScript post_body_value in message_tab

    do JavaScript "document.forms[0].submit();" in message_tab

    return body_value
end tell

I pasted the above code into VIM and ran it with the command line osascript command. Worked like a champ.

And because sleep is for the weak, I decided to track down how to do the equivalent in Python. Mac OS X 10.5 provides a “Scripting Bridge” for Python and Ruby (and potentially others), which causes many frameworks and other objects to be dynamically exposed. Without the need (for better or worse) of yet-another-virtual-machine. Anyways, I cobbled the following together:

from Foundation import *
from ScriptingBridge import *
safari = SBApplication.applicationWithBundleIdentifier_('com.apple.Safari')

def find_window_named(name):
    for win in safari.windows():
        if win.name() == name:
            return win

window = find_window_named("Web site > New message")
message_tab = window.currentTab()

print safari.doJavaScript_in_("$('post_body').value", message_tab)
safari.doJavaScript_in_("document.forms[0].submit()", message_tab)

There may be a better way to do the find_window_named method, but I didn’t have the time to track it down. As it was, I was able to do do the above by playing around with everybody’s favorite Python tool, dir(), which verified my suspicion that many of the commands exposed to AppleScript were also available via the Scripting Bridge. This is evidenced by the currentTab() method of a Safari window, analogous to the current tab of window ... AppleScript. And I imagine most of these are just Objective C methods. And since AppleScript editor’s Dictionary browser told me about the do Javascript [v] in tab [t] command, it stood to reason that it would exist on the Safari object. It was there when I did pprint(dir(safari)), and I knew that I’d need to pass in a Tab object.

In any case, it’s awesome that Apple has embraced Python and Ruby and has tied them in to the Cocoa runtime. Historical note: the first Python - Objective C bindings that I know of where commissioned by a NeXT Developer who wanted to use Python and Bobo (zope.publisher) to do web work with NeXT’s Enterprise Objects Framework, without the weight and cost of WebObjects. I think that means that Python was bridged into the Objective C runtime and NeXTStep frameworks before Jython ever got going. I believe that work was done by the developer who later released Objective Everything which bridged into Perl and TCL as well as Python.

Of course, traditional MacPython from the classic Mac OS was also natively tied in to the AppleScript of that era; AppleScript has always supported other dialects (FrontierScript was a common one).

But it’s nice now to see support coming out of both Apple and Microsoft (and Sun too, I guess) for these languages. The above scripting of Safari was surprisingly easy. As was an earlier experiment to fish around my calendar store for incomplete To-Do items. Quite nice.

But what’s especially nice is that I was able to SSH into my office Mac and tell Safari to submit that form that I had neglected earlier.

16.8.07. Numbers

I don’t know when I last used a spreadsheet for its actual spreadsheet capabilities, on a sheet I designed myself. I think it may go back to AppleWorks (on the Apple II)! Sure, I’ve used sheets like time cards and travel requests that others had made where I just had to fill in the holes. And I’ve received more than my fair share of spreadsheets used like an outliner / lightweight database / structured note list. But I don’t remember how long it’s been since I used a spreadsheet to figure out a budget, to track expenses, or any other dumb mundane thing like that. Until last night.

I was getting ready to pay my mid-month bills, and I was trying to figure out how much I could pay towards one of my credit cards and still have enough cash to cover the expenses remaining in the month. I also realized that I’ve been spending quite a bit at the iTunes Music Store and hadn’t been tracking any of it. I decided that this would be an excellent time to try out Apple’s new spreadsheet application, Numbers. I found a downloadable time trial of Apple’s iWork ‘08 suite, and immediately got to work.

Numbers is pretty damn cool. I don’t know if there are other spreadsheets that behave like this, but in modern times, it seems so obvious: instead of having the big set of cells in one large table, you work in small floating spreadsheets / tables. This is a big deal for so many reasons, with the most obvious being layout. Another great reason is that each table/spreadsheet can be more focused on its job. Already, Numbers felt a lot more intuitive than anything I had used in a long time.

When doing my simple rest-of-the-month budget, my main question was “how much can I pay on this card and still have enough cash on hand for the rest of the month?” Numbers made it easy with its slider option. For just this one cell, I was able to quickly configure it to give me a slider with a range of -700 to -500. When I got the rest of the budget entered, I could then play with the slider and watch its impact on the total-leftover cell. In previous months, I’ve generally done this calculation in my head, or compared where I stood the prior month after paying this particular bill. It was much nicer to whip up a simple spreadsheet where I could make this one particular number interactive and see the results immediately.

So I was able to get a couple of simple but nice looking spreadsheets together quickly that gave me actual data. I could easily play with this data, or just be embarrassed by it (I have spent quite a bit on the iTunes Music Store).

There are still a lot of old-style spreadsheet rules in play, at least in formulas and the like. That’s made a bit easier by being able to use header names (ie, =SUM(Total) or =MINA(Date Purchased)). I think it was Lotus’ Improv, which first appeared on NeXTStep, that worked this way. In fact, I think with Improv, it was the only way you could work: there were no A/B/C/D columns or rows. This was part of a cool feature of Improv wherein you could drag and drop header representations and regroup the data visually without impact on the calculations. I still think that was one of the most forward-thinking spreadsheet applications. But, it’s gone. I believe there’s some open source variation on the idea, possibly written just for GNUStep…?

Still, Numbers is pretty decent. I love the free-floating tables. It does make it much easier to compose complex spreadsheet pages out of multiple tables and data types. It’s pretty easy to refer to other tables as well. And it’s nice to have non-tabular data (text, graphics, etc) floating free from those numbers, making it easier to adjust layouts without impacting cells.

I’m impressed enough that I’m quite likely to buy iWork ‘08, just for Numbers alone. I have a small need for Pages and almost no need for Keynote, but I do find myself needing to get on top of my finances and similar data. Numbers is the first tool I’ve encountered that I think will let me handle my odd needs without requiring a degree or summer course in spreadsheets.