Showing posts with label technology. Show all posts
Showing posts with label technology. Show all posts

Friday, 11 March 2011

How (not) to manage a trial version of software

There are essentially five models to selling software over the internet:
  1. Don't, it's free
  2. Allow download only after purchase
  3. Give away a limited free trial
  4. Give away an "ad-supported" version that uses up your bandwidth and screen real-estate and, sometimes, time, by displaying ads but is otherwise fully functional.
  5. The "freemium" model: A limited free version missing functions that are activated after payment, but which is otherwise fully functional and time-unlimited.
Having a limited trial can take one of several models. One of the world's best twitter clients, Gravity, has a 10-day trial during which absolutely everything works, then it refuses to work at all until you activate it. You don't have to reinstall anything, it just checks on start-up if it's registered or not and stops working until you register your phone during check-out after payment.

For networked applications like the Twitter (and Facebook and FourSquare and ReadItLater and Google Reader and Flickr) client Gravity that's not a problem, but unfortunately some applications that don't otherwise need networking at all will be ad-supported or go away and talk to their home server anyway, which is a nuisance and potentially expensive.

Another popular model is to allow the software to run indefinitely, but not to save anything. I've seen this model used in 3D modelers that can load or edit anything, but can't save any changes.

Or, sometimes, the "limit" is that starting up takes longer and gives you an annoying note, every time, that this wouldn't be happening if you manned up and shelled out for the licence fee.

All of these are, I have no doubt, legitimate. The freemium model is gambling on enough people wanting the extra features, the time-limited feature-full trial offers potential buyers a vital chance to make a complete evaluation, and the pop-up warning and ad-supported models pit the non-buyer's patience against their frugality.

The feature-limited trial can be highly annoying and limit your ability to truly evaluate the functionality, but hey, it's an option.

The only model I really don't like is the "buy it or nothing" option, where you have to take it on faith you will like it and even be able to get along with it.

However, there are a right way and a wrong way to approach each of these models.

The first right way is to put comprehensive and clear screenshots on your web site, regardless of what you're doing with the software. The second right way is to clearly announce what you are doing.

I have just found a piece of software that violates that second principle, and almost as a matter of principle I won't be buying. 

It's not from a company and there are better ways to provide feedback, so I'm not going to name and shame here.

I'll just make it really obvious and say I was looking for a small application to track expenses on my N900. 

I found three - one free, one freemium and ... another one.

Its website has a huge list of features, mentions it's cross-platform, has screenshots and a video, and it's only when you get to the Download page that you are told, in fairly poor English, that it is fully functional except it won't save data between sessions until you enter a registration key you can get after donating via PayPal.

No price, just making a donation at all.

Now, that right there annoys me just a little. Either decide what it's worth, or ask for donations but don't require them, or just give it away. What, you want the processing fees on a 1c donation? That's what I'm tempted to do, here.

What's worse, however, is that the application is available in the repositories for the N900, so it's possible to find it and install it via the on-device application manager before finding out this limitation. In fact, it's possible to install it, run it, enter lots of data, close it down and then, next time you start it up, find all your data missing, think it's horribly buggy and abandon it in disgust.

The first version I installed was from the extras-testing software repository and it was not, to put it mildly, too advanced. I then updated the entire device (I love a system that lets you do that. As opposed to Nokia's other smartphone OS, that doesn't) and got a new version, with extra features, from extras-devel which, explicitly, is not expected to be safe for regular usage because it's cutting-edge.

So the version that looks complete and usable isn't available to sensible people.

I also noticed a brief notification saying I hadn't registered it, and another one saying it wouldn't work fully until I did. 

First of all, I don't remember that second, fairly important, notification from the earlier one, which had the same limitation. Secondly, those notifications fade and disappear fairly quickly. So if you're not looking at the screen, you don't notice it.

It's really, really poorly done.

I shall keep my opinion of the icons to myself.

If you are looking for an expenses tracker for Maemo 5 on the N900, I recommend Toshl. It's freemium, cleanly and attractively designed, easy to use and to comprehend and has full backup onto the web site, where the premium version gives you extra features. It's also available on all the major platforms except WebOS and Windows Phone, although there is a non-functioning button for that so it'll probably be soon.

Friday, 24 December 2010

Smartphone, n.: A device with not quite the lot

Picture this: you're shopping for a new luxury car, and the salesman is explaining that the seat can be adjusted in seven different ways via the one control and it can save settings for seven different people, and the steering wheel can control the radio, gears, cruise control and climate control, and it can steer itself between the lines and control distance to the car in front via radar, and...

Then you notice that it doesn't have an interior rear-view mirror and the wing mirrors are adjusted manually. The salesman looks baffled and says "It's got mirrors, doesn't it?"

That's how I feel we're being treated by smartphone manufacturers.

Item: HTC still hasn't worked out how to build a decent loudspeaker or camera.

Item: Nexus S, built by Samsung to be Google's next developer phone, doesn't have a memory card slot.

Item: my current shiny, with which I am still mostly very happy, the Nokia N900, doesn't have a now-and-even-when-it-was-new standard magnetometer to go with its not having MMS inbuilt and the version of Ovi Maps installed not having any facility for storing bookmarks.

Seriously, what are the thought processes going on in their heads?

With the iPhone, you knew you weren't going to get a feature until Apple was good and ready to give it to you, and that's a perfectly fair and reasonable decision.

With Windows Phone 7, they appear to have deliberately decided to cripple it by denying it memory cards or cut and paste and, well, at least they're being consistent.

But nobody else has that explanation. Even when you get the hardware it may not be activated - the N900 has FM transmitters and receivers, but there was no radio software in early firmwares to use the receiver.

Then there's Samsung, who produced one of the best mobile phone cameras in the i8910 but haven't put anything remotely as worthy in any Android phone.

Then you have screens. Motorola came out with the XT720, which had all the potential to be a great tablet phone, with good speaker and even good camera. And a screen so mirror-finish you can't use it outdoors in sunlight.

Even Nokia have been guilty of this, perversely removing the sunlight-friendly transflective layer from the N97 mini.

There appears to be a "95 per cent" attitude in the technology world at the moment. Apple gives you 95 per cent of the features you want, but does them really well. Everyone else tries to give you all the features, but only gets it 95 per cent correct.

Only one company seems to have the commitment and meticulous dedication to engineering perfection that even justifies a label like "flagship" and they're such control freaks I couldn't justify giving them money even if I could justify their prices.

And yes, I'm aware of the irony.

It's been a truism for a while now that Nokia doesn't release new phones when they're finished - you need to wait for a couple of firmware releases for that.

At the same time, the hardware set of top Android phones is the reason I've bought two more Nokias in a row. Samsung and Motorola are getting very close to convincing me, but Motorola have done stupid, unfriendly things with locked bootloaders - preventing custom firmwares while not committing to prompt and guaranteed updates themselves - and Samsung goes and does something like the Nexus S with no card slot and an average camera.

