Figure out aims (already started), project initial user base, get UI people on board, don't be limited by gwt, look into methods of hooking up interfaces, schematics, schematics, mockups, etc.
*more detail* Wave is kind of user centric at the moment. I know it sounds contradictory making a user interface other than user centric. But it isn't about making it less user friendly, on the contrary, more bout striking the balance between task and the users (which obviously are an important part of getting the task done). I created a schematic for an interface that was more task centric, and it was actually like a walk-through experience (wave agnostic). It is too specific for WAIB, but the general idea that social media for the sake of social media, whilst good for reaping personal information, is ultimately not uniquely useful to the users other than status reasons, whereas things like wave are about getting things done and communicating ideas collaboratively. Obviously there are other synonyms for "task" but you get the idea. I think architecture that reflects the aim to collaborate on something makes sense. I know I said this before, but I'll say it again. “Conversation” is just a default communication. It is one type of collaborative communication amongst many possibilities. Granted it will be a popular one that would be used along side app doc and other things. However it would be good in the long term to build all models and their interfaces with api for that. -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
