Terminology for Infrastructure/Secondary interaction?
17 May 2006 - 1:45pm
Is anyone aware of a particular terminology being used to distinguish common interaction/UI items from application-specific ones? Examples include a progress message on long processes, or a confirmation page to prevent double-submits. They are common to many apps but increasingly important in UX. I don't think the term "patterns" quite addresses the distinction, but maybe others feel differently.