UI UX design agency in Philadelphia

For a live product, an incremental redesign lets existing users adjust as screens change. A full redesign is a better fit when the structure no longer reflects how people use the product, though it calls for a broader look at the screens and tasks that fit together. Decide how much change the current structure needs before choosing a visual direction.

For an early product or marketing site, a small component library keeps the design work contained. A full design system suits a product with many screens or several teams. An established UI kit or open-source component library also helps an early product move faster; a custom visual language suits a brand whose interface is part of what customers pay for.

Start with low-detail wireframes when you need to settle the structure. Choose a clickable prototype when you need people to try a flow or when you want to show an idea to investors before writing code.

For businesses open to the public, US Department of Justice guidance says the ADA covers goods and services offered on the web and identifies WCAG as helpful guidance. We set up readable text sizes, colour contrast, visible focus states, clear labels and tap targets in the design. These give your developers specific interface details to work from.

For state and local government websites and apps, the applicable rule requires WCAG 2.1 Level AA. We use that requirement to guide the accessibility work specified for those screens.

Bring the material you already have so we can discuss the work in concrete terms.

• Your main user types and their tasks, marking those that bring revenue or prompt support calls.
• Analytics, session recordings, support tickets or sales call notes that show where people get stuck.
• Brand guidelines, logo files, fonts, colours and any existing design files.
• Products your users already know, with notes on what works and what annoys them.
• Customers or staff willing to try a prototype and describe what confuses them.

• !

  Polishing screens too early

  Agree the flows before visual design, so an attractive screen does not need its structure redone.

• !

  Designing only the ideal path

  Include errors and empty states in the design instead of leaving developers to improvise them during the build.

• !

  Settling debates by opinion

  Put the prototype in front of real users and use what you observe to make the decision.

• !

  Making forms hard to use

  Avoid low-contrast text, small tap targets and fields labelled only by placeholder text.