(2b) is the normal way to do this, show stubs or progress/loading or cached data while loading and you have ample space to provide reasoning and controls in case of failure.Ĭonsider whether prefetching all or partial amounts of contact data in advance (schedule to your/users' liking) will significantly benefit the user experience while not hurting battery and data use. It's a bit like a bouncer (gatekeeper/login screen) that let you slip through but boots you out moments after, not a pleasant experience. tour guide.įor (2a), you deny yourself the chance to retry (which would be the best solution, as long as the connection is reestablished before the user's patience runs out). I mention MVC above, because each page should only be interested in the data it downloads and displays/handles and if item (1) above is the desired experience, the Contact details will need to be downloaded prior to being handed off to that page, which kind of goes against this pattern.įor (1), you would be effectively blocking navigation momentarily and potentially denying it, which may spoil the users perception of navigation throughout the app (can block discovery of the app and it's features purely because of a lack of or poor connection). The event of an error is it best to display the error and:
Indicate at least the user's action has been recognised. Navigate to the page display "skeleton" text and/or an animation to This also goes against MVC guidelines from a code perspective. The worst case scenario, it looks like the app cannot even navigate Navigation, but can be perceived as nothing at all happening and in What is best in terms of UX?ĭisplay a "loading" animation attempt to download the data and displayĪn error while remaining on the contact list. because of network coverage on a mobile device) and so an error occurs. However, this information may not be obtained each time (e.g. Given the following scenario: say I have a contact list which contains a name, I then click on the contact and, in a successful scenario, the Contact Details are downloaded from the server (which contains more information on the selected contact), and that information is displayed. I cannot find this information online in Apple's Human Interface Guidelines (or I am looking in the wrong place if so), nor Google's Material Design Guidelines.
What is the best perceived UX for mobile applications which require data downloaded midway through the journey.
0 kommentar(er)
