Skip to content

Commit 65ca96d

Browse files
authored
Update rounded_corner.md
1 parent 1cbc628 commit 65ca96d

File tree

1 file changed

+0
-17
lines changed

1 file changed

+0
-17
lines changed
Lines changed: 0 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,3 @@
11
**`False`** For a square finish.
22

33
**`True`** For a finish with rounded corner. To be favored in more emotional, immersive contexts or those tied to specific visual identities. For standard or business-oriented journeys, keep the default corners. This evolution addresses the need for flexibility in adapting the design to certain brand contexts.
4-
5-
### Do & don'ts
6-
7-
**Do:** Use square corners as the default for business-oriented applications and standard enterprise forms.
8-
**Don't:** Apply rounded corners inconsistently across different input fields within the same interface.
9-
10-
**Do:** Consider rounded corners when the overall brand identity uses soft, approachable visual language.
11-
**Don't:** Mix square and rounded corners on the same page unless they serve distinct semantic purposes.
12-
13-
**Do:** Match the corner radius of text inputs with other interactive elements (buttons, cards) in the same context.
14-
**Don't:** Use extremely large corner radii that distort the input proportions or reduce usable input area.
15-
16-
**Do:** Apply rounded corners for consumer-facing, lifestyle, or entertainment products where warmth is desired.
17-
**Don't:** Override established brand guidelines just for aesthetic preference—align with the design system.
18-
19-
**Do:** Ensure the corner style choice is documented and applied systematically through design tokens.
20-
**Don't:** Hardcode corner values individually—use design tokens to maintain consistency and enable theming.

0 commit comments

Comments
 (0)