Hi Mark, UX will be standing by whenever you need us.
My understanding of this split is that instead of UX reviewing each little change (e.g. "How's this one button look? Good? Okay, now how about this dropdown now?") a chunk of work gets done and then UX is pinged with a "How does this entire panel look?" at which point we give a bunch of changes and work closely on the visuals. This should streamline the "look" stuff, but feel free to hit us up anytime regarding flow, or even small design stuff if you feel they are sticking points to continuing. Hope this clarifies a little, Sevaan ----- Original Message ----- From: "Mark Banner" <[email protected]> To: "Dan Mosedale" <[email protected]>, [email protected] Cc: "Sevaan Franks" <[email protected]> Sent: Monday, July 28, 2014 4:33:09 AM Subject: Re: splitting off Loop visual design landing from feature work On 24/07/2014 02:27, Dan Mosedale wrote: > ux-review won't be required on the incremental (non-visually-styled) > bugs, the ux-review will happen in one coherent piece, when the visual > design uplift lands as a whole. Isn't ux-review also meant to cover the particular interactions and flow, not just the layout? This would indicate to me, that we'd still need some ux-review in the majority of cases. Mark. _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
