My future is (apparently) here; HP TouchPad added to the stable [updated 02/25/12]

As the title says, my WiFi network is now playing host to a 16GB HP TouchPad. And maybe it’s just my tablet newbie-ness, but I’m not getting what all the fuss is about re: thickness.

Granted, my Fujitsu pen computer (whose location is now unknown…) is probably closing in on 1-inch of girth. But looking at the TouchPad, I’m convinced that a thinner device might still be comfortable to hold but I can’t imagine that it would be any more comfortable to hold.

Now I know that HP wrote off the TouchPad hardware for a number of reasons – not just an inability to compete with iPad on the thickness front – but personally I think that the “thin-is-in” mantra is just more good marketing being thrown our way.

Anyhow, on the software front I can say that webOS isn’t as smooth as Android, and most definitely can’t hold a candle to iOS. But if you read a previous article you’ll discover what I find most alluring about webOS, performance issues aside. I’m currently in the process of adding patches to make the interface that much more snappy, and the major project at present is to enable streaming of my network video and TV shows. DLNA (or uPnP) is the name of the game here, and it’s requiring a certain amount of synergy between client and server that I haven’t quite mastered yet.

But so far I’m relatively content. More later.

[update 2011/12/16]

So I’ve had the TouchPad running for almost two months now.  And like most people’s TouchPad experiences, the road hasn’t been entirely smooth.

It all started when I tried to do the initial setup of the TouchPad while tethered to my phone’s WiFi hotspot. The tablet kept complaining that it couldn’t reach the HP servers.  Not knowing if this was an HP issue or a carrier issue or what, I didn’t think much else of it.

I had the same problem using my main WiFi network at home, but again, I figured maybe the HP servers were overloaded.

Many attempts later, I finally completed the setup.  And my main problem was spotty WiFi performance.

I posted a thread over at forums.precentral.net (now webosnation.com) detailing the problem, so you can head over if you want the juicy details (and an idea of how many other TP users have comm. issues).  The Coles Notes version: I had no problem accessing my intranet resources over WiFi, but browsing the interwebs at-large was a hit-or-miss affair.

As a result I finally settled on setting up an Apache forward proxy instance, and considering that the TP tends to “live” at home, this solution has proven acceptable.

So what’s my almost-two-months impression of the tablet?

Truthfully it’s getting the intended job done.  I have to admit that there are some usability issues related to the browser (which, in general, I knew to have some issues before ever joining the webOS camp) – most notably, accessing Hotmail requires some patience. But for the most part it’s quite enjoyable, and having Flash makes things very nice indeed.  That I’ve had no issues with Flash videos running fullscreen up to 720p – added bonus.

So I tend to use the tablet mainly for browsing, and this may involve logging into my Google account via the browser and catching up on Google Reader news.  Or I may surf Engadget.  Or CNN.  Or whatever.  It works, and it works well.

I’ve also taken to setting up a Google account specifically for family use, and this account is in fact linked to the TouchPad.  Now, you may recall some concerns I had about a house guest being able to pick up the tablet and read personal information.  But I figured… the main point of this “family” Google account is to setup a synced calendar.  This is no more private or public to a house guest than the calendar hanging on the fridge that we (attempt) to use to track events of relevance to the family.  So the privacy concerns are somewhat moot.  Add in the ability for said Google calendar to sync across the TouchPad, my phone, and Shelly’s phone – automagically – and you have an appealing organizational tool.

Granted, Shelly has asked me more than once about these calendar entries I keep inserting into her calendar… but that’s beside the point 🙂

So for web browsing and family organization, the TouchPad is useful.  Whatever about media consumption then?

I talked previously about DLNA, and I’m happy to say that the combination of bHome and TouchPlayer and PS3 Media Server results in a (mostly) enjoyable experience of viewing network-stored videos on the TouchPad.  I say “mostly”, because sometimes it takes a few finger-taps in bHome for TouchPlayer to actually start playing the video, but usually it just works.  TouchPlayer has some kinks that need to be worked out – most notable a less-than stellar scrub feature – but the ability to play my MPEG2, Windows Media Video and DivX vids on the TouchPad without real-time transcoding?  Priceless 🙂

So am I pining for an ICS port on the TouchPad?  It would be nice to play with, but from what I’ve seen of ICS, it looks a lot like the Honeycomb experience that I already pooh-pooh’d on a tablet form-factor.  Sure, the apps must be fantastically wicked awesome, but I’m quite happy with the fact that I can pick up the TouchPad, get a specific task done, then put it down without feeling obliged to interact with apps just for the sake of interacting with apps.

The web is the OG “app” my friends.  You bettah ask somebody!

[update 2012/02/25]

Just wanted to say that I’m now rocking ICS on ye olde TouchPad. O still think that WebOS wipes the floor with Google’s offering, but I just can’t deny the: polished state of ICS vs. WebOS; the mountain of apps that is Google Market.

Yes yes yes… I know that I wrote previously stating that the web is a great alternative to mobile apps. But there are just some things that a website simply can’t do (at least on a tablet) – like connect to my servers using RDP.

I still think the card metaphor of WebOS is light-years ahead of what any other tablet OS has to offer (save perhaps Blackberry’s PlayBook OS, but we all know where that got its inspiration from…). But… WebOS is struggling for developer attention, Android isn’t. And it shows, both in the available app catalog as well as in the OS itself.

It’s a shame really 😦

Me <3 Opera Mobile

So I’ve been doing some work off-and-on on a mobile version of the site I use to browse/play music on my home network. I’ve wanted a mobile-optimized version of the site for some time, and a recent development with my SHOUTcast streaming client of choice has made this project more of a necessity than a curiosity.

Critical to the operation of the site is the ability to touch-scroll various regions in the page. That, and the ability of the browser to support HTML5 Audio in the MP3 format. And so far, I’ve only found Opera Mobile to be worthy of solving the HTML5 Audio part of the equation while also remaining my mobile browser of choice.

However, I was having no luck with the touch-scrolling part of the equation. Many mobile browsers seem to have a problem handling straight-up overflow:scroll, and even the iScroll Javascript library wasn’t solving my particular flavour of problem. And what was working was working at a horrible pace.

Then I happened to notice that a manual update for Opera Mobile was sitting in my Android Market queue. Among reported changes was an update to the core (or engine) that the Android version of the browser was using. And wouldn’t you know it – upgrading to this version solved all of my touch-scroll issues, and performance is about as snappy as it is on the desktop Opera Mobile emulator.

So colour me happy. Now that the site is functional, I can work on prettying it up and adding gee-whiz features 🙂

Me <3 jQuery

I’m one to scoff at development tools/libraries which purport to make my like easier. Call me a masochist, but something in my head associates “easy” with “anybody can do it”.

I’m also one to get predictions horribly wrong, and the camps that I choose to align with (most notably in the TV sci-fi genre…) have been been known to get beat down by a difference of opinion or a lack of general interest on the part of society at large.

So it was that I heard of Javascript libraries like Prototype and jQuery, but I never paid them any mind. Big mistake. Having seen the latter library mentioned on all sorts of career-development sites, I decided to take a closer look.  And the result, I’m glad to say, is that I’m quite impressed and very likely to rely heavily on jQuery in the future.

It’s not that jQuery lets me do things in Javascript that I couldn’t do otherwise. Rather, jQuery lets me take mountains of code that performs some function and replace it with one or two lines which perform the same function. It really amounts to a shorthand version of Javascript, such that you still have to know what you’re doing in JS before you can use the shorthand.

Admittedly jQuery also lets you do cool things like perform animations. But from somebody who has written my fair share of Javascript animation functions, take it from me when I say that making a simple jQuery call to animate an element is a welcome relief, particularly when you have to consider browser inconsistencies.

So that’s it then – I’m adding jQuery to my recent spate of new undertakings.