Top

Code: Front-End Development

UXmatters has published 11 articles on the topic Front-End Development.

Top 3 Trending Articles on Front-End Development

  1. Speaking Up for Conversation Design

    October 21, 2019

    Voice-first user experiences are now ubiquitous. Smart-speaker sales are up, as is their usage. Older adults are benefiting from the use of voice assistants. However, a large percentage of users still find the experience of talking to voice assistants unnatural. So how can we make voice experiences better?

    While understanding conversation design–best practices is necessary, it’s not enough to make these conversations feel natural. To take your voice user interface (VUI) to the next level, you must add polish—in the form of pacing, sound effects, and diverse phrasings. Let’s take a look at each of these in turn. Read More

  2. UX Design Defined

    June 18, 2012

    Unfortunately, in the field of user experience, people often confuse terms like information architecture, interaction design, visual design, usability engineering, and UX design. In some cases, people use these terms almost interchangeably. This article provides a lexicon of these terms and more clearly defines the role of the user experience designer.

    Information Architecture

    Information architecture (IA) focuses on the organization of data—that is, how data is structured from a user’s perspective, as opposed to the system, or technical, perspective.

    At the level of an entire Web site, or application, information architecture determines what data is on each page and how pages relate to each other. For example, defining a site map is an IA activity. At the level of an individual page layout, information architecture ensures that data is logically grouped and interrelated. Read More

  3. From Wireframes to Code, Part I

    December 20, 2010

    Within many companies, the use of wireframes in user experience design can be a contentious issue. People typically think of wireframes simply as artifacts designers create when generating design concepts, then later discard. Why not create a design artifact that is not disposable, but instead, one your team can convert to actual production code? Is this Holy Grail of the design process a good idea? Is it even possible? Or does the answer depend on the project, the team, and its agility? This first part in a two-part series takes an in-depth look at the process of converting wireframes to code. Read More

Champion Advertisement
Continue Reading…

Columns on Front-End Development

New on UXmatters