Before drawing a new icon
Before drawing an icon, establish its meaning, label, family and behavior at the actual display size. Reuse familiar concepts where they fit.
Write down the intended meaning
Describe what the icon should communicate before choosing a shape. Navigation, deletion and changing a selected value create different expectations. Also distinguish decoration from information.
A star used for both favorites and recommendations can be ambiguous about meaning and interactivity. Review the concepts already represented in the interface and keep a consistent meaning for repeated shapes.
Do not assume a new concept is understandable without text. A short visible label may be the clearest solution. The purpose of an icon is to help people find information and actions, not simply to eliminate words.
Check the existing family and usage terms
An individually polished icon can still clash with nearby stroke widths, corners and fill styles. Search the existing family for the intended meaning and compare visual weight at the same display size.
For shared libraries or external assets, check the source, usage terms and version. Downloadability does not establish permission for every modification or redistribution. Use the terms attached to the actual asset.
If a custom drawing is needed, record the missing capability: a brand-specific expression or a domain concept the current family cannot convey. Give it a clear name to prevent several near-identical representations of the same idea.
Separate the drawing from its interactive area
A small drawing does not require a small interactive area. Provide a usable target and clear separation from nearby actions, especially when accidental activation has different consequences.
An icon-only button needs an accessible name describing its action. If a tooltip is present, check how touch and keyboard users obtain the same information. Decorative icons beside text should not unnecessarily repeat that text to assistive technology.
Directional arrows and brand marks should not be mirrored indiscriminately. Define which shapes depend on reading direction or context, then check them in the translated interface.
Review actual sizes and state combinations
Inspect icons at their actual display size in menus, buttons and lists. Include light and dark themes, selection and disabled states, and long adjacent text. Fine details that look good enlarged may disappear at normal size.
Ask reviewers what action they expect before revealing the intended label. Repeated disagreement may call for visible text or another representation rather than a minor drawing adjustment.
Retain the name, purpose, source location, supported sizes and examples. Update other representations of the same action so people can continue using the meaning they have already learned.
Другие статьи
Все статьи-
운영 기능을 권한으로 나눌 때 먼저 정할 것
운영 화면을 함께 쓰더라도 데이터 접근은 분명하게 나눠야 합니다. 역할, 작업, 데이터 범위, 승인과 기록을 기준으로 권한을 설계하고 서버에서 검증하는 방법입니다.
-
Define permissions before combining admin workflows
A shared interface still needs explicit authorization. Define roles, actions, data scope and audit requirements, then enforce them on the server.
-
AI가 만든 기능을 검증하는 코코드의 방법
코드가 완성된 뒤에는 약속한 동작이 실제로 이어지는지 확인해야 합니다. 코코드는 단위 테스트로 개별 규칙을, BDD 통합테스트로 사용자 흐름을 검증하고, 변경 후에도 다시 확인할 수 있는 기준을 남깁니다.
О том, как мы работаем, и об условиях можно прочитать на странице вакансий.
Все вакансии