|
2009-10-28
, 15:35
|
|
Posts: 5,478 |
Thanked: 5,222 times |
Joined on Jan 2006
@ St. Petersburg, FL
|
#82
|
I guess if people would ask at the same time that why aren't more Nokians actively involved in these forums and at the same time would read the general tone and respect level of the individual messages, for instance in this particular thread, you would perhaps see some hints of the potential conflict built within.
The Following User Says Thank You to GeneralAntilles For This Useful Post: | ||
|
2009-10-28
, 15:45
|
|
Posts: 733 |
Thanked: 991 times |
Joined on Dec 2008
|
#83
|
|
2009-10-28
, 16:20
|
Posts: 1,255 |
Thanked: 393 times |
Joined on Oct 2009
@ US
|
#84
|
Everyone outta just relax about phone functions and all the little features they want. It's a new phone with a new (as a phone) OS and not every little thing will be perfect immediately. But I'm sure most concerns will be addressed quickly. A bit of patience will get well rewarded. I average 15-20 calls, several messages, many emails a day and burn through around 2000 minutes a month. And I'm STILL not worried. It'll work well enough and even better soon.
As a comparison, when I first got my (pre-ordered) G1 it was also a new phone with a totally new OS. With the exception of the notifications system, Android was woefully basic and underdeveloped. Had about 6 apps available, an email client so basic and unreliable as to be almost unusable, not-so-hot browser, no bluetooth, etc. etc. etc. The 'nope' list was pretty long. Plus, the only Android phone, the G1, had very limited memory and was not too speedy.
But Android still succeeded and not just as a 'niche' product, but in a big way with general public users. Developers quickly stepped up, wrote some apps - and we see an explosion of Android hardware only a year later.
The N900/Maemo combo seems to me to be already way ahead of where the G1/Android was a year a go when Google and T-Mobile decided they were ready for public release with much fanfare. The hardware is already there, there's already experienced Maemo developers. Just need to add a few things to Maemo, do a little tweaking. No sweat.
So like I said - I'm not worried at all, this will work out fine. But I am gettin' kinda tired of waiting...
|
2009-10-28
, 16:26
|
Posts: 3,841 |
Thanked: 1,079 times |
Joined on Nov 2006
|
#85
|
|
2009-10-28
, 16:33
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#86
|
The Following User Says Thank You to Texrat For This Useful Post: | ||
|
2009-10-28
, 16:59
|
Posts: 234 |
Thanked: 160 times |
Joined on Oct 2009
|
#87
|
Unfortunately this is a self-fulfilling prophecy. People get irritated because Nokians generally refuses to interact with us, so more Nokians will refuse to interact with us, so people get more irritated, etc.
Once again, broken process. Broken process. Broken process.
It's not our fault if the way management has set things up puts you in between a rock and a hard place. Obviously that needs to be fixed, but you can't blame the current situation on us. Nokia has a pretty clear track record of not getting how to handle an open source community (see the Bugzilla Fiasco that's been ongoing since 2005) and the irritation you see here is simply a side-effect of that. Treat people with respect and you get respect in return. It's a two-way street.
|
2009-10-28
, 17:09
|
Posts: 130 |
Thanked: 46 times |
Joined on Sep 2009
@ New York
|
#88
|
|
2009-10-28
, 17:11
|
|
Posts: 5,478 |
Thanked: 5,222 times |
Joined on Jan 2006
@ St. Petersburg, FL
|
#89
|
As a software engineer by trade, I can understand having a level of indirection between the developers and the customer. Fact is, customer requests CAN get in the way of a developer doing his job, depending on how combative the customer is. There aren't usually problems if the customer is well behaved, but when they are not, it can turn into a mess. That's why I find the request for 'transparency' being something that isn't all that attractive to the developers. The indirection allows them to get the work that they need to get done, done without outside interference. It is up to management to interface with the bug list and set priorities of items on the list based on difficulty and overall usefulness of any fix to the general community.
|
2009-10-28
, 18:10
|
|
Posts: 11,700 |
Thanked: 10,045 times |
Joined on Jun 2006
@ North Texas, USA
|
#90
|
Very good point- most people that will buy the N900 will probably "assume" the [filtering/sorting] function is already there, so no need to be vocal about it yet.
Tags |
phone, usability, user interface |
Thread Tools | |
|
Ragner, you point is taken - you wanted a consistent UI (which in itself it a good design principle).
But the community point (at least in this thread) just because tabs is eliminated as a result of the consistent UI decision, doesnt mean a function (compartmentalizing a long data list) should also be eliminated.
There should be an alternate way of achiving the same effect - which as many have pointed out by way of filters, or other UI effects.
And if there is no BETTER UI means of achieving this , then tabs should be considered because of its own merit as a data partitioning method - even though it breaks the original design principle. In some cases if the best effect is used to achive something and it goes against a principle, its worth doing it - since there are no better alternatives.
Of coutrse is upto the Nokia UI designers to determine the best method - and the community can provide some great ideas. Its best for Nokia to listen to these ideas at least.
Personally I DO think Nokia is listening as they have so far - there may be diferences, but Ragner's and Quim and other's participation itself is a sign of those listening ears.