Today I installed Debian onto my Neo FreeRunner, to be precise the relatively new, Debian based community distribution FYP, which basically combines FSO/Zhone with LXDE. As it is a very new distribution, this post can’t really critisize it, it’s just about writing up some things i noticed and some ideas regarding usability on the Neo Freerunner – rather regardless of the distributions. FYP is just the drop of water inspiring to write this, the first two paragraphs will be Debian related, so you can probably skip them if you’re in a hurry.
First of all, it is great to have an easy way to setup Debian on the FreeRunner, as I said before, Debian armel has great repos, compared to most other FR distribution, which make it easy to try out many applications on the FR without having to compile them oneselves.
But you have to keep in mind, that Debian isn’t focussed on mobile devices, so additional repositorys with software aimed at mobile devices are a necessity in my opinion. This is an observation I made while using Debian on the MDA Pro/HTC Universal some time ago, and I didn’t change my mind on that, examples i remember are the embedded version of Abiword or tools like xmonobut helping you with right clicks, which would be nice to have in such an additional repository, but which partially could lead to confusion in regular Debian.
But let’s come to real usability issues, anyway. In terms of usability there are two kinds of distributions on FreeRunner, those who aim to be finger-friendly, and those that just want to have basic features finger friendly, but require a stylus for the rest – FYP is one of the latter. I think that both usage ways have their point, i like finger friendly efforts a lot, but I like to use software I know from my desktop as well (BTW: I would almost always use a stylus, as long it is a small and handy one – as i hate finger prints, wear,tear and dirt on the display – even think about getting a capacitive stylus for G1 – nontheless: finger friendly is stylus friendly too, as you don’t have to be that exact), at least as long as their is no finger friendly alternative.
An usability issue, which is rather an aesthetic issue, i see on distributions like SHR is that they mix different toolkits, like etk and gtk – the applications look different, and while enlightenment related apps are close to be too beautiful performancwise, gtk apps often look old fashioned or sometimes even bad at all. I think it was Midori on SHR unstable (I know, just a framework demo, not aiming to be a real distribution, but nontheless used by some as one), which looked really bad, using the nice old orange OM2007.2 icon theme, but a plain grey gtk+ theme (i am sorry that i didn’t check, which one) – but the OM2007.2 GTK theme wouldn’t have resulted in a much more appealing UI anyway.
In my opinion these optical issues should be fixed by an “optical initiative”, which rolls out one theme, which makes GTK+, ETK.. etc. apps fit better optically, while being fast and not eyecandy in a way which messes up performance, as performance does really matter and anyway: I personally adore simplicity. This means: Don’t use too power hungry GTK+ engines (e.g. I was really surprised to see FYP using clearlooks… imho not a good idea) to match up with Enlightenment effects, rather remove some “bling” of Enlightenment.
I believe the style “hackable:1” inherited from OM2007.2, the ASU look and the style of new and upcoming “Paroli” are good examples of what I mean.
Additionally I would propose to implement a simple way to enable the user to switch between GTK-iconsets and themes (or rather two configurations of one theme) like a button among illumes applications (or even better as a panel plugin), as there are basically two kinds of applications using the GTK+-Toolkit on OpenMoko devices: Those written for the Neo FreeRunner and familiar embedded devices (OM2007.2, again) and those written for the desktop but being lightweight enough to run on embedded devices like the FR (btw, it would be nice to have a probably xmonobut like easy way to perform right mouseclicks, too) .
I strongly believe that this could lead to a better usability or even workflow ;-) (and so to more popularity for the free platform of OpenMoko and the community) and would be happy if anybody would pick this ideas up soon – being pretty sure that i am not the only one worried about usability and aesthetics.