codotxp / foursquared

Automatically exported from code.google.com/p/foursquared
Apache License 2.0
0 stars 0 forks source link

Improve the user experience for connection probs - add "try again" for network access or no-response problems #195

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Type a really clever and fun shout-out when you check-in
2. click "check-in"
3. have the foursquare server not respond or time-out
4. get kicked back out to the venue page, your shout-out lost

What is the expected output? What do you see instead?
I would expect a "try again?" button or options at that point to save my 
shout/tweet.

This also happens when clicking on a venue and then having no response from the 
server, kicking you back to the list. It should ask if you want to try again.

For all connection errors, which are a fact of life for 4sq, there needs to be 
a way to "keep trying" so the user doesn't feel like giving up, because the app 
is giving up. I see many negative comments about this experience in the app 
store.

There is also the scenario where the request gets to the 4sq server, but there 
is no response, creating an opportunity for dup checkins. The server handles 
this well and doesn't complain, The app could perhaps check to see if it it's a 
duplicate as well by looking at the history again (I know that creates more 
server load)

Original issue reported on code.google.com by mitch.fi...@gmail.com on 15 Jun 2010 at 5:56