Normally, MySQL databases are not placed in Android applications. MySQL is too "heavy". Android applications generally use Sqlite as the local database. MySQL can be used as a remote database to store larger and more data. If it is placed on the remote server, there will be no direct connection problem. If the client wants to connect to the remote MySQL, it can use the network HTTP protocol (common POST and GET requests). This How to deal with this part, you have to learn back-end technologies such as javaweb or php.
The Android client does not use mysql directly, but can use lightweight sqlite and realm databases. Any server language will work. Use REST API to interact, which is standardized http+json. If it is java, you can use jersey, springmvc. If the java server uses mysql, you must use the database connection pool
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
The solution I have used is to request webapi through the app, and the webapi completes the interaction with the database
The solution I have used is: PHP serves as the server and returns json. Hybrid development
Normally, MySQL databases are not placed in Android applications. MySQL is too "heavy". Android applications generally use Sqlite as the local database. MySQL can be used as a remote database to store larger and more data. If it is placed on the remote server, there will be no direct connection problem. If the client wants to connect to the remote MySQL, it can use the network HTTP protocol (common POST and GET requests). This How to deal with this part, you have to learn back-end technologies such as javaweb or php.
The Android client does not use mysql directly, but can use lightweight sqlite and realm databases. Any server language will work. Use REST API to interact, which is standardized http+json. If it is java, you can use jersey, springmvc. If the java server uses mysql, you must use the database connection pool