Digital product design does not only consist of the appearance of the screens. It is necessary to clarify together what work the user will complete, what the product team will develop, and what will go into the first release.
Frequently asked questions
Can the same designer create the brand and product interface for a startup?
Brand identity and interface can be prepared with the same design approach; yet these are separate areas of delivery and decision. As Selçuk Aker, I handle visual identity together with the web or mobile product. It is necessary to separately determine those responsible for product strategy, software development and customer acquisition operations; a single design contract does not automatically cover all of these.
Which screens should be prepared first in MVP design?
First, the target user's basic business and success criteria must be determined. Then the shortest flow that completes this job is designed; for example registration, product selection and payment. It is possible to reserve rare usage scenarios for the next release. Instead of making the number of screens the starting point, we check the missing steps of the flow, error and empty states together.
What deliverables are required from the UI designer and the UX designer?
Within the scope of UX, user needs, information structure, flows and wireframe studies can be planned. Within the scope of UI, visual screens, components, typography and states are defined. Research or usability testing is not the default in every package; Determine the method, participants and deliverables separately at the proposal stage.
What to look for when renewing the e-commerce interface?
Category finding, product comparison, basket and payment flow are examined together. Mobile usage, firmware hierarchy and error messages are also part of the design. It is not right to predict whether the new interface will increase sales; Goals should be determined with existing data, and the impact of the change should be measured after publication.
Why is a design system needed in the SaaS administration panel?
Tables, filters, forms, and status messages repeat on different screens. Common components and usage rules make these screens consistent; Reduces decision repetition when designing new features. The authorities of different roles such as administrator and end user should also be included in the interface scope. A design system is not the same deliverable as a developed code library.
How should the Figma design be delivered to the developer?
Along with the screens, there should be component states, different screen sizes, interaction notes and necessary assets. The prototype provides an understanding of the flow; It does not replace production code. Planning an evaluation step for the developer's questions helps resolve behavior that is not obvious in the drawing before coding begins.