Answer the question
In order to leave comments, you need to log in
App design integration on iPhone?
I can’t sort out the process of design integration in my head.
The designer produces graphic images of screens as a result of his work.
1. In what form should the designer give the result?
2. What can a programmer (without fanaticism) and not be able to do from the design made? To somehow limit the flight of the designer's fantasy. Where and what is the border?
As I understand it, what we have in the integration process:
1. If the designer "draws" a standard UI element, then you set it in the application according to the designer's size and position.
2. If something is not standard, then you "cut" and set the "picture" on the interface and program the click on this element, if necessary.
3. Non-standard UI element, for example, an input field or a button. Elements provide for interactive user interaction and various states (disabled/enabled). How is it here?
Answer the question
In order to leave comments, you need to log in
There is a standard UI and basic element sizes for two types of screen (retina and normal).
The designer must either take the standard ones or draw his own. It is only important to remember that the size of some controls (tabs, navigation) cannot be changed, only skins. You can use transparency in png.
You need to draw both resolutions - retina and normal.
According to point 3. All states are drawn separately, preferably with text comments. For example "we click on the address field with the mouse and the field for the index appears. Figure1."
The main thing to remember is that the developer mainly works with vector concepts - views, controls, etc. If your design is not beating on these elements, then you need to change something.
In general, if you are interested in how to work with a designer, I can tell you in personal correspondence :)
1. The designer must give the result in one and only version :) These are cut elements in png and views with markup in points.
2. There is no border))) A good designer must know the capabilities of the system and predetermine what the programmer can do. This is always discussed beforehand. Well, you can bring to life almost everything that was conceived by the designer, it depends on which programmer comes across.
1. As usual, there are few standard elements in good applications, and it is more convenient to take png for work.
2. The designer should always cut the elements, if he does not do this, then send him to hell. He's just a lazy guy
3. Naturally, the designer must draw two or even 3 states for the element.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question