My Amazon Kindle arrived today — thanks Julie! — and I’m eagerly putting it through its paces for an upcoming Gadgeteer review. Earlier this year I reviewed the Sony Reader and I’m looking forward to comparing the two. (The Kindle is definitely in the lead so far.)
I don’t want to spoil my review too much by talking about the Kindle here yet, but I do have a few first impressions.
Amazon Whispernet (the Kindle’s wireless service) actually works at my home, and quite well at that. Considering that it’s supposed to be based on Sprint EVDO, this surprises me greatly. I suspect it’s roaming on Verizon, unless Sprint lit up a tower close by very recently. If it’s roaming, I have to give Amazon props for allowing that — it makes the Kindle much more useful for those of us who live a bit outside the city.
A hardware tidbit: check the system/logs directory of the Kindle’s internal storage. Mine had a boot log showing that it uses a Linux 2.6 kernel on a 400 MHz PXA255 with 64MB of RAM, and EVDO module from AnyData. The software seems to be Java based with a plugin architecture so they can add more applications later, like the ones under the “Experimental” menu. Maybe someone will figure out how to hack it for user-installed apps, though I don’t have any more hope for that than I do for it on the iPhone.
I’m also pleased by the fact that the Kindle has native support for unencrypted PalmDocs. Although the Kindle’s native format for DRMed books is something new, its format for unencrypted documents is MobiPocket, which is essentially HTML wrapped in a PalmDoc container. Plain text PalmDocs work just fine too. Just make sure the file name extension is .prc, not .pdb — just go ahead and rename it, as the file format is the same inside. Other than plain text, those are the only formats it supports directly right now, but at least Amazon offers a conversion service which is free via email, or 10 cents if you email it a document to be sent wirelessly to the Kindle. Or, on Windows, you can use Mobipocket’s own conversion tools. From where I sit, this is far easier than dealing with the Sony because all of my books are on my Mac, and many of them are already PalmDocs.
And yes, this probably means that Pyrite Publisher is about to rise from the grave. I think this incarnation will be a Kindle-supporting e-book librarian though…
Now that we know an iPhone SDK is coming, here are my predictions about it based on all of His Holiness’ statements about “security” and “protecting the network”:
Prediction One. No retail iPhone will run unsigned apps, ever, at all. There will be no possibility to install them by clicking through warning dialogs, as you can on Windows Mobile and Series 60.
Prediction Two. The only way to load apps onto a retail iPhone will be through iTunes (okay, that part’s a no-brainer), and the only way to get loadable apps into iTunes will be to buy them from the iTunes Store.
Prediction Three. To get an app signed and listed in the iTunes store, developers will be required to submit it for approval and certification. Not only Apple, but their carrier partners on a country-by-country basis will have veto power over which applications appear in the store.
Prediction Four. Apple will set the prices for iPhone apps. Either they will all be a flat rate, or more likely they will have several tiers of pricing. Which tier an app ends up in will depend on Apple, the carriers, and what kind of app it is; developers won’t be able to choose.
Prediction Five. Out of the price for iPhone apps, both Apple and the carrier will get a cut, the total of which will be larger than the fees typically charged by shareware registration services.
Prediction Six. The means used by developers to test their apps on real hardware may be hackable, but will not work for general app distribution. I wouldn’t be surprised to see a method that involves ADC membership with a signature that allows app updates to only work with a specific registered iPhone.
Prediction Seven. The SDK will not be free; it will either be sold separately at a price commensurate with other pro development tools, or (more likely) require a paid ADC membership.
Prediction Eight. If there is a way to develop iPhone apps that doesn’t have these restrictions, it will be based on Dashboard widgets, and widgets will be sandboxed at least as restrictively as Java applets in a browser.
So, I guess I’ll revisit this post in February and see how close I got…
My review of the HTC TyTn II is up at The Gadgeteer. In short, I like it. It’s a worthy upgrade from the original, with better performance, a solid feel, internal GPS, and many small improvements and fixes. It’s good enough to tide me over until Apple makes an iPhone I actually want, at least…
As I’ve mentioned in some of my previous posts (here and here for example) I’ve been looking for the perfect mobile device, and not finding one. At some point today UPS will be dropping off a fresh new HTC TyTn II. I already know it isn’t perfect, but it is a nice incremental upgrade to the TyTn I’ve been using since last fall.
The TyTn II upgrades the original model in a number of ways. It has a new CPU (still the same 400 MHz clock as before, but with a secondary core and acceleration for 3D and Java) and twice the internal memory, and runs Windows Mobile 6 out of the box. The screen now flips up to an angle for better viewing while you use the keyboard. The camera has been upgraded to 3 megapixels. And last but certainly not least, it has an internal GPS which works both on and off the mobile network.
I won’t say more about it here yet, because I’ll be reviewing it for The Gadgeteer — look for my review soon, perhaps next week. In the meantime, you can catch up by reading my Gadgeteer review of the TyTn from last year.
My review of the Sony Reader e-book device has been posted over at The Gadgeteer. In short, I like it but it still has room for improvement (doesn’t everything?) — for the rest you’ll have to read the full review.
As I mentioned a couple of days ago I have been playing with a Nokia 770 lately to see if it is a viable addition to my gear bag. What I didn’t mention before was the difficulty I have been having tethering my HTC TyTn to it through Bluetooth. It may seem silly to use a full featured PDA phone to tether anything smaller than a laptop, but since the TyTn has 3G and the 770 has a decent web browser, it seems like they might make a good pair for those times when Pocket Internet Explorer isn’t enough. It’s worth a try, at least.
The first problem I encountered is that I have Windows Mobile 6 on my TyTn, and that version of the OS no longer has dialup networking support. According to Microsoft’s infinite wisdom, we should all be using personal area networking for Bluetooth tethering. It works really well with the Mac’s built-in Bluetooth stack (and with Vista, I would think), but smaller devices like the Nokia tablets and TomTom GPSes haven’t quite caught up yet. One of the clever hackers at xda-developers put together a package to restore the missing DUN support, so I installed that.
That wasn’t enough, though, as the 770 insists that the TyTn has no usable services on it. It is supposed to support DUN, file transfer, and SIM access, and all of those are enabled on the TyTn, but the 770 still refuses to pair with it using the last official OS release (Internet OS 2006). The 2007 hacker edition of the OS (the N800’s OS backported to the 770) worked better. The phone pairing applet still didn’t work, but you could pair the TyTn using the generic Bluetooth control panel. I don’t want to run the hacker edition OS on my 770, though, as it tends to be slower and more crash-prone on the 770 hardware, and seems to be missing some core features like streaming audio playback. So I went back to the 2006 edition, and today I finally fixed the problem.
My solution isn’t exactly for the faint of heart, though, as it involves directly editing configuration files. Full details after the jump, if only so I can remember what the heck I did in case I ever have to re-flash my 770…
(Read more…)
Earlier, I wrote about my search for the perfect mobile device, and why it seems like there might not be one. But what about a two-device solution? Palm seems to be taking a stab at that idea with their upcoming Foleo, and I’m looking forward to trying that. In the meantime, I’ve been playing with the Nokia 770, another interpretation of the “second device” concept.
The Nokia 770 is the first of two Nokia “Internet Tablets”. Its successor, the N800, is essentially the same device, but with improved hardware. The 770 has recently been appearing at various online vendors for under $150, while the N800 retails for $399, so I thought it would be an ideal way to try out Nokia’s concept without spending too much cash.
The Nokia 770 (and the N800, which shares the same basic design) is a horizontal form factor device with a large touch screen and connectivity through WiFi and Bluetooth. It runs a heavily customized version of Linux and a web browser based on Opera. In addition to the browser the software includes an e-mail client, Jabber and Google Talk instant messaging, and a streaming media player. Notably, the 770 and N800 do not come with PIM software — Nokia is positioning these products purely as Internet tools, not as PDAs. Of course, since the 770s OS is based on Linux, there is a lot of add-on software already available for it, and a convenient package management interface for downloading and installing it automatically.
But how does the 770 work as a “second device”? Better than I expected, although it still isn’t very close to perfect. The browser is far better than most phone browsers I’ve tried, at least in how well it renders the web as it is meant to be seen. It even supports Flash, although the 770 isn’t really fast enough for that, so I ended up turning it off. The e-mail and instant messaging support is seamless and automatic, although the e-mail client leaves a lot to be desired. (It’s no worse than the stock messaging app in Windows Mobile, I suppose.)
For my needs, one of the biggest things holding the 770 back from perfection is its lack of a truly usable input method. The only methods built in are a typical on-screen tappable keyboard (with word completion) and a decidedly sub-par handwriting recognizer that requires you to write in a fixed size box at the bottom of the screen. I haven’t been able to get the handwriting recognition to work well yet, and I doubt I ever will. So for a device with easy to set up email and IM, I find it hard to believe I could actually use it for either. The TyTns thumb keyboard is much more efficient, and the TyTn also has the Block Recognizer (a.k.a. Graffiti with the serial number filed off) which works well for me as a long-time Palm user. The Nokia tablets will work with a Bluetooth keyboard, but that’s yet another thing to carry around, not to mention being useless unless I’m seated.
So, in the end, the Nokia Internet Tablet is closer to what I need, but not quite close enough. I’m carrying it in my gear bag anyway, because it is occasionally useful for its browser. I’m guessing that the crispness of the display will make it a good e-book reader too, although I already have one of those which has been a permanent part of my kit for a while. The search continues… perhaps with a Foleo, next.
With the release of the iPhone, I’ve been considering my options for mobile devices to try to figure out if any of them is ideal for me. The iPhone isn’t — I’ll talk more about that in a later post — and unfortunately it seems like nothing else either. This post, and probably others to follow, is as much for my own benefit as it is a way to publicly record my thoughts in the vain hope that someday, someone might make a device that works well for people like me.
Thanks to my work with Julie at The Gadgeteer and my own fetish for handhelds and PDAs, I have been able to try a number of different things. My current phone/PDA is a HTC TyTn which is arguably one of the best Windows Mobile phones available right now. I’ve used the Treo 650 and also have a Palm TX. I have a couple of Nokia N-Series phones, but unfortunately they’re tri-band so I’d have to switch away from AT&T if I wanted one of those for everyday use.
The options boil down to five smart device platforms:
- Windows Mobile Pocket PC
- Palm OS
- Symbian
- iPhone
- Blackberry
There is a sixth option, which is to use a separate device such as a PDA or ultra-portable PC which is tethered to a phone by Bluetooth when necessary. I’d prefer not to do that, since I already carry too much crap around with me.
Let’s start with the iPhone, because it’s on everyone’s mind right now. First of all I have to say that Apple did an amazing job on the iPhone design and user interface; nothing else I’ve tried comes close. But for me, it falls short in a few key areas.
One of the iPhone’s biggest drawbacks, from my perspective, is the lack of 3G support. Of course, opinions on this will vary based on network coverage. But here in Birmingham, AT&T’s 3G network is pretty solid throughout the city and more populated suburbs, while the EDGE network can get very congested and slow. Theoretically, EDGE can do over 200 kbps; in practice, around here, it’s more like 20 kbps most of the time. For a device where one of the major features is browsing the real web, this really hurts.
The lack of add-on applications is also a big disadvantage of the iPhone, as far as I am concerned. I understand that there are reasons why Apple made that decision for the launch, and I hope that it will change in the coming months, perhaps with the release of Leopard and its development tools. The problem right now is that while the iPhone is very good at what it does do, it doesn’t do enough on its own yet. Web applications are not an acceptable substitute, because inasmuch as EDGE is slow, so are they.
And yes, I do want to do more with the iPhone than it does out of the box. I’d like SSH for server maintenance — one less thing I would need a laptop and a WiFi connection for. VNC would be nice too, or better yet, proper Windows and Apple remote desktop support. I need a text editor or word processor, so that I can whip out a folding Bluetooth keyboard and write. I’d love an e-book reader, so that I don’t need to carry a separate one if I’m going to be waiting around somewhere. Instant messaging is a must, preferably with multiple networks but I’d be happy enough with a mobile version of iChat. Streaming audio and video would be cool too, since the iPhone is also an iPod.
On the “pro” side of the ledger, the iPhone has excellent support for Mac syncing and a great web browser, both of which can be troublesome on other platforms. These may be what make me choose an iPhone in the end, although I doubt that will happen until after Leopard is released (which seems the obvious time to announce an iPhone SDK).
Next time, I’ll talk about my current platform, Windows Mobile. And by “talk”, I probably mean “complain”…
Recent Comments