Mocks of the application

[ArfatSalman]

Use this issue to collect the mocks of various screens.

It's a good idea to collect the mocks within the context of a user stories. For example,

• How many number of distinct pages do you have?
• What are the user actions?
• In how many steps does he / she achieve it? What action items have to clicked?
• What screens they have to go through?

You can use tools like Figma (recommended) or other wire-framing tools like Balsamiq.

Ensure that you also know at least these things (you can always list more things)

• Application Layout Structure
• CSS / React Layout Library
• Icon Sets
• Color Scheme
• Theme

Feel free to consult older projects listed in the Little Tags Notion page.

If you have questions, comment on this issue.

[nitinmadelyn]

Total number of distinct pages are 10.

User actions:

1. signup
2. login
3. add to cart
4. checkout
5. payment
6. profile update
7. address update
8. change password

Here's the home page mock we have created: https://www.figma.com/file/2D2BRZS1FOC83O1XuTzBc7/Little-Tags?node-id=1%3A3

[nitinmadelyn]

Is it ok to design html/css directly without creating mocks?

[ArfatSalman]

Is it ok to design html/css directly without creating mocks?

Just for FYI, generally the answer is no. If you prototype using HTML/CSS, you can then copy paste bad code in the production when you are implementing the actual feature.