CODEWITHSUNDEEP
androidresttimeouthttpclientsettimeout
eduyayo
eduyayo

Reputation: 2038

What timeout value should I set to avoid problems in a REST based Android application?

It may sound stupid but. I've set the timeout to 5 seconds and testing with a 3g connection it seems to be too little when in my experience it really sounds like an eternty.

What's a common use value for users not to desperate and keep the things together?

Upvotes: 0

Views: 384

Answers (2)

Stephen Punwasi
Stephen Punwasi

Reputation: 476

Doesn't sound stupid, but it depends on the interaction between your app and the server. Unlike a router based timeout, some routers begin their calculation when they begin to do the work (Heroku comes to mind). In this case, anything under 30 seconds is good.

Upvotes: 1

ivan.sim
ivan.sim

Reputation: 9298

There are really no special, commonly used values for something like timeouts. A value that works for one user may not work for the other. The important thing from a UX perspective is, when the timeout does occur, the user is informed of:

  1. A timeout has occurred.
  2. The next appropriate action to recover from it, such as, restart the app, wait a while, contact support etc.

via unambiguous error message.

Upvotes: 1

Related Questions