The UI designer organizes the visible and interactable surface of the digital product. When hiring a freelance UI designer, just discussing how many screens will be drawn would be incomplete. The state of the button, the form error, and the behavior of long text are also part of the interface. The success of the design should be evaluated in terms of how clearly the developer can understand real product situations.
A screen has different states
A product listing may be full, empty, loading, or incorrect. Depending on the user's authority, some transactions may not appear. If there is only the ideal screen in the design file, someone else makes these decisions during development. Preparing the screen inventory with the situations reduces later uncertainties.
Determine the use of components, not just their name
Two buttons that look the same can be used for different purposes. The visual distinction between primary action, secondary action, and destructive action must be consistent. It should be explained when the component is used and how it behaves when the text inside it is extended. A giant design system may not be necessary for a small project; Order as needed is sufficient.
Only size does not shrink on mobile
Adjacent areas on the desktop may line up differently on the narrow screen. Menus, tables, and filters may require other interactions. Which screen widths will be considered and which elements will change behavior should be written in the proposal. Don't count auto-minimizing a desktop sketch as a mobile design submission.
Test developer handover with an example flow
Review a set of screens with the developer before approval. Navigation, error message, and focus order should be discussed as well as color and size. UI design alone is not a substitute for usability research or working code. If these responsibilities are defined separately, the project will proceed more clearly.
You can compare the required deliverables from UI/UX design service and design system delivery.
Frequently asked questions
Is it enough to only take home screens in UI design delivery?
In addition to the main screens, loading, empty content, error, success and authorization statuses should also be defined. If the developer sees only the ideal screen, he has to guess the design of other cases during implementation.
Why is minimizing the desktop screen not enough for mobile adaptation?
In a narrow space, the order of information, navigation, and interaction may vary. For a table, menu or form, the use on the small screen should be designed separately; should be controlled with long content and touch areas.
