Answer the question
In order to leave comments, you need to log in
Layout for Android, how relevant is it?
Good afternoon dear community.
There was such question for developers of programs for Android.
How often does a situation arise when you need the program interface to be already laid out? Those. all resources (graphics, styles, etc.) have been added, and you would already be directly involved in the development of functionality.
Or, to rephrase the question a little, do we need such layout designers who produce a ready-made interface (tested / adjusted) at the output? Or is it a utopia and it is more convenient for programmers to do everything themselves.
ps The question is not idle, it's no secret that the more or less complex interface of the android program requires a lot of time.
Answer the question
In order to leave comments, you need to log in
IMHO, it's completely irrelevant. When developing for android, the programmer has to interact very closely with the UI. Programmer-coder and programmer-programmer? Why produce entities? I believe that any programmer for android is also a coder.
As for me, a more or less average layout designer should be able to do this. And of course, this is the direct responsibility of the layout designer, not the programmer.
ps jQuery Mobile is quite easy to learn.
If on the web I can still concentrate purely on the server side, for example, and leave the layout to other people in the team, then when developing for Android, I can’t imagine how it’s possible to deal with functionality without affecting the interface. Everything is really intertwined here.
It is possible, of course, that someone will make the base layers, then I could devote more time to the functionality. But the question is different.
Even if I do not do layout, the person who will be will not be able to make normal layers without knowing the features of Android.
That is, if under the web it was possible to explicitly separate the vertska into a “pure” layout designer, then under Android it seems to me impossible in principle)
The market for mobile applications is quite good... To say approximately, 3 years will definitely still be relevant.
Layout for Android... Everything is simple here: the whole site with responsive design, fewer cumbersome scripts, mobile browsers tend to read them incorrectly...
Contrary to the opinion of most of the respondents, this task should actually be performed by a separate designer, not a programmer (shameful not to know). He must be aware of all the intended functionality of the application in order to understand which user interface elements to use. And he will naturally arrange them according to his design taste, as well as select the font of the inscriptions, theme colors, etc. beauty. The designer also needs to edit the code (if he has previously scribbled it in the editor) when, for example, there is a drop-down list, and placing elements in it is possible only programmatically. In fact, it only works in the main thread, since the entire UI is processed there (this is in Android, I can’t vouch for others if that). It is written that in the end, the designer forms the TOR for programmers and transfers the project to development. More likely,
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question