How to separate app interfaces, front-end websites, and background management in projects

For example, in a project, the development of the app interface, website front-end, and background management modules is to use one project for development respectively, or use one project for separate module development, how can I reuse some common functions of different projects, such as the order place used by the app and website front-end... for example, in a project, the development of the app interface, website front-end, and background management modules is to use one project for development respectively, or use one project for separate module development, if different projects are used, how should we reuse some common functions, such as the order processing used by the app and website front-end? Do we need to separate these functions.

Reply content:

For example, in a project, the development of the app interface, website front-end, and background management modules is to use one project for development respectively, or use one project for separate module development, if different projects are used, how should we reuse some common functions, such as the order processing used by the app and website front-end? Do we need to separate these functions.

Using restfull API, common parts can be made into Libraries

We now use swagger to define data interfaces. The front end uses h5 static pages, and the Web directory is assigned a directory for the front end. The app project has a dedicated attachment directory, and the back end uses the Java idea project, the front end uses the h5 hbuilder project, and the app uses the Android studio project.