DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Coding
  3. Languages
  4. The Pull-to-Refresh Gesture Needs to Die

The Pull-to-Refresh Gesture Needs to Die

Alec Noller user avatar by
Alec Noller
·
Jan. 05, 14 · Interview
Like (0)
Save
Tweet
Share
7.51K Views

Join the DZone community and get the full member experience.

Join For Free

Strong words, given that we're talking about a gesture. But that's the core idea of this recent article from Co.Design - pull-to-refresh has to go. The author, Austin Carr, argues that pull-to-refresh is an out of date design, no longer relevant in today's mobile ecosystem. "A relic of a bygone era," he says. More specifically, the problem is that pull-to-refresh is an unnecessary step in a world where things should probably just refresh on their own, and hanging on to this manual choice just takes away a design choice that is simple and intuitive and potentially useful for something else.

Carr does provide some counterexamples - Twitter's use of pull-to-refresh as a tool to allow user's to return to the same place in the Twitter feed before refreshing, for example. Overall, though, it's an interesting point when it comes to mobile design, and pull-to-refresh likely isn't the only design choice that is still being implemented just because people are used to it. 

Check out the full article and see what you think. How does one innovate in something like mobile design when so much of good design relies, for example, on control schemes that users find to be intuitive?

I guess killing pull-to-refresh is a start, though.

Design choice Design Die (manufacturing) mobile app Scheme (programming language) IT

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Load Balancing Pattern
  • The Quest for REST
  • The Future of Cloud Engineering Evolves
  • Better Performance and Security by Monitoring Logs, Metrics, and More

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: