A
Well, since your request is being carried out for a while, you're not gonna be able to take your interface back to download.There are two options:Hang some boater, in the simplest case, a cooler, if you want to jump in and make the User-Frendly interface look towards the Skeleton pattern.It's to load the data in advance, keep them in the cash and then pull them out. But there's a couple of nuances here:If you don't have any data at the time of the start-up on the new screen, it's not gonna fit you. For example, if you get some information from the user and depending on this information, you're gonna have to go to option one.If all data are downloaded when your application is downloaded, the data will be downloaded, but the user will never use it (not come on this screen for example) and it will be possible that you have spent the user and the phone's memory on empty.Therefore, your task is to take these points into account and plan the loading at a time when the user has the potential to use them. If, for example, you have a float when the user enters a bank application, and there's a screen for the order. To this end, he needs to make a flash drive like this: меню -> еще -> инфо -> заказать справки. You don't need to load them with the app, but if, for example, the user failed before the Info feed, maybe it's time to start loading them.Well, it's a good tone, but more difficult implementation is to show data as they are downloaded. Suddenly, if you also have a bank application and a map screen contains the maps and a list of operations on it, and they're holding two different requests, then don't wait for both of them, but show them as they get, for example, first if they're downloaded, then the list of operations. It's possible to keep the data from being loaded with all the coppers, so the user has a very slow internet, so you can show him some information.