Droooooooid – Part Deux

Many, many, many hours of work has been done since this post was posted.

The results are mostly good.  As it stands now, I’ve basically got all of the core functionality I had on the Touch Pro – plus more, obviously.  And a nice consequence of this work is that much of the processes I’ve used in the past are now somewhat simplified.

In particular, I’m quite stoked about the uber-quick WebDAV access and client-less access to the intranet.  That last one needs some security work, but it’s there and it’s a beaut.  I’m yet to test streaming from the Home Audio streaming zones, but that’ll likely happen in 1 hour or less (once I go out for lunch).

I also made some useability improvements to the fileserv, which is what allows me to send links and files to the phone.  Google has a Firefox and Chrome extension that allows you to do this, but I prefer to roll my own solutions.  Additionally, this one doesn’t require any special software that somebody isn’t likely to already have.

Truthfully the fileserv stuff has had a “todo – enhanced security” line item for some time now.  That’s not resolved yet, but I imagine I’ll be using this facility more going forward and that alone may prompt me to get all this security stuff nailed down.

So what’s not working?

Mail isn’t 100%.  I worked with the developer of my server software to iron out one bug, and that was great, but as it stands now the native Android Mail client is missing some core functionality (ability to set trash/sent folders is the biggest, and the ability to filter IMAP folders) so I’m using the k9mail client instead.  Unforunately that client isn’t doing two-phase deletions/moves properly.  So for now I’ve got to use both clients.  A bummer for now, but hopefully it will get resolved soon.

What’s changed?

My particular brand of push notifications have changed.  You may or may not know that certain events (types of mail, surveillance) generate notifications on the phone.  In the WinMo world these notifications were delivered via SMS. Some would automagically (courtesy of PushEffect) tell Outlook Mobile to connect and sync my mail.  That last little bit simulated push email, and while I have no such facility now (but may again play with IMAP IDLE) it’s sort of a moot point now; both Mail and k9mail are so fast to sync folders that I now do the process manually, which is really no more effort than opening Outlook Mobile to read the mail I just got notified about.  I could probably spend some time in the future to replicate the sync functionality on Android, to operate in the same manner it did in WinMo.  Chances are that that won’t happen any time soon though.

So anyway, the notifications were delivered by SMS, by way of an Email-to-Text gateway supplied by my mobile carrier.  And they being the gougers they are, they decided that I had to pay for the privilege of getting these missives directly instead of having their own servers cache them and send me stupid “you have mail, reply R to read” SMS messages in their stead.  That always bothered me, and while I took some baby steps in the past month or so to get around that in Windows Mobile, I now utilize a GMail account in Android to get around it completely.

Both methods offer quick delivery of said notifications.  The GMail method has no length restrictions, which is good, while the SMS method had no data usage, which was good.  But with 6GB of data allotment each month, data usage isn’t really a concern.  What is a concern is roaming data.  With data-based notifications I simply won’t get any notifications at all if data is off due to roaming.  So I’ve got to think about this one.

Nevertheless, being able to get of the monthly charge is a  Good Thing(tm).  Worst case?  I switch back to SMS-based notifications while out of the country, and use a little hack to deliver the essence of the message without the direct-email-to-text feature.

So that’s that for now.  I feel that a Part 3 will be coming soon.  Stay tuned.

Droooooooid!

Okay, so I’m not rocking a Moto Droid, but I am now rocking an HTC Desire Z.  The wifey helped to make this happen so thanks go out to her.

It’s currently 2:47AM so this will be short to begin with; I’ll have to come back later to flesh out this post a little more.

First impressions:

  • I will not be rocking CM6.1 or CM7 (?) on this device.  As it turns out, HTC Sense is cooler than I thought, and it’s a more polished experience than standard Android.  Yes, I realize that this places me at the mercy of HTC/Bell to feed any potential update craving that may arise in the future, but for now I’m willing to live with that
  • The screen is beautfil.  Nuff said.
  • Hinge isn’t the snappiest but I can definitely live with it.
  • It’s really nice to have a phone that actually hangs up when I tell it to (and not a few seconds later – Touch Pro, here’s looking at you kid)
  • It’s a little weird going into so many apps and just… leaving them to go elsewhere.  I could do this with the Touch Pro as well, but given the speed of that device it wasn’t often that I’d go into 6-7 apps in one sitting.  Perhaps it’s the new-car-small of the Z that’s got me bouncing around in apps (particularly as I’m still trying to get the thing setup to my liking).  However, I will say that some apps do seem to restart when you go back to them, and that’s definitely weird coming from WinMo, which would leave apps open until memory constraints forced them closed.  I don’t think I’ve hit any memory issues on the Z yet, so it may just be that Android is a little more aggressive in the task management department.
  • Battery life isn’t as good as the Touch Pro.  Again I’ll say that I’m using the device extensively in order to get it setup, and I have a feeling that two mail apps were trying to IMAP IDLE on my mail account – a consequence of not having my mail setup correctly yet.
  • I never thought I’d say this, but I like that I can link my local contacts to my Facebook contacts.  Having this integration – provided by HTC Sense – is nice, although I’m still adamant that I wouldn’t go so far as Windows Phone 7’s penchant for throwing Facebook photos into your local photo gallery.
  • L-O-V-E the way that the notification bar works.  Very cool to finally be able to see what a notification is  about without having to make any overt gestures or load the relevant app.
  • Maps on Android is AWESOME.  Especially Maps 5.0.  Check it out if you’re rocking an Android phone.

