At present in the industry, the design specifications for iOS are also uneven, and many of them are still stuck on 6 devices and ios 9 systems, and now the latest ones are iphone 7 and iOS 10 (the replacement is really fast) , I'm talking about the latest iOS interface design specification (Android design specification, we'll see you next time)
I am a UI designer, so what U sister is talking about here is to explain what a designer should do in the process of creating an APP from scratch from the designer's point of view.
If you are in a company with a sound team, when the project is approved, all relevant personnel (product Wang, operation meow, design lion, programmer, etc.) will be gathered together to hold a product meeting, and the product Wang will explain the project prototype, market Research and analysis, market demand, product positioning, profit model and other specific functional modules and jump logic, discuss and exchange prototypes together, improve and b2b data perfect the deficiencies, and then evaluate the project time, and the construction can start.
Note: When explaining the product and demonstrating the prototype, you must listen carefully and fully understand the entire logic. If you have doubts or do not understand, you must ask questions and let the product answer them, otherwise logic may appear in your design draft. error etc.
At this time, we can create a new project and make preliminary preparations.
My personal habit of project filing is to name the folder with "project name + version number" , because this method is very convenient for me to manage and find project files. Some designers may put all the files in one folder. If there are fewer files, it is fine. When there are too many files, you will cry, and you will not know which version of the file is.
Repeated revisions are commonplace for designers. When a page is revised many times (including 2 changes in 3 days), the source files of many designers should look like this:
First draft, First draft 1, First draft 2... Reviewed draft, Reviewed draft 1... Revised draft, Revised draft 1... Final draft, Final draft 1... When I look at source files like mine, I think I'll vomit blood because It's too hard to distinguish, which is the previous version and which is earlier (at this time, you also saw that the designer's work is really hard, and a few days ago, you thought that the designer worked overtime to solve problems and went to heaven. There is no PS in heaven, please click here for details)
In this situation, I just want to recite a poem: Party A has abused me thousands of times, I treat Party A like my first love, and one day I will be Party A and abuse design institutes all over the world.
My personal habit is to name it "file name + date of revision + number of revisions". For example, "Homepage_4.10" is the final version, but on April 12, the product said that the homepage needs to add a notice, then I The file is "Home_4.12", but it has been changed three times before and after, that is, "Home_4.12.3" is clear at a glance, and it is easy to find the file to be modified.
When I set up the project, I just need to explain to the development partners, and they will naturally know which file is the final version.
Here, U-mei seriously reminds you guys, don't delete all the revised drafts, don't delete them, don't delete them (important things have been said 3 times), every revision is in Make revisions on the basis of the copy, because after we have revised a lot of drafts, Party A may say, "The first version is still good, let's go back to the first version" (don't vomit blood or smash the computer), so please make sure that the copy to modify it.