For any design requirement we can get “Product requirement document”, which has all the use cases and edge cases of the product which is made by either Project/Product manger or Designer

Process

1. You finish all feedback rounds with Product manager
2. You have a canvas of lot of UIs
3. You cherrypick the final screens
4. Creat a new page/file for Dev
5. Devs develop and come back for Review
6. Designers confirm pixel perfection
7. Developers send product to QA (Quality Assurance)

When you start out, you first

1. One project just for Design System-

• Universal Guidelines - Brand colors, icons, copy directions shadow, border radii, typefaces, etc

1. iOS, Android and Web each will have its own library
2. Colours can be universal
3. Typography, Iconography and Images change
4. Decide how many devices you cater
5. Each category can have GTM and WIP
6. Each Project will have individual files
7. Each File for a specific launch

• Libraries need to be enabled accordingly
• Maintain covers for all
• File name matters a lot

How to name different projects

While designing File Covers..

• 1500px x 960 is a safe area
• Priorities simplicity and legibility
• Have a template that scales well
• Have tags for statuses
• Experiment with BG Fills
• Avoid having too many variations
• Always best to have Designer’s Face
• Startup Example
• Company Example

Quick tips

• Header frames that are simple
• Hyperlink Title to the PRD
• Vertical for Use Case, Horizontal for Flow
• Dashes/Underscores instead of spaces
• Practice naming layers
• Only instances, no detached stuff
• No colours without styles in Selection
• When doing Design Review, use Inspect