User Profile

User profile and account management

What it solves

User Profile is the interface that displays a user's identity, activity, and public or personal information. Profiles serve as both an identity card (how others see the user) and a self-management tool (how the user views and edits their own data). A well-designed profile balances information density with visual clarity, supports both viewing and editing modes, and respects privacy by giving users control over what information is visible to others.

When to use

Use User Profile to display and manage user identity, activity, and personal information. Common scenarios include:

• Displaying a user's public profile on community or social platforms
• Showing the authenticated user's own profile with edit capabilities
• Team member profiles in collaboration tools
• Author profiles on content platforms (blogs, documentation)
• Contributor profiles on open-source or marketplace platforms

When to avoid

• Account security settings (use Account Settings)
• Application-level configuration unrelated to the user (use app settings)
• Contact cards in a directory where interaction isn't needed (use a simple card component)
• User management admin panels (use a data table or admin interface)

Implementation workflow

1. Confirm the pattern matches the problem and constraints before copying the example.
2. Start from the anatomy and examples in references/pattern.md, then choose the smallest viable variation.
3. Apply accessibility, performance, and interaction guardrails before layering visual polish.
4. Use the testing guidance to verify behavior across keyboard, screen reader, responsive, and failure scenarios.

Accessibility guardrails

Do's ✅

• Use alt text on avatar images that includes the user's name
• Use proper heading hierarchy (h1 for name, h2 for sections)
• Make all action buttons keyboard accessible with visible focus indicators
• Use <time> elements with datetime attributes for dates
• Ensure the edit mode provides clear form labels Don'ts ❌
• Don't use the avatar as the sole identifier — always include the text name
• Don't make profile stats interactive (clickable) without clear affordance
• Don't auto-play media on profile pages

Performance guardrails

Target Metrics

• Profile page load: < 500ms with avatar and content
• Avatar image: < 100KB optimized (serve multiple sizes)
• Edit mode toggle: < 50ms response
• Activity feed: Lazy-load items beyond the first 10
• Avatar upload: < 2s for upload + processing + preview

Optimization Strategies

Responsive Avatar Sizes

<img
  src="/avatars/jane-96.jpg"
  srcset="/avatars/jane-192.jpg 2x"
  alt="Jane Doe"
  width="96"
  height="96"
  loading="eager"
/>

Common mistakes

No Default Avatar

The Problem: Users without a profile picture see a broken image or empty space, making the profile look broken.

How to Fix It: Show a fallback: initials-based avatar (first and last initials with a background color) or a generic silhouette icon.

No Empty State for New Profiles

The Problem: A new user's profile page shows blank sections with no guidance on what to add.

How to Fix It: Show prompts for empty fields: "Add a bio to introduce yourself", "Upload a profile picture". These disappear once the user fills in the data.

Edit Mode That Reloads the Page

The Problem: Clicking "Edit profile" navigates to a separate page, losing the user's context and requiring a page load.

How to Fix It: Use inline editing (click to edit fields in place) or a modal overlay. Keep the edit experience on the same page as the view.

Related patterns

• https://uxpatterns.dev/patterns/authentication/account-settings
• https://uxpatterns.dev/patterns/authentication/login
• https://uxpatterns.dev/patterns/authentication/signup

---

For full implementation detail, examples, and testing notes, see references/pattern.md.

Pattern page: https://uxpatterns.dev/patterns/authentication/user-profile