Showing posts with label symbian. Show all posts
Showing posts with label symbian. Show all posts

Wednesday, October 1, 2008

Christmas wishes from N95 S60 firmware

It's Christmas time soon, so I decided to put out a brief series with humble "wishes for improvement", the features that I would like to have as Christmas present from Nokia Santa (if there was one)... well, there's hope... Lapland is there in Finland... :)

The first round is, actually, about things I hate most in my current N95 v30.0.016.

Frankly speaking, S60 firmware team have made great progress in term of both the code stability, speed and power consumption. Kudos to the hardware guys!
You are a reason for Nokia to rock.
But there's not much done in terms of improved user experience.

Sad to say, but almost 2 years have passed since it's flagman phone was out, and some pretty obvious "features", those that derail the user experience from the "happy thoughtless bliss", have still not been fixed.

I know, I know, we geeks are all so adaptable to anything, but as a pro with an "eye for UI" I still refuse to adapt and still I go reminding all you S60 PM and the coders alike - this is what will make S60 (and so my N95) User Experience very much better:

1. Access Point preferencing, please Santa!
We still have to answer to each bloody application, which bloody AP to use.
Please please please Nokia, make the system-wide panel of preferenced Access Points, and the future strategy of each app is to either (a) respect the system AP pref, or (b) well, there's better be no (b)...remove all AP settings from zillion places in zillion applications (N-Gage, VideoCenter, E-mail etc).
So far, only some WAP bookmarks in browser need a separate AP, and of course MMS sender/receiver.

2. Don't lock my phone, please Santa!
Like I already ranted here, there are smarter ways to know if your keypad needs to be locked.
For a start, unlock the phone if any cable is being inserted (the phone is not in a pocket or a bag, it's in the hands),
then, keep the phone unlocked if it's being charged (it's surely not on the go, either).
In other words, think of ways to keep the phone accessible...
To skip keypad autolock in such situations would be nice, for example.
This would let the user implicitly lock the keypad, if so desired.
The current behaviour makes usage of phone in home/office fixed locations miserable - just to read new SMS fast we need to click 4 times (two for unlock, one to close confirmation, one to show message).
Keypad lock/unlock confirmations are a nuisance! They hug my workflow for 2 seconds! I feel punished.
Why we need them at all, when the key sign in the upper panel is the indicator already?

This is pretty burdensome and counter-intuitive. Imagine sliding your finger to unlock iPhone, and then boom! 2-second modal dialog to confirm...yuk

I would very much appreciate it if you'd unlock the keypad for me, when I insert a USB cable or an Enhancement, so that I could choose the mode RIGHT ON. Me and you know I can't insert something when my phone is in my pocket (and thus, under danger of erratic key presses).

And while you're there, please make an option to switch off connection warnings in all apps which use network (MOSH, Download! etc).
I don't like to be pestered by warnings, that's the Microsoft Way...









3. Permit my signed Java, please Santa!
With all those certificates, there's a reason to think that it did filter out the unwanted (malicious) unsigned programs during installation phase, and now we have only perfectly legit java MIDlets installed.
Now, what with pestering me out with incessant requests for permission of network access etc?
I know, you know, that Opera mini has to get the network, otherwise no fun. I know, you know, that it was signed with a certificate for all those access things.

Then why there is no persistent permissions for my installed java applets? A simple checkbox would let the phone memorize my trust settings and do not ask me every launch. In fact I do believe in defense-in-depth, but are we not paranoid here? Maybe we can let signed apps do the things they want?

4. Lifeblog will Sound, please Santa!
Lifeblog is the best thing that happened to S60 in all it's time.
It is the focal point of data aggregation, and the underlying interface for Ovi services, it's the technology which can (and should) be adapted for every phone, maybe even merged with Search 4.0 functionality.
There is support for Sound Recordings in Lifeblog. You have to start them from the Lifeblog, and they appear on the Timeline, and they get synced with Ovi or PC Suite, and they go to your PC!
But - when you make recordings straight from Voice Recorder app, LifeBlog does not see those sound files.
Come on, this is an omission. Should be fixed, IMHO.

It would make great sense to include the 'normal" recordings in Lifeblog, and not force the user to create them in Lifeblog, thus separating and isolating Lifeblog from the data which is already generated.

How many of you created at least one sound rec from within Lifeblog?

For ex. when you take photos straight from the Camera, or send SMS straight from Messaging, Lifeblog sees them all.
But not when you make the Sound Recordings. This eventually leaves a lot of sound bites out-of-sync, you never see them on PC, unless you do the hoola-hoops jumping to get them specifically via some other process (hunting down, copying, deleting ...yuk)...
Would be wiser to join them into the Lifeblog circle of things.





5. Lifeblog will Note Me, Santa!
Now, I had written previously about Notes sync here, and the dead is still not done. I have also filed bug requests during PC Suite beta 6.85 and 6.86 about incorrect timestamping of Notes during sync. Nothing changed so far.
This time I will speak from the firmware team perspective - how to treat them on the phone.
And I mean the Lifeblog strategy and features here.
Right now - we have two sets of Notes - the ones on the phone and the one in LifeBlog.
Lifeblog notes can be created, seen and managed only in Lifeblog. I think this is the second most important Lifeblog problem - since the rest of your "normal" notes in elsewhere, and so - kept out of normal Lifeblog sync cycle.
Timeline is the best presentation you can get, to see things in a time-sorted order.
Here it would be very nice to see the Notes that we already have on the phone, and not to force us to create new ones from arcane Options menu.

