File, db. Configuration tables, etc. will not work. Remember not to store data in Application. In addition, data can be restored through the life cycle, but it is still recommended to store data with a long life cycle in the form of files. Such as what I mentioned in my appeal.
Not only the global data of Application, but also static global variables will be destroyed. The use of static global variables should be reduced in Android, and even if they are used, attention should be paid to storage and recovery during the life cycle.
Database, shareprefrence, file cache, network server, etc. are all stored in the form of file storage. The programs stored in the memory will be released after the program exits
Databases, sharedpreferences, files, networks, these can be stored persistently. In this way, when starting the application, you only need to read the corresponding content to restore the data display effect
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
File, db. Configuration tables, etc. will not work. Remember not to store data in Application. In addition, data can be restored through the life cycle, but it is still recommended to store data with a long life cycle in the form of files. Such as what I mentioned in my appeal.
Not only the global data of Application, but also static global variables will be destroyed. The use of static global variables should be reduced in Android, and even if they are used, attention should be paid to storage and recovery during the life cycle.
Database, shareprefrence, file cache, network server, etc. are all stored in the form of file storage. The programs stored in the memory will be released after the program exits
Databases, sharedpreferences, files, networks, these can be stored persistently. In this way, when starting the application, you only need to read the corresponding content to restore the data display effect
What the person above said is right