[FlashCodersNY] Catalyst Question from last night

[Hudson Ansley]

or

1) multiple "designers" (throw some marketers and execs in there) come
up with many different skins and required options
2) intrepid developer builds system to handle everything, with a UI
settings tool ( very rough, it will be made smoother later ;-)
3) most of the features never get used

yeah, I think the catalyst work flow has potential...

Regards,
Hudson

On Tue, Jun 16, 2009 at 3:44 PM, James
O'Reilly<james.oreilly at synergymedia.net> wrote:
> I find skinning to be a backwards workflow that severely limits creativity.
>
> Think about it.  With skinning, you end up with a developer who designs a
> user interface that meets the functional requirements of the software.  Then
> the designer gets the project and tries to apply design to it.  This usually
> ends up being little more than font choices, background colors and button
> rollovers.
>
> Skinning method: "Build it first, we'll see what it is we're going to design
> and we'll make it look nice."
> 1. Developer Mocks UI
> 2. Developer Writes Business Logic
> 3. Designer Skins UI
> 4. Developer Implements Skin
>
> To me, I think it makes more sense for a UI or UX specialist to design the
> software first then hand off a completed and working UI to a developer to
> finish.  The fact that Catalyst doesn't allow a designer to write even one
> line of code or edit the MXML makes it even better to me.
>
> Sensible method: "Design something kickass that we haven't seen before and
> we'll make it happen."
> 1. Designer Builds UI
> 2. Developer Writes Business Logic
>
> I'm hoping Catalyst lives up to the hype.  As both a designer and a
> developer I see how it could make my life easier even when it's only me who
> has to do both sides of the puzzle.
>
> JOR
>
>
>