---
title: "Pull to refresh"
created: "2026-07-02"
updated: "2026-07-02"
type: "concept"
status: "compiled"
category: "ui-patterns"
namespace: "ui-patterns"
source_url: "https://ui-patterns.com/patterns/pull-to-refresh"
source_site: "UI Patterns"
source_copyright_note: "Source site footer says All rights reserved; this page is a catalog pointer, not a republication."
source_path: "/patterns/pull-to-refresh"
source_slug: "pull-to-refresh"
track: "User Interface Design Patterns"
group: "Navigation"
subgroup: "Gestures"
section_headings:
  - "Problem summary"
  - "Example"
  - "Usage"
  - "Solution"
  - "Immediate visual feedback after the action"
  - "Refresh indicator should only be triggered by user action"
  - "Meaningful state transitions"
  - "Rationale"
  - "Why should we use pull to refresh?"
  - "Discussion"
  - "Visible “refresh” button vs Hidden pull-to-refresh gesture"
  - "When you should use visible “Refresh” button or auto-update instead of Pull-to-refresh"
  - "Thumb-reach issue on iPad"
  - "Augmented Pull-to-refresh"
example_count: 11
retrieved_at: "2026-07-02T18:23:09+00:00"
confidence: "medium"
---
# Pull to refresh

> Catalog pointer for the UI Patterns source page: [Pull to refresh](https://ui-patterns.com/patterns/pull-to-refresh).

## Taxonomy

- Track: User Interface Design Patterns
- Group: Navigation
- Subgroup: Gestures
- Source breadcrumb: Design Patterns > Navigation > Gestures > Pull to refresh

## Source Page Inventory

- Source URL: https://ui-patterns.com/patterns/pull-to-refresh
- Page title: Pull to refresh design pattern
- Section headings available at source: Problem summary, Example, Usage, Solution, Immediate visual feedback after the action, Refresh indicator should only be triggered by user action, Meaningful state transitions, Rationale, Why should we use pull to refresh?, Discussion, Visible “refresh” button vs Hidden pull-to-refresh gesture, When you should use visible “Refresh” button or auto-update instead of Pull-to-refresh, Thumb-reach issue on iPad, Augmented Pull-to-refresh
- Example screenshots detected at source: 11
- Primary example image detected: yes

## Retrieval Notes

Use this page as a routing handle, then open the source URL when you need the full pattern explanation, screenshot examples, or exact wording. For public Pixi Wiki use, prefer paraphrased design implications over long source quotes.

Useful retrieval frame:

- Ask what user behavior or interface decision this pattern is meant to shape.
- Check the source page sections before prescribing it; many pages distinguish usage, solution, rationale, and examples.
- Compare nearby patterns in the same subgroup before choosing one.
- Cite this catalog page plus the source URL when using the pattern in design review.

## Source Shape

- Problem summary: 16 words on source page
- Example: 86 words on source page
- Usage: 63 words on source page
- Solution: 231 words on source page
- Immediate visual feedback after the action: 80 words on source page
- Refresh indicator should only be triggered by user action: 42 words on source page
- Meaningful state transitions: 47 words on source page
- Rationale: 263 words on source page
- Why should we use pull to refresh?: 256 words on source page
- Discussion: 561 words on source page
- Visible “refresh” button vs Hidden pull-to-refresh gesture: 75 words on source page
- When you should use visible “Refresh” button or auto-update instead of Pull-to-refresh: 199 words on source page
- Thumb-reach issue on iPad: 56 words on source page
- Augmented Pull-to-refresh: 121 words on source page

## Source Navigation

- Previous source navigation: Friend
- Next source navigation: Rule Builder