I’m sure there’s more, and they’ll come when I follow-up on this post.  It may be possible that many of these enhancements could be had on the WinMo platform, particularly considering that HTC Sense is available (indeed, was conceived) on Windows Mobile.  Still, the speed of my Touch Pro can’t compare with the Z, not to mention the screen resolution, vibrancy and size.  I will say that for now I prefer the layout of the hardware keyboard on the Touch Pro, but that could be a case of a year’s worth of familiarity with said keyboard.

One negative I noticed today – and I hope that this is was an isolated occurence – was trouble staying connected to the Bluetooth kit in the car.  I had problems like that on WinMo, where Bluetooth on the phone would actually turn off.  My solution was to write a native program and some Mortscript to force Bluetooth on whenever it inexplicably turned off.  Well, it seems that the Z’s Bluetooth is staying on, but the connection is dropping.  Will investigate more later.

Off to bed now.

Tablets – ready for (my) primetime? [updated 01/27/12]

I’ve heard a yearning for a tablet for a long time.  I made a (misguided) foray into the world of pen computers, scoring a used device on eBay some number of years ago.  Suffice it to say that that particular puppy hasn’t seen the light of day in some time.

The iPad is now all the rage.  And while I understand the allure of the device, and the particular niche it fulfills, the more I look at the iPad for my intended purpose the more I’m realizing that there are way too many shortcomings to even consider dropping $600+ on the thing.  And unfortunately, the same goes for the Samsung Galaxy Tab, the current champ in the non-Apple tablet world.

Here’s the thing.  I’m not looking for a device to carry around with me.  That’s what a smartphone is for.  Which isn’t to say that I wouldn’t want to travel with the tablet; rather, it would tend to “live” mostly at home.  So I’m not particularly adverse to the 10″ form factor; weight may be an issue, but if we’re talking solely about “portability” then there’s nothing wrong with 10″.

Now, I decided a long time ago that every portable device deserves a wireless connection.  I didn’t spend long with my Compaq iPAQ 3630 before an expansion sleeve and PCMCIA WiFi card were ordered.  Fortunately, any modern computing device worth its silicon has a myriad of wireless connectivity options – one of which is “3G”.  The carriers love to push this, as more 3G-toting users means more revenue.  But again, given that my intended use for a tablet is for home use, I’m pretty sure I can get by with WiFi – and tether to my smartphone whenever truly mobile connectivity is needed.

So what of these shortcomings?  I’m getting to that.  And in order to get to that, I have to talk about the fact that these devices are actually quite capable little devices.  The Tab, in particular, feels very powerful to me.  It screams “computer” much more than the iPad, and that’s not a bad thing.  It does its job so well, in fact, that I’m chomping at the bit to cram an Android smartphone into a pant pocket.  As a mobile platform, I must say that Android is getting it done quite nicely.

The iPad, on the other hand, still comes off as a large toy.  I just can’t shake the feeling.  Sure, you can run cool apps, but I’m not looking to run cool apps at home.  My home needs for a tablet are quite modest – surf the web, control my home automation systems, check email.  It really doesn’t have to get more complex than that.

And in that vein, the Tab also falls short.  Every time I pick up a Tab I feel like I should be putting it in my pocket and carrying it around with me for the entire day.  This is not a feeling I want to get from a device that’s supposed to live on the living room table.  I think that Samsung is intending the tab to be a mobile, portable device – but that’s not the niche that I want it to fill.

Then there are more tangible shortcomings – like the complete and utter lack of multi-user support.  Some of the coolest things you can do with the iPad and Tab come from using the native apps, which are the most pure reflections of what the manufacturer intended you to use the device for.  And some apps, like email, are very personal in nature – do I want some house guest to pick up my tablet and start reading my email?

