When we are develop application, we may receive lots of Mock Up screen from the Design team or we will create them to help us design the program;
In this article, I will talk about what are the things or information we could discover from the Mock Up screen that helping us to develop our programs;
- Built in component: The building block provided by the SDK; For example, button, label, etc;
- Custom component: A component built by yourself; For example the sub view displaying tweet in the Tweet Feed view;
- Third party component: Similar to the custom component, but built by others; For example, CircularImageView, an ImageView displaying image with a circle mask;
- Using a Table
- Using a Scroll view (vertical or horizontal)
- Using Tabs
- Using Grids
- When an user enter password in the text box, warning is shown when he typed too many characters;
- When an user press “LOGIN” button, a progress indicator will show up and wait for server response;
- When the LOGIN response is just received from server, bring the user to the main screen;
- The data which is displayed by the UI;
- The data which is used internally;
- How to get those data and How is the data be produced or calculated?
- What are the API will be used by the UI?
- Which UI will be switch to and when will this happen?
When we received a requirement specification, we are hard to dig out the detail from the bullet points list of requirements; However, when we have the Mock Up, we can dig out more detail about what are things to be done in the Front-end (User Interface) or Backend (Server API);
So before you start coding, take a look and take some note from your Mock Up screens;