Originally Posted by matthewcc

So, today I had an opportunity to hear an interesting lecture that talked about messaging. One thing that I hooked onto was this concept of choice vs. the right to choose. I think this is especially important as Maemo becomes mainstream.

Today, as described, maemo is all about being open, free and accessible. The benefit of this is a platform that embraces a diversity of ideas and sources of innovation. The downside of this is this degree of freedom is (or may be) considered cumbersome to the mainstream user. So I would like to start a conversation on what is more important.

Choice or the right to choose

Choice means that you have hundreds of options put in front of you and if you would like to be able to use any of these options, then you must find, test, build, etc.

The right to choose means that you are presented with a solution and if you want, you can go outside of this.

I will relate this to symbian... Choice was pre-ovi store. The right to choose was post-ovi store.

I know that there are many people who are passionate about both sides of the issue and would like to better understand. I apologize if my phrasing was too bias and will accept a better revision of either side.

Originally Posted by Fargus

The problem with the option of Choice is that you are limited to the available choices - technically the old school Russian politics was one of choice but you only had a single choice to decide between!

The right to chooe is also any use if there is something out the as a viable option or you have the skills to provide one.

Personally? I'd prefer the right to choose and spend the time required to ensur that the option I want is for me!

Make sense?

Choice means that you have hundreds of options put in front of you and if you would like to be able to use any of these options, then you must find, test, build, etc.

The right to choose means that you are presented with a solution and if you want, you can go outside of this.

Originally Posted by DaveP1

But then again, the problem with the right to choose is that you are limited by what is available to choose. Henry Ford offered you the right to choose a Model T in any color, but the only color Ford sold was black. If you wanted a different color, you could paint it yourself.

The right to choose when there are no choices is not always preferable.

Originally Posted by bocaJ

I guess I'm not understanding the dichotomy, sorry.



For "the right to choose" you say I can "go outside of this" - I understand this as if I don't like the solution I'm presented with, I can write my own app or use apps written by others. In fact, "the right to choose" sound exactly like "choices," plus you get a pre-built option to start with. If I were more of a developer, I'd call it Choices++.

So I'd go with that, but if I'm not understanding things correctly, please let me know.

Originally Posted by Johnx

bocaJ and Cherrypie sum it up pretty well for me. Now having said that, I'll go off on a slight tangent. Somehow the word "consumer" always bothered me. Maybe I'm reading too much into it, but I really feel like it comes with a lot of preconceptions attached. It always seemed like it was weird to classify people as "consumers" when in fact lots of them are contributing to Maemo in some way or another. Or maybe they're just users right now, but in the right circumstances they might get motivated to learn to program, or do a translation, design a UI or even just help others. I can't help but feel like this constant chrous of "consumers this" "consumers that" is selling people short and setting low expectations for them. I really don't know what to call them instead of "consumers" though. I've been thinking about a couple terms, but I think the most catchy one I've come up with is "people." Sorry to be off topic in your thread, matthewcc, especially since I think it's a worthwhile discussion.

-John