Saturday, 15 August 2015

ios - Reporting network errors to users -



ios - Reporting network errors to users -

note: more of "philosophical" question technical one.

so, i'm writing ipad app syncs info backend wrote. sync works well, on good network 1 @ apartment.

but in slow or otherwise mediocre network public 1 in starbucks or office has tendency error out. in testing, when fails (albeit, infrequently) on these mediocre networks it's timeout or "could not connect server" scenario, , sec effort has consistently succeeded, resulting in successful sync.

so question how or whether study these errors user. right quietly study errors user ( using unobtrusive error mark, not modal dialog ), it's annoying in these scenarios because next sync (has far) succeeded.

for context: app syncs in background, continuously, local changes spotted , pushed server , long-polling background thread watches changes on server , pulls them downstream app.

my thought when sync, should seek (for example) 3 times, breaking out on first successful attempt. if 3 attempts fail should study error user.

is reasonable idea? or terrible idea?

thanks,

ios networking user-experience

No comments:

Post a Comment