What I want is an N900, next generation, all updated and upgraded hardware, maybe the N8 camera (we can dream), still the keyboard, and Maemo 6, not MeeGo. And now that's doomed forever. Do I think the first MeeGo device will be worthy, and complete?

Don't make me laugh bitterly.

Saturday, 18 December 2010

Queensland solar power: covered in coal soot

I stared at this story for a while, wondering what my response would be.

Then the Government published a media release as well, and I decided to go with: Pathetic, foot-dragging pack of short-sighted hypocrites.

The story is:

Under the definite headline Queensland to host one of the world's largest solar power stations, says Stephen Robertson, the Courier Mail reported conditionally on December 15 that:

Queensland could become home to one of the world's largest solar power stations, Energy Minister Stephen Robertson says.

This tendency to make unjustified, definitive claims in headlines (ie, "lying") is one of my biggest complaints against editorial practices in poor-quality journalism. Bald statements tend to get remembered, and headlines tend to get remembered, so the end result is the perpetuation of inaccurate perceptions. This, particularly in science journalism where a nuanced discussion of uncertainty is paramount, is unnecessary, destructive to an informed public and unforgivable.

But I digress.

The fact is that for a state blessed with wide open spaces and lots of sunlight (anyone not associate Queensland with sunlight? No? Didn't think so), Queensland has been as backwards as the state's reputation, and needs to stop being proud of plans that will barely even catch us up to where we should be.

This is a state addicted to burning things. Electricity generation is built on a platform of coal, and more coal. Even "renewables" production depends heavily on burning things. According to a 2009 report to the Australian Bureau of Agriculture and Resource Economics (ABARE), in 2007 bagasse (sugar cane mulch after the sugar is extracted)  provided a third of all electricity produced in Queensland from renewable means. Surprisingly, hydroelectricity was most of the rest. Biogass and wood pulp contributed and there was a frankly surprising contribution from wind. Solar, including solar hot water heating, barely even registered.

To be clear: Even if you don't accept global warming, a heavy reliance on a finite resource has never been intelligent. Any manager with half a brain plans for things like expansion and increase, and any geologist, geometrician or anybody capable of acknowledging the spherical nature of the earth can tell you that no fossil fuel is available in unlimited supply.

If you do accept global warming, something it's becoming harder and harder for even the obstinately ignorant to avoid, burning agricultural by-products is questionable and burning fossil fuels is asking for trouble we've already started getting.

Nor is it acceptable to hide beyond excuses that "the technology wasn't ready".

Let's recap, shall we: Solar concentration through lenses was achieved BC and the first solar hot water heater was build pre-1900.

The photovoltaic effect was recognised in 1839, exploited in 1883 and explained by Albert Einstein in 1905, for which he won the Nobel Prize.

The United Nations held a conference on solar power in 1961 and spacecraft were solar-powered in 1967 (only the electrics, obviously).

The first solar car race in Australia was run while I was in primary school, and Jimmy Carter had solar panels installed on the White House in 1977 - they were later taken down by Ronald Reagan, who believed that the job of a leader and government is to prevent, at all costs, doing any actual leading or governing.

I believe that governments are elected, and paid out of our tax money, to lead, govern and look to the future. I'm also disappointed in their response to water management, but that's another rant entirely.

At this moment, in Australia, we have companies developing quite exciting concentrating dish photovoltaics,  concentrating dish solar thermal and dye-sensitised photovoltaic solutions in addition to the more conventional solar photovoltaic panels. And that's just what I uncovered in five minutes googling.

Whyalla in South Australia (40MW) and Mildura in Victoria (154MW) are both planning, or even constructing, large-scale plants. Yet the best the Queensland Government can do is a lot of plans, high-sounding words, ambitious statements and a couple of measly little power stations rating in the hundreds of kilowatts. Wizard Power is building a 40 megawatt, 4,000 kilowatt, station in Whyalla, a city a lot further south than the Queensland border. That plant is expected to produce 66 gigawatt hours of electricity each year.

According to that ministerial statement, Queensland's "first solar farm" will produce 335 megawatt hours of energy per year.

The state-government-owned CS Energy is building a solar thermal add-on to a polluting power plant, and it's planned for a capacity of 44MW and all it has to do is pre-heat water entering a coal-fired plant rated at 750MW.

For a state that prides itself on self-sufficiency and is selling itself as "the smart state" and "ClimateSmart" and the "Solar State", there is an awful lot of catching up to do and a deplorable lack of ambition. And that's even before we factor in the fact we export more coal than we burn.

Thursday, 9 December 2010

No, that memory card slot is not optional

The more we demand our smartphones do, the more on-board storage they need.

As cameras get bigger and better quality, image files increase. Music playback is now standard, so we need somewhere to put the music files. Many devices still remember when "smartphone" meant being able to edit documents, and we still need somewhere to put them. Podcasts. Ebook readers. High quality video playback. Extra applications (more of a problem on platforms that don't have any to begin with). The list goes on.

And then there's the simple fact of operating systems getting bigger and bigger, and needing somewhere to put all the system files.

Once upon a time, "extra space" meant having a memory card slot. Then someone had the bright idea of soldering a memory card to the motherboard, and hey presto, on-board storage.

Most devices have both for added flexibility, although some of them make it a painful business getting at the removable card - under the battery cover or, in some particularly stupid cases, under the battery. Some only have the on-board storage.

And then there's Windows Phone 7 which, apparently, won't have a card in any device.

I don't care about Windows - there are many other and much better reasons why I won't have anything to do with it - but it doesn't make me very happy when other people decide to save themselves a buck by cutting that off the feature list.

Here are the reasons I will never, if I can at all help it, own a device without:

Easy portability

Let's face it, nobody's encouraging you to buy a phone and keep it for two years, even though that's how long plans generally last. Some devices aren't even supported properly past one year. So being able to take all of the files you want with you from one device to the next easily is nice, even if you're not a reviewer who has to do it several times a week (I'm not, sadly, I just manage to sound like it). Some people, of course, may be tempted to point out that nowadays we can do that easily with desktop software and syncing, which brings me to my next point:

Software agnosticism

Having removable storage means I'm not tied to someone else's - frequently quite bad - idea of how I should manage my own files. I use Linux on my desktop computer, so I can't run most desktop "companion" software anyway, making it specially important for me to not have to care. Microsoft have announced that Windows Phone 7 will only talk to their Zune desktop software, which is one of the very good reasons they can take their software and shove it. Apple devices only want to talk to iTunes, although there are workarounds. That sort of arse-hattery is one reason I still haven't considered buying an iPhone or iPod, even if I wanted to pay their exorbitantly inflated prices. I was bitten by buying a digital audio recorder that relied upon companion software which, surprise surprise, doesn't run on Linux. And even if you are happy using Ovi suite, or iTunes, or Zune, what if you buy a different platform? Ovi Suite will only talk to Symbian, I'm not sure about iTunes but I'm pretty sure Zune won't be happy talking to iOS or Android or Symbian or Bada or... Nokia have gone down a fairly sane route - their on-board memory is generally accessible via USB Mass Storage, the same way USB memory sticks and cards plugged into card readers are - but even then you are relying upon the phone working.

What if the device breaks? 

I managed to kill my N97 mini by leaving it on the roof of a car. My anguished scream is still echoing around the multiverse. Considering the interesting shape the phone was in after it was run over, I was amazed to find the SIM card and memory card unharmed. I could simply plug them back into my ancient N95, resync my calendar and contacts with Google, and away we go - images and ebooks and podcast downloads all intact. My alternative would have been to go to a repair centre, wait an indeterminate length of time and pay someone for the privilege. No thanks.

Upgradeable storage

With 32GB of on-board storage appearing routinely now, this is almost a non-issue. But, what the hell, why not say it: If the on-board disk dies or fills up, having a replaceable, upgradeable extra is not to be sneezed at.

Software installation

You may not have noticed, but some software demands memory cards, or comes on memory cards. Some GPS software companies will send you a card containing available maps. If you install a mapping program that can store maps locally (and if you don't, you're relying far too much upon network coverage), they will often warn against storing maps on a built-in drive.

As a final, bonus point: I don't trust the bastards.

You can make up your own minds, but I know which way my wallet will be voting.

Tuesday, 7 December 2010

You can take your guilt trip and shove it

Our electricity bill landed the other day.

There's nothing particularly special about that fact - it happens with depressing regularity, four times a year.

What is interesting, however, is this little snippet:

"You generated 1.9176 tonnes of greenhouse gas emissions during this period. To reduce your environmental impact, switch to Government accredited GreenPower, and offset the the carbon emissions generated by your travel."

Let's play a little game: How many mistakes can you spot in those two sentences?

There should probably be a hyphen in "Government accredited" because it's playing the role of a compound adjective, it's not clear whether GreenPower relates to travel or to household usage and oh yes: I generated 1.9176 tonnes of greenhouse gas emissions.

I'm sorry, who did?

Over the period covered by that bill, I emitted various greenhouse gases by normal biological processes. My transport patterns, dictated first by the fact I don't live within cooee of public transport, has released many more greenhouse gases but since I use a motorbike mostly, not a car, that puts me slightly ahead of most people but behind those who are able to afford an electric vehicle. I also chose to use household electricity in various ways which, ultimately, determined the size of this bill.

I did not, however, contact the electricity provider and insist upon all of that electricity being generated by fossil fuels.

If I were still living in Tasmania most of it would have come from hydroelectricity, which only generates greenhouse gases through maintenance work. If I was in Denmark, 20% would come from wind power. If I lived in various parts of various countries around the world, I would be getting a lot of it, without making any decision, from various forms of solar, wind, geothermal, wave or hydro.

Because I moved to Queensland, I am getting it almost exclusively from coal.

The electricity providers in Queensland are blessed with high levels of sunlight and large amounts of unused land and even though our water supply is questionable, there are actually generators built into the dams which supply our water.

Yet we get our electricity from a finite, non-reusable resource which is dirty before it's burned and dirty after it's burnt.

I do have an option of ticking a box and getting charged more for electricity generated partially by renewable resources. Because my partner and I are both in casual employment and have debts to pay off, this is not a sane option for us.

On the other hand, the government is complicit by providing subsidies to the fossil fuel industry (PDF).

Subsidies. So stop saying "But coal is cheaper!" or "solar is too expensive!" Let's move all of those subsidies from fossil to renewable resources and see what happens. Of course, that might mean we charge China slightly more for the coal we export, but since there's so much of it I'm almost sure it wouldn't take much to make up the costs.

The reason "I" generated greenhouse gases is because this state is inherently conservative and technologically anachronistic.

I'll make you a deal: I'll keep an eye on my own usage, making savings where I can, and you do your job and plan for the future, whether it involves a carbon tax or trading scheme or not, and stop trying to make me feel guilty by blaming me for your lack of foresight, planning and courage.

The only thing you're doing now is hastening me moving to an alternate provider.

Wednesday, 24 November 2010

N900: Ah, Linux in your pocket

I recently, as anybody who keeps an eye on this blog may have noticed, got my hands on an N97 mini and found it nice but wanting.

Then, in a rare (not being sarcastic, it really was rare) moment of brain-fartery I left it on the roof of my friend's car, from where it hit the ground and was run over by a tram in Melbourne.

Which left me back on the old N95. Which is now unusable because the ribbon cable to the screen broke.

Which, of course, left me needing a replacement and, despite the availability of the brand new Nokia N8 and a swag of new Android devices, I went for something with confirmed power but an uncertain future. Oh, and a keyboard and a Debian-based operating system.

I got a Nokia N900.

This is therefore my usual rambling sort of things-I've-noticed post, and this time not only am I writing it on the device, I'll be posting it as well, using the MaStory blogging app.

So anything could happen.

It is, first and foremost, a Linux computer. This is very, very cool. It means that all sorts of things that wouldn't normally be possible, are. Application having problems? Run it from the command line and see what it says. Try doing that on a different platform!

I am, right now, cheating slightly by writing a few paragraphs from my desktop computer, using vim, after ssh-ing into the N900. Yes, that's all possible.

This is not a phone that grew up and wants to be a computer - this is a computer that shrank enough to be a phone.

The build quality is up to Nokia's usual standard, which is to say: potentially great, but on this device about 95 per cent of great. There are a couple of little niggling things to do with fit and close lines, but generally absolutely solid. The biggest worry is the neat little kickstand that folds out from around the camera housing. It just feels fragile, quite apart from being off-centre.

Now, some specifics:

The screen isn't up to capacitive levels of sensitivity, but is rather good and the image quality is truly stellar. Everything is fantastically crisp.

Camera: great. Software interface less so, and I am disappointed to see that the excellent night mode available on the N95 and N97, with the same camera hardware, is not there. Dual LED flash very nice and there's a program available to use it as a torch.

Speakers: as good as the old benchmark N95, just about.

Text entry: for some reason, there's no on-screen display of the old Nokia standard 'abc/Abc/ABC' lower-case, first-letter-upper, all-upper notification. As it sometimes but not always automatically capitalises first letters (there's a setting for that), it would be nice to know, you know?

The Notes application is a different approach to the 'list of simple notes' application in S60, and damn it's good. A proper little rich-text word processor. I'm using it here (or I was, until I copied and pasted - which is not only possible, but uses desktop-standard keybindings - into MaStory.

Which brings me to: the keyboard. It's so much better than the N97 mini's keyboard, actually friendly to my slightly long thumbnails, good feel and nice rounded profile for easier usage. Could be even more pronounced, but that would probably impact upon the already, um 'noticeable' thickness of the device. Also, having the apostrophe needing an extra key press is a bit annoying for those of us who know how to use it properly. The only other issue is that, as All About Symbian noted, it would be slightly easier to use if taller.

And then there's the writing aids. Has auto-completion but it's quite weak. Has no auto-correction. Having said that, it copes fairly intelligently with punctuation and seems to learn for the auto-completion, which is nice and will no doubt be quite helpful.

Now: Nokia didn't provide any MMS functionality on this device. A fantastic camera, all data options, full multi-tasking, but no MMS. Didn't they *learn* from the first iPhone? There is, however, fMMS, from The Community Of Developers, to fill the gap. Nokia have even released a semi-official statement saying, in essence, "We're not going to provide MMS functionality because, well, gee, isn't it just *swell* someone in the community did our work for us?"

Now, the first problem with that approach is the comment from early in the development cycle to the effect that "I can't make it work yet because it's a proprietary Nokia API." The second problem is the hell of a time I had making it work. I managed it, but I still have no idea how (I think you have to have the right GPRS and WAP APNs configured, but *not* an APN for MMS, let fMMS take care of it).

The third problem is the fact that, as I was swearing with it, I found that my current provider, Crazy John's, don't provide MMS configuration settings for the N900 because it's not necessary on a device that can't do that. Crazy John's have quite another problem in insisting upon doing everything with auto-config SMS instead of just providing a list of bloody settings (you can find them if you go to the Android FAQ pages) but you should be able to see my point: no official supply means no support. Good one, Nokia, for ignoring a fundamental piece of a modern phone.

Oh yes, and not only but also: WTF were you thinking, Nokia, when you built Ovi Maps for Maemo with no provision to keep, let alone sync, bookmarks? There is a workaround - have a Contact for each bookmark, with full address, and it will give you a little globe icon that opens that place in Maps. But oh dear, for a company that invested so much (buying NAVTEQ, for a start) in GPS and mapping - just not good enough.

Moving on.

Multiple homescreens: I'm not convinced it's the greatest idea of all time. There are more efficient ways of launching applications, and it's really only an advantage for dynamic widgets. I think that HTC's way of doing an overview - thumbnails of desktops filled with widgets - is an excellent idea if you're going to have multiple screens. The N900 could do this - it would just be a modification of the current, fully dynamic and live task manager view of running apps. Damn, I wish I had the skills to program that.

There's a problem with some Qt applications. After spending huge amounts on purchasing Trolltech and their Qt, and coming up with two cross-platform device strategies, some twat at Nokia let a release out the door with a default setting for some text fields of black on black. Truly, WTF?

When it was launched, it was notorious for not having any form of portrait mode. That has slowly improved, but where it does appear there are bugs and issues. In typical Nokia fashion, we find a huge WTF in the web browser which, in portrait, gives you a couple of option buttons but no way to access others until you rotate back to landscape. So you can't, for example, close a web page. This is annoying.

Overall, I am enjoying it immensely. None of the twitter clients are as good as Gravity on Symbian (not much is) and at least one of them still hasn't been updated for OAuth and some of them don't work very well at all and the best of them isn't in the repositories yet, but that's a niggling issue next to the sheer power of the device.

Unfortunately, I also have to say "potential" about a device which has run up against a change in Nokia strategy and may be orphaned very soon, but there are some very good developers and they are doing some very good stuff.

And oh, the shiny is great with this one.

Wednesday, 1 September 2010

Nokia N97 mini: SlideIT and LightNotePad

(Prescriptus: I finally fixed Blogger's formatting bizareness: There is a button for "remove formatting", which finally returns things to nice, simple HTML. I have no idea why, after I copied the text from a plain text file, it was messy, complicated and wrong HTML in the first place.)

Part of the challenge faced by smartphone manufacturers is how to get text from the user's mind onto the screen. The N97 mini has a slide-out QWERTY keyboard, but it's only really average in quality and sometimes you just can't be bothered.

There may also be better options.

So let's look at this, shall we: How do we get text into the phone, and where do we put it?


Text entry

Take the very shiny SlideIT keyboard.

Like the somehow more famous Swype, you draw a line connecting the letters of the word you want - in order, obviously - and the software works out what the word is. It's like supercharged predictive text. You can also tap out words and then add them to the dictionary from the keyboard instead of having to drop into another dialogue first.

And it works really well and I'm not sorry I paid for it - although I wish it had dropped in price before I paid up. There are paths that cover quite a lot of words and there are subtleties of usage which you learn over time to improve prediction, but you can also tap out letter-by-letter and be offered predictive suggestions as well as the option to add or delete that word from the dictionary. These blog posts were mostly written using SlideIt.

It is, indeed, very shiny and quite the most relaxed way of entering text I've ever used on a small screen. But its integration with the system leaves something to be desired.

When called it doesn't resize the window you're entering text into but floats over it instead, which inevitably means that it's going to end up covering the text, and quite quickly.

Luckily, there's a button to switch it between top and bottom of the screen, which is a functioning workaround but still feels like a last minute "Oops, we really should fix that!" kludge.

However when you switch the phone to landscape mode the SlideIT interface changes to have its own entry area and replaces the application itself in the same way the system keyboard does.

Unfortunately, although the keys are nice and big in this mode, it introduces an extremely annoying performance bug. The screen has a visible refresh rate. You have to wait for words to be drawn on screen before entering the next one, and gods help you if you want to change the system's selection - it deletes the old word one. Letter. At. A. Time, then draws the new one in.


The grammar model could also do with some work: it automatically capitalises the first word after a full stop, but not after exclamation marks. At least, not always. Generally, when it feels like it. 

It also insists upon capitalising the first letter of some text fields but not all, and refuses to let you capitalise in the middle of a word, both of which make entering decent passwords impossible. You have to disable it, even on the N97 family where the hardware keyboards don't work, by launching a separate application - you can't do it from within the keyboard interface itself.

It would have been nice if they had put the word "Symbian" in the dictionary for the Symbian version.

And one more thing - I CANNOT get it to give me "this". At first I thought I was just being a victim of a particularly common path, but then I found out that said word wasn't in the dictionary. "This," wasn't in the dictionary.

So, of course, I added it.

The next time I needed it, it had disappeared. I had to add it again. And again. It has become a saga in its own right.

The final problem is that it doesn't work with the two programs I most often need text entry in - Gravity the uber Twitter/Facebook/Google Reader client, and LightNotepad the barely-adequate-but-best-choice text editor (see below). Which leaves me at the T9 entry. And that's really, really annoying.

On the the whole however it really is a very cool system, and really would make the difference between me living with a touch only device and me throttling someone.


Text Editors

As far as I'm concerned, every computing device needs a text editor. It's the ultimate basic tool. With a basic text editor you can write letters or emails away from a word processor or an email client, replace a note book, take phone numbers or addresses or other contact details easier and usually faster than using the device's contacts application, and even use it as an ebook reader for device agnostic formats like pain text or html.

So what's available on Symbian? Stuff all, actually.

The built-in Notes application can handle large quantities of text, but that's about it. There's no find, no undo (which has already made my life unpleasant) and this is how you get files in or out to work on them: 

  • In: open in the built-in file manager (or select "Open with system" in Xplore), which thinks it's dealing with an email attachment and asks if you want to save it to Notes.
  • Out: you can't "export", you have to "send". Yes, send via bluetooth, MMS or email, but not actually dump it to a text file on the phone's file system. Yes, you have to email it to yourself.
The only reason I am using Notes at all is that SlideIT doesn't work with most non-system software - when I've finished a chunk of text, I select the text on screen and copy it across to LightNotePad. Unless it's too much, and it doesn't all get copied at once. I have a sneaking suspicion this is due to SlideIt not a system limitation, but I keep forgetting to check.

Then there's DEdit. If you have a non-touch Symbian device, stop looking now. Jbak's text editor is incredibly powerful and has more features, keyboard shortcuts and options than I got close to using.

And it has one very, very useful feature. It can remember your location in a file, and go back there when you next open it.

This makes it an almost complete basic ebook reader if you're desperate, and is invaluable if you have large files.

And it doesn't work in Symbian with touch. Jbak's other invaluable tool the TaskMan task manager does but DEdit hasn't been updated in a while and I'm afraid he may have lost interest in it.

Or, probably more likely, it would be a huge effort to make all the keyboard hotkey combinations work on touch and he hasn't, or hasn't finished, or won't.

I was most upset when I found out I would have to search for a replacement.

Without paying slightly stupid sums of money for a mobile office suite, which would be complete overkill not to mention potentially less actually useful, I only really found one alternative - LightNotePad. The "light" part may refer to its inability to handle files greater than 200kb, which goes beyond short story territory into small novel.

It's fairly basic. It has a find function, a page down button but page up using the green key (which launches the phone dialer at the same time, whoops) and, very useful, the ability to set a bookmark for the file.

No undo, however, which is slightly annoying.

You may think I'm being a bit obsessive with this bookmarking feature but navigating through a file on a small screen can become tedious in the extreme and you can save yourself an enormous amount of time by not having to do so.

And besides: there's ebooks. (quick note to say; on Symbian, if you do want an ebook reader: ZXreader. It's a Russian site, so use Google Translate or something. I use Google Chrome or Chromium, which detect the non-English and offers to translate it for you, very seamless).

I started off being astonished there was such a small selection, but I'm forced to concede I shouldn't be. The number of people who want a text editor on a handheld device and don't want it to read Microsoft formats is, in all honesty, very, very limited.

Dammit.

Thursday, 26 August 2010

Nokia N97 mini: Pity they stopped before finishing it

After two years and no little agonising (look back over this blog's archives if you really want to know) I ended up, thanks to a ridiculously cheap contract which is technically cheaper than buying it outright, but amortised over two years, I have a Nokia N97 mini (Nokia site).


The main reasons for buying, apart from the price, being that it has a good camera, OK speakers, mature OS that I already know, the almost certainty of regular firmware upgrades into the next year, and doesn't actually fall down on any criteria, whereas all other contenders fell down badly on at least one or two criteria. 


Not great, but pretty good everywhere.


And that's how it presents: Not the smoothest, fastest or prettiest, but consistently powerful and has so much functionality built in it's almost complete out of the box. 


But, me being me, I just have to start picking holes the moment I pick it up and turn it on, and have to keep finding holes the longer I use it. See my "Notes from the N95" series if you doubt my nit-picking tendencies.


I shall, for the moment, draw a veil over the time taken to refresh each screen or to change between portrait and landscape and back, because if I start mentioning that I may start crying, and I want to finish this.


Some of the Mini's problems are obvious, like not having a sunlight friendly transflective layer on the screen. But would you really expect charging to be a problem?


It is.

I have a powermonkey, a rubberised little beast of an external power source which made my infamously small-batteried N95 approximately twice as useful and became indispensable to me.

It doesn't work with the mini.

I was to discover that both the N97s are "notorious" for being "picky" with chargers, some people having trouble with genuine Nokia accessory chargers.

This does me not a happy bunny make.

 Powermonkey, however, are brilliant. I sent them an email saying "Got one, love it, doesn't work with my new mini, is this a known problem?" they sent an email back asking for my address so they could send me a new microUSB tip, in case that's the problem. No demand for proof of purchase, just "here, have a new tip, see if that works." Customer service win.

It's long postage from the UK to Australia, so I haven't received it yet.

I shall now mention the stereo ear buds that came in the box. They are, in all but one crucial respect, rather nice. In fact, much nicer than the set that came with my N95.

They have little rubber cups over them that fit really well in your ears and effectively isolate you from the outside world ( although my God does eating toast echo in your head), the cords seem stronger and the control is a very attractive unit, as opposed to the ugly chunk of the N95's unit. And when I plugged it in, I got a message saying to use the phone microphone. Not an actual full hands free, then?

Specific moments of fail (or, on twitter, #fail):

  • system settings and email settings both appear as an application called " settings", which makes life interesting when you're trying to assign a shortcut and you have to choose from a text only list;
  • in old S60 3rd Ed, settings dialogues that had multiple pages had visible tabs. In 5th, there are tiny little arrows instead, very easy to miss. Fail;
  • this is more a design thing: when you select a text field to edit with the soft keyboard, what you get is the keyboard replacing the application you're in with its own sort of scratch buffer, instead of just popping up and resizing the application. You get the full amount of existing text and I suppose it neatly deals with the problem of badly designed applications, but it looks incredibly amateurish;
  • The screen lock switch. Easy to use, but the cheapest and tackiest piece of design and manufacturing on the whole device. It actually rattles;
  • it gives you a message to "unplug charger from wall to save power" whenever you unplug phone from charger. Annoying enough. But, it gives you the same message when you unplug a USB cable. Can't it check, and realise that would be a stupid message to give?
  • there is no transflective layer on the screen, making it all but invisible in bright sunlight. News flash, Finns: some of us live in countries with bright sunlight, and would like to be able to use your phones outdoors. Particularly the rather excellent camera you provided, which can't be properly aimed if we can't see the screen;
  • I think I have just diagnosed one of the worst offenders of lingering-even-after-dead RAM hogging. Nokia's own Podcaster. The one they declined to donate to Symbian. I wonder if I've now found out why? I was having hideous problems with running out of RAM to the point where the only way to get the image gallery to load was to reboot. And everything has improved suddenly, and the only change I can identify is that I switched to the development, official Symbian Podcatcher, which is also better designed and nicer to use;
  • The home screen keeps crashing, and needing to reload. Please note, it has received two firmware updates since release, already, and it's still happening.
So, after all that, what is the single biggest thing the mini needed to be a truly great phone?

Double the RAM. It really is that simple. The screen is unnecessarily annoying in direct sunlight, the lock switch is a little cheap, it could have done with at least one more firmware generation before being released - possibly three.

But the single biggest issue with it is performance, and we all know that the single best way to improve performance of any computer is - more RAM.

It just runs out too damn easily. It has 128MB, and that is just not good enough. It has about 40MB free after booting, and that drops pretty quickly.

The benefits of the most mature and sophisticated multi-tasking mobile device operating system start to disappear when applications running in the background start closing down every time you run something interesting in the foreground - the HOME SCREEN keeps crashing, and that's just stupid.

If Nokia had given this thing 256MB, it would have made the WORLD of difference.

As it is, it feels like yet another own goal, nearly-there effort. And that bites when you're a customer trying to use it the way it could be used.



Next time: third-party software.

Tuesday, 22 June 2010

In praise of hackers and modders

(Edit: I called the i8910 the Omnia Icon in Australia. Actually, that's a winmob device. The i8910 is the HD Icon. Which doesn't sound any less stupid.)

Before I start, let's get a little something out of the way, first:
A hacker is someone who tries to take things apart in order to understand them, and fiddle with them in order to improve them.
A cracker is someone who tries to break things in order to break them for fun and profit.
Right, moving on.
Here's the thing: The world relies upon hackers to advance. Engineers? Hackers, if they're any good. The spirit of "What would happen if..." and "Hey, how does that work..." drives productive creativity and improvements.
Scientists? Hackers, by definition. Hackers of reality and of life.
But the term is a computer one, and it's computer programmers who fiddle who I want to talk about now.
All programmers, if they're any good, are hackers. They want to know how somebody else did that cool thing, they have to chase down bugs in their own code, they're dissatisfied when they see something functioning below-par. They'll sooner spend two days building a replacement than twenty seconds being frustrated.
And they make really cool toys for the rest of us.
Commercial software is built by waged hackers with deadlines and managers. Open source software is built by hackers, some of whom have wages and managers while they're doing so.
And then there's the ones producing not the major product, but the improved version. The one you have to work to get. The operating system that works the way it should have done, if only the company producing it hadn't had commercial obligations or, well, deadlines and managers.
I had a Sharp Zaurus SL5500 for years. It was unabashedly a toy when I got it - a chunky PDA with a QWERTY keyboard and a Linux operating system which satisfied my twin desires of having a cool toy, and being able to type lying in bed. Laptops are too clumsy, too bulky, for lying on your back jotting down thoughts and chasing ideas. Oh, and an ebook reader for Project Gutenberg classics.
Being Linux, an open-sourced system, built using a variety of also open-sourced toolkits and projects, it was only a matter of time before OpenZaurus arose, flexed its muscles, and started producing an alternate, community-built, better-performing, less rubbish software platform.
Okay, buggier as well, but that's the price you pay for development.
I have no idea how many times I reflashed that poor device with new updates, but by the end I could do it in my sleep and it was probably a contributing factor to its eventual, inevitable, demise.
Eventually, however, the SL5500 was replaced with the sexier (black) SL6000, and then the C-series came out with a mini-laptop form factor and a swivelling screen and all the sex appeal that chunky SL5500 never had, and development on the now rapidly aging devices slowed and then stopped, lingering bugs left untreated.
At the same time, my progression through mobile phones landed me at a device with a big colour screen and enough of a java platform to run ebook readers, and then I found a text editor for the phone, and the Zaurus was doomed. The next time I actually tried to turn it on, no amount of hard-resetting, battery-replacing and fiddling would produce the merest flicker of life.
That phone was replaced with a much more powerful one running an open-standards operating system called Symbian with an open-standards interface called S60.
And that brings us neatly to my point, really, because we are now in the realm of smartphones which are more powerful than dedicated PDAs or even laptops of years gone, and one of the defining points of a smartphone is that you can upgrade it.
Which, of course, decent companies do on a regular basis - buy a top-end or even middle-range Nokia and you can confidently expect a new firmware version to bring speed, battery life and functionality improvements every other month for a year or more.
But some don't and, occasionally, others take up the slack.
And then there are those which invite it.
Google's Android operating system is Linux, customised. Which, to geeks and hackers, is like walking into a lion enclosure waving a chunk of dead goat over your head.
While companies pander to network operators and take special note of commercial agreements, hackers cheerfully take the code, rip out the rubbish, port across a cool toy from the next release, drop in something else to fix what everyone except the distributor thinks is a problem, and hey presto! You void your warranty but, frankly, the advantages outweigh that.
If you use an HTC device running Android, you really should be using Cyanogen's replacement ROMs.
Motorola managed to alienate a large community of current or potential users, me included, by preventing this practice on the non-USA Milestone.
It's healthy to have people like this keeping the big boys on their toys.
But let's return to Symbian. The platform, used by nearly everyone but championed by Nokia, who bought S60 and dominated the ecosystem to such an extent that they, in my amateur opinion, damaged its competitiveness, has its roots in 8-bit greyscale devices running for two weeks on a pair of AA batteries, and has been evolving healthily ever since, becoming the most resource-efficient, flexible and potentially powerful of all smartphone systems without, at the same time, really extending itself.
It can support network protocols that are still in the laboratory, but read the international press and you'd get the opinion it's doomed, dead in the water, rubbish, horrible to use, out-dated and slow, part of which relates to S60, which quite frankly is old and has always demanded a little effort to use it properly, and part of which is Nokia being parsimonious with hardware, relying on the efficiencies of Symbian to keep costs down while still providing class-leading functionality.
But then there's Samsung. Unlike Nokia, who cut back on hardware and then spend time and effort optimising the software, Samsung produce truly mighty devices and then just sort of... forget them.
The current king of Symbian, the most powerful and the most impressive, is not the all-singing N97 family but the one-piece Samsung i8910, variously known as Omnia HD (because it was the first phone able to shoot HD video) or, in Australia, the slightly nauseating HD Icon. Great 8MP camera, great stereo speakers taking up each end of the device, great big 3.7" capacitive toughened glass AMOLED screen, 600MHz processor with full graphics acceleration and oodles of RAM.
But the first release had crippling problems, and since then it's had, well, a couple of firmware updates, but not what you'd call love, care and attention from momma and papa in Korea. The C: drive, where the operating system lives, is so small that a couple of system updates fills it. And the discerning smartphone power-user these days demands updates, currency, movement, dammit!
Roll on HyperX. Yes, it's possible to produce custom firmwares for Symbian. Generally, this hasn't been needed, and it's presumably tricky enough that people haven't tried. But for a megaphone like the i8910, hoops were, as the saying goes, jumped through. And even people who normally run a mile from the innocent suggestion that hacking a phone to customise the home screen might not mean the end of the world, have dipped their toe in the water and declared themselves impressed.
I wouldn't be surprised if Samsung sell a few more i8910s thanks to HyperX. I may very well, in the next month or so, be one of them.
Raise your glasses to the hackers and the modders - we wouldn't have got this far without them.

Tuesday, 16 March 2010

How to replace a photocopier with a good camera phone and your own printer.

There is a problem with photocopiers in libraries - University or public. You need money, for a start. Then you need time, you need a photocopier not being used by anyone else, it can be highly wasteful of paper, and of time.
You can get a much more flexible and useful result by using a digital camera and a few minutes of image processing when back at your PC.
Photographing pages and then printing the photos can work at least as well, if not better, and can be done anywhere, any time.
So let's look at doing so.
You need, first of all, a digital camera. A decent high-quality camera on a decent mobile phone is perfect. I've been using a Nokia N95, which is possibly even overkill.
For best results you will need to modify the camera settings slightly. I find that setting it Black & White makes life easier. There may also be settings to adjust light balance based upon flourescent, incandescent or sunlight, settings for image sharpness (more is better, in this respect, because you want nice, clear text) and image size. Go for the highest quality photo your camera can take - you can always discard pixels later, but no matter what the TV shows will have you believe, there is no way to put them back in.
You may be able to do all this as a customised setting so you don't have to repeat yourself next time you want to copy anything else.
You need two things: You need a consistent light level across the entire page, with no obvious areas of shadow or light, and you need a good contrast between text and background. Basically, you need a good background level of light. A flash is particularly poor in this situation, because you are so close to the page that you will probably get a bright spot and a gradient outside that. Your mileage may vary if you have a particularly good xenon flash (those of you who still have N82s can stop feeling smug, you bastards).
I suggest you try and get each page flat, photograph it from directly above to minimise any text distortion, and try and get it to fill as much of the frame as possible. Tip - try and keep the page numbers, you will need them for referencing properly.
Oh, and of course you want them as sharply in focus as possible - practice breathing exercises, if you have a shaky hand.
Once you have the images, you need a computer and good image editing software. If you have access to Photoshop - sure, use it. I use the GIMP, which is free and just as powerful.
To make life easier, you want each photo orientated the right way, and you then want them as legible as possible.
It's also a good idea, financially, to cut down on the amount of ink you print.
You will notice that the image is in greyscale, with a not-entirely white background and not-entirely black text. To correct this, look for a neat little tool called, in GIMP, "Threshold". It sits under the Colours menu, and what it does is take the greyscale image and turn it into strict black and white by picking a degree of grey and making everything below it white, and everything above it black. Very neat, deceptively simple, and if your photos are any good, very, very effective.
I don't usually need to adjust the defaults - you may find it beneficial.
This process should give you pictures with no visually messy and ink-wasting grey smudges, and with the most readable text.
If you want to print, print as you like - I prefer two-up printing. Digikam can print an entire set of photos quite nicely. Picasa can, as well. Experiment with your preferred software.

Sunday, 28 February 2010

Android versus Symbian. Fight!

While I am struggling with the question of whether I replace my current Symbian smartphone with a resistive touch-screen Symbian phone (N97 mini) or a capacitive touch-screen Android phone (Motorola Milestone), I thought it was about bloody time I made a list of vital functions and tried to find replacement Android software, before making the jump.
This is prompted by Steve Litchfield's flawed but interesting similar comparison on All About Symbian between the N97 and the Google Nexus One (that link points to part two, which includes the link to part one).
I'm not listing "top functions" here, I'm listing functions: Everything I use my phone for. Any replacement for the N95 has to be able to do everything I use it for, otherwise: No deal. I'm skipping little things, unless there's a big problem or there's a serious reason to prefer one platform over the other.
Also, I'm only really focusing on Nokias where Symbian is concerned, for two reasons - I know the most about their options, and their history with S60 (they own the company, which helps) gives them a decided edge over the likes of Samsung and Sony-Ericsson.
Address book
Thanks to tight Google integration - advantage Android
Calendar
See above - advantage Android
Email
See above - advantage Android
Camera
Built-in. Obviously, superior on Nokias given their traditional edge and Carl Zeiss optics, but with rapid software development I'm willing to risk a Motorola Milestone.
Advantage Symbian - not only Nokia, but Samsung and Sony-Ericsson are punching hard, here. Samsung's Android phones have been sub-par in the optics department so far, but SE may pull off something great.
Podcasts
Finally, the first interesting comparison. Nokia has the edge here for quite some time, with their own Podcast application managing, downloading, and playing podcasts on most of their phones. The third-party Escarpod, despite the fact that its apparent rapid development has not been associated with any actual new releases, has benefited other Symbian phones.
On Android: Google Listen, obviously. There have been reports of bad instability, and poor user documentation, but there is development. Also, Beyond Pod, My Pod, Doggcatcher ...
Advantage Android, only because Listen integrates with Reader, so you can manage podcast subscriptions easily on any desktop.
Loudspeakers
Nokias are variable - the N95 was brilliant, the 5800 better, the N97 family apparently not so.
HTCs are famously shit, but the Milestone was a pleasant surprise when I heard it briefly. That long gold strip of speaker doesn't seem to be only show.
This is probably a draw.
Ebook Reader
Symbian - Mobipocket Reader, which hasn't been developed since Amazon bought the company (hmmm... I wonder why not?), and QReader, which just hasn't been developed in a couple of years, and most promisingly, the Russian ZXReader (link through Google Translate).
Android - Aldiko. FBReader (which I first used years ago on a Sharp Zaurus SL-5500). AReader. Yep, promising enough.
Draw.
Audiobook Reader
More than just a music player, audiobook readers need to be able to remember exactly where they were in any given music file, and play even more formats.
Symbian - Nokia Audiobook, which is no longer developed and relies upon one specific format, with a desktop PC helper application, and PlatySoft's Scheherazade, which needs Python. Scheherazade goes one step further than just remember locations - it automatically rewinds a few seconds after every pause, helping you catch up to where you where last. Very nice, albeit with Windows 1.0-era interface non-graphics.
Android - Ambling, BookDroid. Good start!
Draw.
Text editor
Symbian: DEdit is fantastic.
Android: Text Edit, apparently. Kote-Lite. And bonus points for GDocs, allowing access to Google Docs documents via a download-edit-upload system.
I'll go with draw, here.
Twitter
Symbian: I bought Gravity, and it really is the premier Symbian/S60 application at the moment, also acting now as a Google Reader reader, and Facebook.
Android: Twidroid is the famous one. There are many others.
A simple numerical count would give Android the advantage here, with most of the Symbian ones crude or java or half-baked, but... damn, Gravity's good! Draw.
News - Google Reader
Symbian: See above - Gravity.
Android: Frankly, the web-based WebKit interface is great, but, yes, there are apps.
Draw.
Facebook
Symbian: Look, I use the web interface, I use Gravity's incomplete but largely sufficient feature. With a 5th Edition touch-screen device, there is an official app.
Android: Oh look, there's an official app.
Draw.
Foursquare
Not important - only just started using it, not sure I will continue to do so.
Symbian: Oh look, Gravity! Unfortunately, that means firing up my Twitter and Facebook access as well. Although I would usually take the advantage to check in on those, the extra data usage does add a little bit of cost and a little bit of time. If I had a huge data plan and a huge battery, I would leave Gravity running. But I don't expect either of those things.
Android: Being an American service, there's already an official app for Android, but not Symbian.
Advantage Android, for having a specialist app.
Mapping/GPS
Symbian: Nokia's latest partly-bullshit announcement of "free navigation for everyone", available on new phones, gives them a really serious advantage in off-line usage, provided you buy a new phone that isn't the original N97, which has (well, okay, mostly had) serious problems.
Android: Google Maps is free, of course, and does navigation for free, and does voice navigation in the USA and will no-doubt be expanded. But, you need a data connection, which means data costs and a signal - not always possible out in the fun bits of the world where the good biking roads are. However, there are commercial apps, and there are solutions like MapDroyd for offline map viewing.
Advantage Nokia/Symbian. You can't beat having on-device, offline maps and voice navigation from a specialist, giant GPS company which provided maps to GPS device manufacturers and was purchased by Nokia at a cost of about US$10billion.
Conclusion?
The actual communication functions are an on-paper win for the Google integration of Android, and a couple of extra native apps.
The camera on a Nokia is a known quantity, and superior.
Everything else appears to be evenly matched, with only my own experience with Symbian giving that platform a real edge.
But hey, isn't the fun of playing around with a new device half the fun of owning it?
Balanced against this, as well, is the fact that Symbian is going through a major shift with the introduction of Symbian^3 this year and Symbian ^4 soon after bringing about a complete binary incompatibility, making life interesting for developers and their consumers.
Oh, and one more thing: Although Symbian is the most sophisticated and advanced OS under the dated S60 UI, and although that dated S60 is still an extremely efficient way of getting things done after learning it, it's beginning to seriously bore me.
Android is just a more exciting platform at the moment.

Thursday, 18 February 2010

Oooh, the shiny! Ooooooh, the SHINY!

This is a rambling tale of two superphones.

I'll use that term, obnoxious as I may usually find it, to highlight the fact the I am not talking about mere smartphones, with good hardware and maybe a specialisation or two, but the cream of the crop - two of the premier mobile devices on sale today.

From Finland, the N97 Mini. One of the best 5MP cameras on any mobile device, all the trimmings in the form of GPS, magnetometer, accelerometer, Bluetooth and high-speed everything, stereo FM transmitter, a big touch screen, a slide-out QWERTY keyboard and the latest iteration of one of the most flexible, evolved and powerful mobile operating systems - Symbian with the S60 user interface. Oh, and it has full, free, offline GPS navigation, something which did nasty things to Garmin's share price. The N97 mini, slightly more compact than the N97, has a more useful shape, was launched with decent firmware, and has better internal memory configuration than the infamously disappointing but slowly improving-in-firmware N97. Not the absolute flagship for Symbian - the Samsung i8910 is still a bit more impressive, even without a keyboard or Nokia's S60 tweaks - but pretty damn near.

From America, the Motorola Milestone - the non-USA version of the Droid, with different radio hardware. 5MP camera, everything else, gorgeous screen, slide-out QWERTY keyboard, and the newest and fastest-growing kid on the block, the open-source, Linux-based Android operating system from Google and, this being Google, an awful lot of functionality depending upon being online - maps, for example. The Milestone, when it was first released with Android 2.0, before Google trumped them with the HTC-built 2.1 Nexus One, was the absolute flagship of Androidness.

Problems? Well, the S60 5th Edition on the N97 Mini is a kludge, the screen is an unfashionable resistive (pressure sensitive), instead of capacitive (which uses the galvanic effect to measure the electrical conductivity of your skin), and Nokia have a not entirely proud history of using the efficiency strengths of Symbian to not entirely hide them skimping on CPU and RAM.

On the other hand, the Milestone has a suspect camera, and Android is still very much in development.

Now, I have toyed briefly with the Milestone, and find the interface to be more shiny than focused, but definitely cool and swish.

I have also handled an N97 mini, thanks to the fact that when I walked into the shop, they didn't have a fake display model.

The build quality was a sizeable step above my N95 (not really praise, that, let me start again...) The build quality was very good, with no wobbles anywhere, and the hinge on the keyboard rock-solid and snappy. The software environment is two evolutionary steps on from the ones I now know backwards, and the screen, although people complain about resistive screens being a pain to use after capacitive, seemed perfectly fine. The keyboard didn't seem too bad, needing only familiarity to be comfortable, and although I didn't agree with the default menu layout, that's nothing that a few minutes customising won't fix.

The Milestone is a very sexy black oblong indeed, from the clean and industrial school of design, well made and is of course very tightly integrated with all the Google services I already use.

Essentially, then, we have two comparable devices, with slightly different hardware philosophies, one with a software platform I know backwards and already have a solid set of tools for, and one which will be an exciting new adventure.

Symbian has a huge number of applications, some available via Nokia's stumbling Ovi Store, most straight from developer websites. Android has a rapidly growing marketplace and developer community.

Nokia consistently build the most comprehensively competent devices. Motorola put their all into the Milestone.

The N97 Mini keyboard looks a little finger-friendlier, the Milestone has a D-pad for precise cursor placement in text.

The N97 is an N-series Nokia and has an N-series camera with Carl Zeiss Optics. The Milestone doesn't.

So it's not exactly an easy choice.

And here's the three big factors:

The screen - One the one hand, the capacitive screen on the Milestone is more sensitive, and better/clearer/sharper (marginally!). On the other hand, it can't be operated in gloves, through plastic map pockets, or with fingers that are too wet/dry/cold. The N97 can be operated with anything you can push it with, including pens, glove fingers, and through water-proof covers. As I ride a bike, and may need it for GPS, or to control music, this last bit is rather important for me. Even if I get a holder, and it doesn't rain, I can't operate a capacitative screen while wearing gloves. Until someone introduces bullet-proof voice control that works with severe levels of background noise, that will continue to be a big issue for me. And no, I can't afford to buy a separate bike-specialist GPS system that acts as a control centre for phones and MP3 players, no matter how much they may impress me.

Support - Nokia have a great reputation for releasing half-finished firmwares, but a better one for steadily rolling out upgrades. Motorola still need to prove themselves, and the thriving third-party ROM scene that some devices enjoy is questionable for the Milestone.

Services back-end - I use Google, and although I don't trust them to ensure privacy, get everything right, make the best decisions or even not fuck up now and again, they know how to make services. Nokia, well... There are many reasons I don't use anything branded "Ovi" except the built-in mapping software, and the fact that I already use Google is not even very far up the list. Nokia I do not trust to build services at all. Although they have improved quite a lot lately, the web interface to Ovi Maps made me burst out laughing in incredulous disbelief last week when I had a quick look at it.

Now, for the less practical consideration: Android is more exciting. Symbian is a known quantity, very solid, with quirks and issues but something I know will give me a superbly functional device. But familiarity, unfortunately, breeds indifference. The touch aspects will be interesting, for a while, but Android is entirely new, and there will be so much to explore.

There is also the fact that Android is evolving fast, and may soon leave the Milestone behind if Motorola or the community don't keep up the firmware updates, while Symbian is rushing headlong towards Symbian^3, due out this year, which will see a progression towards a complete UI overhaul and a graphic toolkit change that will begin to introduce incompatibilities.

So there's not really much to pick between them on that front, I have to say.

Which brings me irrevocably back to the fact that picking between them is going to be a right bitch.

Price is not really an issue - the N97 Mini is $900-ish, the Milestone $700-ish (through Expansys, Motorola Australia went bankrupt), but go to eBay and you can find either device, claiming to be fully unlocked and Australian-compatible, for $600 plus extras thrown in, like car chargers and screen protectors.

It turns out that although I love having choices, I hate having to actually make one.

Search This Blog