It’s simple, start the service in the background to check for updates regularly, download new image resources when there are updates, and load and enable new images the next time you open the app. It just seems to be irregular for users.
The one above is the commonly used method. If you feel that regular updates are too troublesome, it is easier to check for updates when the app is opened. If you want to open the app and detect new pictures, download them and display them, you will definitely end up waiting for too much time in the welcome interface.
Start checking for updates on the welcome page, but when the network is not good, it will take a little more time.
Set a reasonable time to detect updates (for example, when exiting the program, request the network, then save it (exit the app at this time), and then when you start the next time, read whether there are updates, directly Enter)
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
It’s simple, start the service in the background to check for updates regularly, download new image resources when there are updates, and load and enable new images the next time you open the app. It just seems to be irregular for users.
The one above is the commonly used method. If you feel that regular updates are too troublesome, it is easier to check for updates when the app is opened. If you want to open the app and detect new pictures, download them and display them, you will definitely end up waiting for too much time in the welcome interface.
Start checking for updates on the welcome page, but when the network is not good, it will take a little more time.
Set a reasonable time to detect updates (for example, when exiting the program, request the network, then save it (exit the app at this time), and then when you start the next time, read whether there are updates, directly Enter)