<?xml version="1.0" encoding="UTF-8"?>
<essay xml:lang="en" version="pto" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:gal="http://norman.walsh.name/rdf/gallery#">
<info>
    
    
    
    
    
    
    
    
    
<title>Me and my Sidekick</title><biblioid class="uri">http://norman.walsh.name/2005/01/11/sidekick</biblioid>
<volumenum>8</volumenum>
<issuenum>5</issuenum>
<pubdate>2005-01-11T07:48:28-05:00</pubdate>
<date>$Date: 2005-09-11 10:27:02 -0400 (Sun, 11 Sep 2005) $</date>
<author>
      <personname>
<firstname>Norman</firstname>
	<surname>Walsh</surname>
</personname>
    </author>
<copyright>
      <year>2004</year>
      <holder>Norman Walsh</holder>
    </copyright>
<abstract>
<para>Is it time for convergence? Can I really replace my Palm Pilot
with the Sidekick combination phone/PDA? Maybe.</para>
</abstract>
<dc:subject rdf:resource="http://norman.walsh.name/knows/taxonomy#Sidekick"/>
</info>

<para xml:id="p1"><productname>Sidekick II</productname> is
<link xlink:href="http://www.tmobile.com/">T-Mobile</link>’s brand name for
their version of
<link xlink:href="http://www.danger.com/">Danger</link>’s
<productname>Hiptop<superscript>2</superscript></productname>
combination phone, PDA, voice/data device. <personname>
<firstname>Deb</firstname>
      <surname role="suppress">Walsh</surname>
</personname>’s mobile contract expired in December, so I have an
earlier than expected opportunity to take one for a test drive.</para>

<para xml:id="p2">The device is really marvelous. It's just a fraction larger
than my current Nokia 3650 and a little bigger than my Palm Tungsten T,
which it will replace:</para>

<gal:image rdf:resource="images/20050111-133245"/>

<para xml:id="p3">Its clever swivel design exposes a quite reasonable
keyboard:</para>

<gal:image rdf:resource="images/20050111-134933"/>

<para xml:id="p4">It's not big enough for touch typing, but it's a useable “thumb
board”.</para>

<para xml:id="p5">What really sets this device apart is its integration with the
web. With the Sidekick, you don't “start GPRS” or “open a connection”
when you want to use the web, it's <emphasis>always</emphasis>
connected. For a reasonable flat rate (currently $20/mo), you get
unlimited data usage so there's no reason not to always be connected.
Combine that with a pretty reasonable web browser that understands
most HTML and a lot of CSS (but no JavaScript, alas), a couple of
instant messaging clients
(<systemitem class="username">ndwmob</systemitem> on
<systemitem class="service">AIM</systemitem> or
<systemitem class="service">Yahoo IM</systemitem>),
and even a useable mail tool
(<literal>ndw+pager</literal>
at <systemitem class="domainname">nwalsh.com</systemitem>), and you've
got a useful internet device that fits in your pocket. The SSH2 client
is an added bonus (yes, that's <command>emacs</command> running in a
terminal window up there, what else?) This is
<link xlink:href="/2004/11/02/mobility">what I want</link> from a mobile device.
</para>

<para xml:id="p6">The ergonomics and user interface are really first rate. It makes
other attempts to do data on a PDA-sized device seem pretty clunky.
And all of the data is constantly synced with servers at T-Mobile, so there's
an always-accurate web interface to your data. These servers also provide
an XML-RPC interface that allows you to download the contents of your
device. (A big “thank you” to <personname>
      <firstname>Dan</firstname>
<surname>Connolly</surname>
    </personname> for helping me get things working.
He's been the trail blazer here.)
</para>

<para xml:id="p7">All this for less than half the price of a
<productname>Treo 650</productname>, its only obvious competitor.</para>

<para xml:id="p8">But it's far from perfect. In fact, it's a testament to just how
good the device <emphasis>really is</emphasis> that I'm still
considering it despite a laundry list of flaws ranging from the
worrisome to the inconvenient:</para>

<para xml:id="p9"><emphasis>It isn't really my device.</emphasis> My Palm device
is clearly my piece of hardware, my data is stored on it in my local
storage, and what I do with it is my business. With the Sidekick,
things are much less clear. The data is really on T-Mobile's servers,
though it's cached locally, and there's no easy mechanism to develop
or distribute third party applications for it. T-Mobile's clearly got
a very closed view of who can do what with it.</para>

<para xml:id="p10"><emphasis>No local syncing.</emphasis> There's a USB port,
and apparently developers can use that to send data and applications
to the device, but it's not something that's supported for regular users.
And it's not clear to me how many hurdles I'll have to jump through
if I want to become a developer.</para>

<para xml:id="p11">Those issues are hard and partly philosophical, the rest
I think are simply limitations and bugs in the device.</para>

<para xml:id="p12"><emphasis>No timezone support.</emphasis> I'm used to using the
fabulous <application>DateBk5</application> calendar on my Palm. It
has robust timezone support, allowing me to enter events in a specific
timezone and always keeps them correct in my local timezone. No such
luck on the Sidekick: all events are in “local” time. And, alas,
changing the timezone on the device doesn't change what “local” time
means. This is going to be inconvenient when I'm on the road.</para>

<para xml:id="p13"><emphasis>Absurd field length limitations.</emphasis> Only 255
characters for a note field? Only 30 for the name of a company? What
sort of brain damaged stupidity is this? It's going to make using
the Sidekick as my “information appliance” a bit more difficult.
On the other hand, with constant connectivity, moving some data off
the device and onto the web will be more reasonable.</para>

<para xml:id="p14"><emphasis>Only 10 categories and labels.</emphasis> You can
specify categories for contacts, but only 10. And you can specify labels
for phone numbers, email addresses, and web pages, but only 10.
This'd be that brain damaged stupidity thing again.</para>

<para xml:id="p15"><emphasis>Phone number mangling.</emphasis> The device thinks it
knows what phone numbers are. Fair enough, I guess, since it's a telephone.
But mangling the numbers I put in (changing punctuation, removing spaces,
shifting letters to uppercase) is a little annoying.</para>

<para xml:id="p16"><emphasis>No notes on phone numbers.</emphasis> So, per the previous
point, I can no longer have “+1.555.123.4567 (Gold)” as a phone number
(it becomes “+1-555-123-4567GOLD” and I bet the device dials the 4653 part
too).
But there's also no where for me to put a note on this phone number to
indicate that it's for the Gold desk. I could use a special label,
except they only give me 10, per the point before the previous.
I'll probably just live with the mangled number and the hope that dialing
extra random digits never confuses anyone.</para>

<para xml:id="p17"><emphasis>US-centric addresses.</emphasis> You can have multiple
addresses per contact, that's nice, but they're all US addresses.
Anything you put in the “state” field gets shifted to upper-case, for
example. Brain damaged stupidity again.</para>

<para xml:id="p18"><emphasis>No bluetooth.</emphasis> Oh, well, maybe in the next model.
Until then, I can live with a wired headset for as often as I'm likely
to use the device as a phone.</para>

<para xml:id="p19"><emphasis>The calculator sucks.</emphasis> I mean, it
<emphasis>really</emphasis> sucks.
It sucks more than even a regular non-RPN calculator.
If I write any apps for this thing, the first one is going to be an
RPN calculator.</para>

<para xml:id="p20">I have about another week to decide if I'm going to keep it. So
far it's looking pretty positive, bugs and limitations not withstanding.</para>

</essay>

