2 Jun
Ryan Singer: UI design on Rails
How to break down the wall that has always divided developers and designers? Ryan Singer has the solution.
There exists a wall between the design and the development, in reality this is unveracious perception deriving from the wrong assumption that the designer must create the graphics for an application. The designer must have a profound understanding of the product and be able to in theory shape and describe it.
The suit that Ryan foresees is that the designer can, positively must operate at modifying the structure and the functionality of the application. The designer must also require the base knowledge of code that the application has been written in.
To give the designer other than the knowledge that he needs, an incremental learning approach, from this verge of view the discussion simplifies in how much the designer in reality already know very simple programming languages (HTML, CSS…) from that they can derive the base concept of which is needed.
The first step is to have the understanding of the views, therefore the controllers and in the cessation the models (but this is not essential for the work of a designer).
If they can get to this equal elevation of mutual agreement it opens up another channel where the designer and the developer have power to communicate. In an ideal vision the designer is responsible for the sake of the views while the developer concentrates on the models and the controllers.
Ryan is know presenting a scrap of a controller from basecamp that he uses as an example to show the cooperation at the code level between the designer and the developer that is the only habitual method to have satisfactory results.
Ryan concludes explaining how the designer be able to benefit from some science utilized from the developer. Like for example REST through which it is possible to define a base design to interview a resource.
Annalisa
