DZone
Java Zone
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
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Java Zone > Pull-to-Refresh, or Not?

Pull-to-Refresh, or Not?

Juhani Lehtimaki user avatar by
Juhani Lehtimaki
·
Apr. 03, 12 · Java Zone · Interview
Like (0)
Save
Tweet
4.24K Views

Join the DZone community and get the full member experience.

Join For Free

Cyril Mottier from the GreenDroid fame wrote an insightful and thought provoking article about pull-to-refresh on Android. Read the full article here: “Pull-to-refresh”: an anti UI pattern on Android.

Cyril brings up a lot of good points and they are very much worth considering when building apps. On the other hand I personally don't completely agree with all of his points. The post has triggered an interesting discussion over at Google+. My comment in the discussion thread bellow. Head to G+ for your contribution to the discussion about pull-to-refresh on Android.

My comment after the jump...
Juhani Lehtimäki  -  Nice article but I'm one of those people you referred in the conclusion and I completely disagree :)

While you have good points I don't think they all aren't that meaningful and I'd like to present some counter arguments to your points.

You say that the gesture is invisible. While it is true that it is invisible I do thing it is very easily discoverable on lists that shoe newest information on top. The natural way to see if there's more is to try to scroll more which will automatically expose the user to the functionality. There's no need to be a techie. Also, the Android's way of showing list end doesn't have relevance, in my opinion, with pull-to-refresh. Even on iOS the pull to refresh is not associated with the bounce. You are pulling an extra element to view.

By far the biggest thing I have to be on use of pull-to-refresh side is the same reason I strongly advocate use of swiping gesture for moving between tabs. Pull-to-refresh is an action that can be performed in any place of the UI. It does not require reaching for an icon in action bar.

I also don't think that having to be on top of the list is a downside. When tapping refresh you need to scroll up anyways to see the new items (apps should not behave like G+ app that springs you to the top when there are new items).

Android (robot) app Icon (programming language) POST (HTTP) Element

Published at DZone with permission of Juhani Lehtimaki, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • An Overview of Key Components of a Data Pipeline
  • What Is Cloud-Native Architecture?
  • Challenges to Designing Data Pipelines at Scale
  • Implementing RBAC Configuration for Kubernetes Applications

Comments

Java Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • 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:

DZone.com is powered by 

AnswerHub logo