And so… I’m conflicted.  On a few fronts.  I don’t like Apple’s walled garden, but I think I do like the 10″ form factor.  I like Android’s utility, but I don’t want/need my tablet to be that powerful.  So what am I saying, really?

One, is that none of the tablets on the market now are going to get the job done for me.  I mean, I’d take either one if I won it (though I’d probably sell the iPad), but there’s no way I’m paying $600+.

Two, is that I know what I need:

  • multi-touch interface
  • capacitive touchscreen
  • tabbed browser with Flash support

I think I’d like a capable built-in media player, but I do not want to store media on the device.  Not even pictures.  Any media should be streamed over the network  – perhaps using UPnP or DLNA.  And while I’m not adverse to accessing a marketplace and running other native/3rd-party apps, I think that this capability must go hand-in-hand with the some sort of fast-user-switching ala Windows XP Home.

Until these criteria are met, I may find myself sitting on the sidelines of the tablet game.

[update 2011/08/30]

Interesting article from Engadget, questioning the tablet’s position as a productivity device and the real necessity for a “third device”.  At this point I really wish I had scored a $99 TouchPad – not quite “taking one if I won it” that I mentioned above, but close enough.  Oh well, so it goes.  I figured I could move run an Android port on it as soon as that technical feat was accomplished.  Surely it wouldn’t be long, right?  But something strange happened when I played with a TouchPad in-store for 30 minutes or so, followed by a couple of Honeycomb tablets – I was far more impressed with WebOS than Honeycomb.  In fact, Honeycomb felt like the cross between a media device and a mobile computer that I alluded to earlier in this post, to the point that the promised functionality belied the limitations of the device (reported so well in that Engadget article).  I suppose that experience reaffirmed an earlier tweet I had made that WebOS on a tablet would be killer.  It’s unfortunate that software support will be lacking though; I did note some issues with the native web browser, and it’s very questionable how timely updates would come out (if at all) to address such issues.  If a port of Honeycomb or even Gingerbread ever surfaced for TouchPad, then certainly updates would be frequent – but again, Honeycomb felt like an entirely different beast, with WebOS wearing the tablet pants much better than Honeycomb.

So it seems that not much has changed.  My requirements still remain the same – multitouch with tabbed browsing and Flash support.  If anything, I’m now more convinced of the things that I don’t want – ie, a tablet with a complex interface.  Keep It Simple Stupid.

Even the multi-user conundrum has a workable solution on WebOS.  Firstly, I imagine that the only player who will solve this problem outright is Microsoft with Windows 8.  And I already know that such a tablet will be insanely expensive and too powerful for the light duty I’d want it to perform.  Secondly, a tablet’s increased real-estate means that visiting webpages is a very practical alternative to running the dedicated app (think Facebook, Gmail, etc).  Thirdly, I’m not of the mind that – even at $99 – it makes sense for a household to have multiple tablets for the sole purpose of casual usage; quite simply, it’s an unnecessary indulgence and a real distraction.

So how is the conundrum solved?  Whether through fast-user switching (ala Windows) or actively logging in/out, the fact is that a multi-user system requires a user to reauthenticate and “unlock” the device.  Now, if you’re working on a tablet that’s little more than a casual media consumption device, I can imagine that it’s enough to do this un/lock dance on a per-“app” basis.  And the ability to login and logout is something that every website application presents as a matter of course, but no native tablet app presents as a matter of course.  Many people are probably used to doing so within their web browsers.  So right there, the “requirement” to run the web version of your “productivity” apps – and crucially, the ability to do so on a generously-sized screen – means that you don’t have to worry about somebody sticking their nose into your private data.

But here’s where WebOS shines.  If I’ve got a video open on the family tablet, or a series of webpages – neither of which are “private” – then somebody else can pick up the tablet, stack my open apps, and open their own apps and webpages.  And so you end up with a shared user space, where each user’s resources are sitting in their own stack.  When I want to use the tablet and restore the state of my “apps”, I stack all other apps and unstack mine.  And finally, since we’re talking about a simple tablet here, I can imagine that each stack would only be a handful of cards deep – ie, very manageable for both user and system.  I certainly wouldn’t have 10-15 apps open simultaneously like I tend to do on a desktop computer.

I’ll say it – it’s unfortunate that TouchPad went from overpriced at $500 to unsupported at $100.  A happy medium may very well have been $150-200.  Here’s to hoping that WebOs lives on and that somebody picks up the hardware mantle.  Certainly everybody has seen that there’s demand for a non-iPad tablet at a lower price point?  It doesn’t have to compete with iPad; rather it just needs to fill the niche that the $99 fire-sale flushed out.

[update 2012/01/27]

Well well well

That may change things.