How many of you created at least one note in Lifeblog? I doubt there are many such geeks...

Why there was such need for note data fragmentation is quite unclear.
Would be wiser to join "normal" notes into Lifeblog circle of things.
This would make the Lifeblog the powerful all-absorbing one-stop technology for all user content, except for web/e-mail and 3-rd party.
Integrate Search 4.0 into that - and we have a killer app, nothing similar exists on competitor symbian-based products (Apple has Spotlight and iMovie/iPhoto/iSync)
Also please Santa, make a LifeBlog app for my Mac! I still have no automatic way to backup my messages and notes and sounds there. (OK I know that one's too much to ask by Christmas, just count me in for the Ovi Mac Suite beta)

6. Better Podcasts, Santa!
There are few deficiencies in current Nokia Podcasting application.
One of them is the the podcasts titles stop scrolling as soon as I start downloading at least one podcast. This makes selection of some other podcasts to download impossible, if the podcasts have long titles. A good example is our Mobile-Review site.

Second drawback is that there seems to be some sync lacking between Podcasting app as such, and the Music Player's "Podcasts" section.
Since you can play podcasts in both places, but each of them keeps it's own DB of podcasts status - "played" or "not played" statuses are separate in both apps for the same track.
This makes up for user confusion when you see tracks as "new" although you've actually heard them all...

This is explained by the following scenario:
(a) You open Podcasting download two podcasts (podcast1, podcast2) from, say, "Voice of S60"
(b) Now you can see the Yellow (unplayed) status of both podcasts in the Nokia Podcasting apps
(c) Going into Music Player now, you can find both podcasts in the "Never Played" section
(d) Play the podcast1 in Music Player, and you see it disappear from "Never Played" in Music Player
(e) Going to Podcasting, you still see yellow color of both podcasts, as if they never played.
(f) Play the podcast2 now in Podcasting, and see the color change, and the icon change to black checkmark
(g) Going back into Music Player, you still see the podcast2 in the "Never Played" category

I should notice here also that Podcasting app handles Russian (and maybe other international) titles well (ex. Mobile-Review),
but the very same podcast titles looks as boxes in the Music Player, which, apparently, uses a different code to render MP3 titles.








Can't you Santa do some code re-use? :) I simply can't read it like that!


[update] There's also difference between Podcasts and Music Player in marking listening position.

Music Player (not Podcasts!) marks the place where you left off/stopped playback in each podcasts, and gracefully resumes playback, should you try to play a podcasts which was not "rewound" or listened to the end.

Podcasts, on the contrary, makes you start from 0:00 every time, which annoys me because I expect I could play podcasts while I manage them, download new episodes, navigate directories.
Seems like to do this, I have to leave podcasting and start Music Player instead.

All said, would it not make sense to disable playback option in Podcasting, once and for all?
Or... make that option switch to Music Player instead?



Such are my humble wishes to Nokia Santa, if there was one. I do not ask just for myself, neither I need more Nokia hardware.

Just please "play nice" with those "dumb" and "tired" users like me, will you, please...? :)

Saturday, July 12, 2008

Blue Phone for the Elite

This time, I want to share my joy.
While it's only a part of my user experience, Macs had and will always be (hopefully) taking some 'warm place' in my heart.
But there used to be some 'gotchas' for an advanced Symbian smartphone users like me.
There are simply no PC Suites at all, neither from Nokia, nor from Ericsson, not from other UIQ/S60 licensees as far as I know.
Well, "good riddance", I can hear you mac users say. "What's not there you don't need (only want?)" Not quite so.
It's only that the most "painful points" are closed on Mac, with the help of iSync and the Modem Scripting for GPRS.

(I should note here that iSync is able to reconcile all your devices in one go, be it Palm and 2-3 phones plus add .Mac account - all those sources will have the same data after you sync them in a single pass, just press one button.)

But the third most "painful" point for us 12-button peddlers is, of course, the text input.
Now, I don't know about you, but I hate T9. It works (kinda) but then again in my N95 half of the times I use it - it has wrong Input Language, and it's not easy to switch between the keyboard layouts.
Think of trying to enter some Russian in Nokia Maps - and your default input is English.
It takes a serious trouble to travel all the way to the Phone Personalization and back. Sometimes I just give up and curse.
On another note, entering contact names should not have T9 on by default.
There are many use cases like those... but we diverged.

Anyway you look at, typing on your Mac is much faster than on your phone.
So there you have - the need for some "serious" messaging application, right on your Mac where you have "the digital hub" (sorry Nokia, the "multimedia computers" are mostly "for the geek of us").


And BluePhoneElite delivers!




