Charley, This is pretty cool feedback and I actually used your email response in my session. The 5 participants (all from Nokia ;)) really liked the idea of rejecting an interface. Anyhoo I am shortly updating the wiki page with your instrumental feedback.
Will you be interested in helping the coding side as well? I'd reckon we need to start with defining a schema on CouchDB and throwing an Django frontend for registration and authentication to the service. Thanks!! -Sivan On Thu, Jun 16, 2011 at 7:03 PM, Charley Bay <charleyb...@gmail.com> wrote: > Sivan spaketh: >> >> <snip, CrowdQuick> >> Here's the braindump and a basis for the spec: >> >> http://developer.qt.nokia.com/groups/qt_contributors_summit/wiki/CrowdQuick > > >> >> <snip>, >> Let's start tossing more ideas at this, and ofcourse your feedback is >> highly regarded and appreciated. <snip> > > This is a *really* clever idea. Netflix should have had this before they > rolled out their "new and improved" interface. > > It would be nice to see a "star count" rating scale, or a "count up/count > down" display on parts of the interface (e.g., widgets or collections of > widgets). Clicking on the "star count" would transluscent-highlight the > parts of the interface the user is now rating (like just a "calendar > widget", or the whole "input dialog"), and the user simply presses "Up" or > "Down". > > That's a two-press rating, but I think it's needed to (1) avoid accidental > hits (a second press is needed to confirm), and (2) enable the user to "see" > what is *actually* being rated (the translucent highlight covers the area > being "rated", and this rating operation is "modal": Rate up, down, do > nothing. > > Of course, to avoid re-votes, we'd also need to "remember" if the user > already voted. So, based on current login/session/user-id/something, the > "vote" list is one of: > > *- Already voted up (Un-do now) > *- Vote Up Now > *- Vote Down Now > *- Already Voted Down (Un-do now) > *- Dismiss/Do nothing > > With a clever visual interface, all these states should be shown to the > user, and these should collapse to a rather small set of pixels: > > [I LIKE THIS] (Vote up now, un-do down vote) > [DO NOTHING] (dismiss) > [NOT LIKE] (Vote down now, un-do up vote) > > If you *really* want to go nuts (in an ambitious way): > > *- a "down vote" would immediately cause the user interface to "revert" to > the previous version, or the previous "highest rated" version, or the > previous "liked" version for the current user > > *- user interfaces would be dynamically assembled for a given user based on > that user's "preferences" for components. > > For example, it may be reasonable to have *multiple* "Calendar/Date-Input" > widgets, and the user always sees his/her "preferred" input widget. > > This CrowdQuick idea is really very clever, IMHO. > > --charley > _______________________________________________ MeeGo-community mailing list MeeGo-community@meego.com http://lists.meego.com/listinfo/meego-community http://wiki.meego.com/Mailing_list_guidelines
