11.28.07
Goals for OS2008
While the new OS2008 is the most user friendly and simplified experience we’ve had to date, there are things I’d really like to see both Nokia and the developer community do to keep / make things consistent and easier to use. These are not in any particular order, but are all things I’ve been thinking about regularly since first getting the N810. Each one will add to the list of improvements we’ve already received. I look forward to hearing your comments and seeing what else you think should be added to the list.
- Every device does not have a keyboard, but every application should support basic shortcuts for Close (CTRL+W) and Quit (CTRL+Q). Enable additional keyboard shortcuts as well … this has not been how the tablet has worked to date, but the keyboard is a such a compelling way to control the N810, I am always looking for more ways to keep my thumbs driving.
- Scrolling in menus (system or application) should let me move all the way around whether I decide to go up or down.
- The menu button should work or not work in an application, rather than only work on the main screen. (i.e. Modest message view vs. Folder)
- Finger taps should be the preferred and optimized mode for things. I can still use the menus when they are smaller, but icons and general UI widgets should be designed for fingers.
- Use a repository for your application. I’ve installed plenty of .deb files but these do not restore today when you backup and update your device. Applications installed from repositories, however are able to re-install easily. Repository based applications can also provide an update notice within the Application Manager. Early stage Garage apps as debs is OK, but as things progress we really need a repo system. Perhaps the Maemo team can help create one the community can manage.
- There are system UI alerts as well as a programmable LED on the N810. Take advantage of these things to let the user see what’s happening with applications that provide notifications I would really like to see either an application based preference or a system level control panel that lets us define how we want to see notices for applications by type. (email, rss, im, voip, mauku, etc…) The N800 has an LED as well but I am not sure it’s programable in OS2008.
- Let us set default applications for things. I thought I read that the release of Modest will have a setting to replace the default email application in the same way we chose the browser engine when MicroB was released. I should be able to also choose a default voice app (I have three + a SIP account enabled now), IM and RSS reader for starters.
















VoIP & Gadgets Blog said,
November 28, 2007 at 2:02 am
Khertan said,
November 28, 2007 at 4:16 am
>”Use a repository for your application”
Yes of course, but it’s really annoying that there isn’t simple method to create a repository except on debian system, and when i follow the debian tutorial to create a debian repository it’s fail on the maemo app manager.
There is community repository for maemo, the extra, but you need to use an other debian tool dput. And requirement to upload a deb are very annoying ! Specially for onboard developpers like me, which create his package onboard.
ossi1967 said,
November 28, 2007 at 4:39 am
You say “Finger taps should be the preferred and optimized mode for things.”
This is becoming the subject of more and more emotional discussions in various forums. A lot of people seem to like using fingers instead of a stylus for reasons I simply have to accept (but will never understand).
There are, however, people like me who prefer the stylus.
Now moving everything towards “finger friendly” would have some serious drawbacks (the new main menu, for example, is a mess, and we’d see more of it then). – I’d prefer giving users the choice. The choice we already have with two keyboard layouts. The choice we used to have in OS2007’s main menu. Make it a system setting: “finger” or “stylus” and let the OS adapt. I dont see any use in annoying part of the user base by dictating the way of use.
Jaffa said,
November 28, 2007 at 5:04 am
@Khertan: dput is just a basic wrapper around ssh, AIUI.
Search maemo-developers there are details on uploading to extras(-devel now) without dput.
fanoush said,
November 28, 2007 at 6:04 am
Might be useful to file your issues in bugzilla too.
The “Scrolling in menus (system or application) should let me move all the way around” is already there, feel free to vote for it and add comments
http://bugs.maemo.org/show_bug.cgi?id=987
Quim said,
November 28, 2007 at 6:25 am
Please don’t encourage people to create their own repositories. If someone wants to do it, fine. However, in maemo-developers we are discussing extras-devel and extras as default placeholder, being both repositories meant to be maintained by the community (details being discussed as well).
Khertan said,
November 28, 2007 at 12:29 pm
jaffa > don’t find it.
I dream about a small repository with a html front end, where user can add their package only by uploading a .deb and after a validation, their package appear magically in the repository …
timsamoff said,
November 28, 2007 at 10:52 pm
Thanks, Jonathan… I’m going to try to work a couple of these aspects into my UI doc.
Momchil Karabulev said,
November 29, 2007 at 8:27 am
i think it’s important to add a shortcut to switch keyboard layouts when using bluetooth keyboard. just like this is implemented in linux or windows
Add Keyboard OS2007 - Dogpile Web Search said,
November 30, 2007 at 11:14 pm
spidy said,
January 3, 2008 at 8:14 pm
More Improvement Suggestions from a user interface designer!
The Home Screen:
This needs to be redone. I would much prefer to see a modular space like igoogle.com implementation. Each module is defined in usable areas and layout options can be selected for each applet. ie full module or collapsed
Maybe even a tab structure that can be filled with application shortcuts or mini versions of the apps.
Screen Off Feature:
There needs to be an easy way to turn the screen off and locking it but not turning off the device. I would follow the iPhone usability for this feature, where the power button turns the screen off and when you hold it down you turn the device off.
Finger Vs. Stylus:
The finger usability should not compromise the stylus input. This can be address by using input size comparison. If you are using the stylus the input size and pressure is concentrated in a smaller area and if you are using a finger the input are is much larger and should enable a response system for finger use. i.e. if you were to click on a button with a stylus it should respond normally and if you are using your finger it should maybe get magnified first or some kind of alert to tell the user that they are currently on a specific icon or interface. I’m going to use the iPhone again for example; their implementation of they touch keyboard does this excellently!