I should confess I've had a "long-term relationship" with this program before I could make my fairly weighted judgement and present it to your attention. This envolved seeng it develop, helping it develop, filing all kinds of suggestions, trouble shooting etc.
The good part about that the now you don't have to bear through all this.
The products is ready. And I highly recommend it. This is what many PC Users dream of - but for Mac Users only.
No bloat, pure meat. Yet very extendable and it has plug-ins and scripting.

The functionality of this product differs a lot from the Nokia offering.


First of all, it's an online product. You don't have to press buttons to "Refresh" the list of SMS, calls etc.
You have the freshest view as long as your bluetooth connection to phone is not broken.....

Secondly, it's a multivendor offering. You can have many phone from many manufacturers connected and working at the same time. When you want to send a message, simply select the right phone from the drop-down list.

It's like iSync - no matter what your hardware, you'll have the best features available.
And no need to put tons of bloat from every phone maker. (Heh, good part about this rant is that Nokia does not yet produce "bloat" for Macs)
Thirdly, you have the calling functionality thru your Mac!
You can use Mac's headset (or speakers/iSight mic) to do voice calls.
Just like Skype, only really via GSM/CDMA.


Once you get an incoming call, a nice window pops up, with the number, name and the contact's picture from your Mac's Address Book. Incoming Text messages are also popping up, giving you options to Reply of Forward them.
There is a nice capability to enter text notes for each voice call, made or received. You can type during the call as well as after the call.
The only pieces missing are MMS support and there are some minor UI "misconceptions", like the Device Folder grouping in Message Center, or showing all the same Recent Calls in every phone's context menu.
Those can be easily adapted to, and if there are enough user requests, I believe it also can be changed.
I personally believe that the future of this program's UI is adding back the unified calls+messages centre, but per each phone, so it would not have the current Mac-centric view, where every known call or message is shown on all and every phone. Add the invocation of those by double-clicking the phone's icon and I'm done!

My experience also shows that the developer support is exceptional! I usually got friendly responses for every of my e-mail within just a few days. As a small company, Mirasoftware does it's best at providing meaningful answers, support and bug-fixes. A bugfix within a week - I would like Nokia to try and match that!

A very nice touch is that they always provide an exact bug-fix list with every release. For those who like to see what changed, it's indispensable.

Another nice feature is reading the phone book directly from the phone when you address a message or a call, and no, you don't have to hit "Refresh" to get the newest version. As long as you have connection, BluePhoneElite2 has the synced version in cache.

The product costs 25 USD and is well worth the money. A time-limited trials are available for you to make sure you have the features supported. Sending a support request even during a trial is no problem, and there are all the chances that (in rare case of issues) you'll get the bug-fix and will have the "green light" to buy.

And so did I !

N.B. N95 is fully and perfectly supported.

Friday, August 3, 2007

Wildcard Caller ID idea


Hi Experts,
I'm back with an idea of a little neat feature for Symbian (and possibly others) cell phones.
The idea is simple - to make user's life easier by recognizing (via Caller ID) groups of numbers matching a wildcard, not just the whole exact number of a Contact. Let me show you how.
You have Contacts in your cellphone's Address book. The phone matches the incoming CLI (Caller Line ID) of the caller to a number in the Contacts. But what if you want to identify a group of numbers?
This could be useful, for instance, to quickly see from which network (or city) you are being called, or from which company. It's no secret that many companies get pools of consecutive telephone numbers, so you could be quickly seeing from which company you get the call even without filling your Address Book with all employees' numbers.
Business customers may be interested in this feature. It would be a beneficial, value-adding feature for a platform, and a marketing differentiator, to provide a new type of contacts in the phone's address book - a template (wildcard) contact.

Usage example 1: Let's say I have the following entries:
+74955556666 Lena (BeeLine), +16457236546 John, +791687458755 Lena (MTS).

What if I could enter Address Book records like
+7916* MTS, +1* USA, +7903* BeeLine, +749512388## Forbes, +7812* St.Petersburg ?

Like in UNIX wildcards,
* (star) stands here for any number of any digits, # (mesh) stands for any single digit.

Usage Example 2:

I was 'phone-abused' by a real estate agency in Moscow - they have lots of employees in many offices, calling in from their office phones, all from the same pool +7495363####. I wasted lots of time answering their calls, telling them I "wrong number" and so on. They seem to have had wrong number of a client written down. Had I had this template contacts feature in my phone, I would have not need to squinch my eyes trying to see first digits and decide if I need to pick up.

Usage Example 3.

When late at night someone calls you from abroad on an important mission, it would be nice to see it's from another country (a word "Germany" shown) instead of trying to wake up and see if the first digits are +49.

Sounds good? Might be even better! (options)

"Exact match" means the current way of doing things - all numbers match.
"Wildcard match" means the new, group match.

A cellphone shows not only the exact match, but also the next worst match from a wildcard entries. And it could even highlight the part of incoming number that matches a wildcard, with a different color!

This gives a user, at a quick glance, a good idea of who might call, or where from, without the annoying deciphering of the caller ID by himself. If there's no exact match, the call history shows just the full number. If there's an exact match, and a worse match, the call history logs
the 2 longest matches. 

Please tell me what you think.