View Single Post
Posts: 77 | Thanked: 160 times | Joined on Nov 2009 @ T.M.O
#480
Originally Posted by nosa101 View Post
But has adobe released the porting kit?
Sure, we know they release it but have they?
I'm sure we don't need Nokia to answer that because Adobe did the releasing.

If they have released it, then we can ask Nokia if it will be ported. I think Adobe is full of schit
As evil or full of schit Adobe maybe. Nokia isn't any better come to think of it.

I know its off topic, but look what happened with the whole N7x0, N8x0 upgrade fiasco. I never even owned one.. but still felt really bad for the poor souls after having read up about it.

Look at what is happening with the Meego-Harmattan/Meego upgrade path. A long long silence and then among the PR1.2 press release a little snippet of the news of no official update to the next OS on the N900. Of course they knew all along and that is why its an underhanded move on Nokia's part.

Suddenly a flood of, "hey lets make a community supported version come up". For what, damage control? Can't really be all altruism now, can it? Yes, I applaud the community effort massively(and appreciate Nokia's help too in this regard), but I still feel burned

Am I surprised considering how Nokia has for so long handled the issue of upgrades on legacy devices? NO!! And that's why it hurts more.

IMHO unless they have a UI so heavily reliant on multitouch, like lets say like the new leap feature on the HTC Android phones. I see no reason to drop the official upgrade path. Most other multitouch requirements can be taken care of +/- sliders in applications. And multitouch keyboards are less of a requirement for the N900 users considering we have a HW keyboard.

Look past 4.00 on this video to see the leap feature in HTC
http://www.youtube.com/watch?v=vDd8__9Nvug

The N8x0 was left out for not having an OMAP3 Soc. The N900 for what? A resistive touch screen!!!

Originally Posted by Peter@Maemo Marketing View Post
Let's remember that this all about user experience. Polishing software is a lot of work. Polishing each application for resistive screen (as good as it is) is not trivial considering that we are making the UI for our Nokia product on MeeGo for capacitive screens as we have said already in Maemo Summit 2009.
I would think that the OS is supposed to handle the nuances in hardware, not the applications themselves.

Qgil eloquently, described the problem at hand some time back.
Originally Posted by qgil View Post
This argument combined with the argument of the 'designed obsolescence' also pops up regularly.

It is true that 'Nokia sells hardware' but this is just part of the story. Nokia develops a consumer offering based on devices, software and services. Harware is very important in this strategy and so are the software platforms, the application developer ecosystem and the Ovi services. As opposed to a specific device, software and services can be continuous and evolutionary. They can support very well the very important job of customer retention.

If the owners of a Nokia XXX are happy with this offering, one day they will move to Nokia XXY, or perhaps Nokia YYY. They will recommend Nokia to their relatives and friends, etc.

If the owner of a Nokia XXX is unhappy because one or more of the pieces described above doesn't work, they will start their walk away to other competitors.

So you might get WONTFIXES and FIXED in [next release], and that [next release] might or might not be available for your next device. But don't think that Nokia doesn't care about bugs in current releases and about the satisfaction of the users getting those bugs.



What do you mean 'reduced activity'? Can you express it with numbers or some more details?
And I'm clear on where my loyalty won't lie after the N900. I will happily move on to Meego in the future(and continue enjoying my N900 for now), but probably not with Nokia


Meh!! if flash 10.1 isn't coming to the N900. I now have bigger things about the N900 to worry about

Death to Flash!!!
Most companies in any case will support H.264 in the hardware and have appropriate licenses. While it will suck for pure FOSS supporters, I hope the new Google WebM project takes care of that too.

Jobso is right here. I don't want a middle man between my content and the content provider. Now, if only he could ever convince me to get tied down to his draconian locked down though buttery smooth iSchit
 

The Following 3 Users Say Thank You to un-named_user For This Useful Post: