UI UX design agency in Atlanta

For a live product, an incremental redesign lets you change screens gradually when users are likely to resist a sudden shift. A full redesign suits a product whose underlying structure no longer fits how people use it. The choice affects how much existing structure you keep and how much you reconsider.

For an early product, use low-detail wireframes to settle the structure. A clickable prototype is useful when you need people to try a flow or investors to see it before code is written. An established UI kit or open-source component library can speed up the early work; a custom visual language suits a product where the interface is part of what customers pay for.

Your development arrangements affect the choice too. Design-only work suits you if you already have developers; design and build from one team gives you a single party responsible for the finished product. A small component library is often enough for an early product or marketing site, while a full design system suits more screens or several teams.

For a business open to the public, US Department of Justice guidance says ADA Title III covers goods and services offered on the web and points to WCAG as helpful guidance. We design with readable text, colour contrast, visible focus states, clear labels and tap targets large enough to use.

For state and local government websites and mobile apps, the Department’s rule requires WCAG 2.1 Level AA. We review the relevant page and app designs against those criteria and document the interaction details needed for development.

Bring what you have to make the first discussion specific.

• List your main user types and their tasks. Mark the tasks that bring revenue or generate support calls.
• Gather your logo, fonts, colours, brand guidelines and any existing design files.
• Ask your developers for the front-end framework, existing component library and current back-end limits.
• Note products your users already know, including what works and what annoys them.
• Identify customers or staff willing to try a prototype and explain what confuses them.

• !

  Polishing too early

  Agree the flows before investing in visual design, so attractive screens do not need restructuring later.

• !

  Making forms hard to use

  Avoid low-contrast text, small tap targets and fields labelled only by placeholder text. Check labels and controls on a phone.

• !

  Leaving after handover

  Keep the designer available for development questions so the team does not have to guess at intended interactions and let the built product drift from the design.