Communication between client and server applications on Meteor. Common base or API?

Question

JavaScript

There is a task to make a system for receiving orders from an Android and iOS application.
We decided to take meteor as a platform.
Reasons:
- Fairly understandable documentation and you can find answers to some questions
- Easily converts the code to an Android and iOS application
- Mongo suits
- Clear template engine
Since the order database will be the center of the system, and the data will come from the application, questions arise.
Basic Entities
- Order Base
- Phone Applications
Questions:
1. Is it necessary to separate the application code from the order base? In meteor, you can do a split and check on isCordova, for example, to check that this is an application.
2. Or is it better to make them with different code and attach to the same mongo database?
3. Or for the application to send requests and receive responses from the order base (API). Since the application can be rewritten.

Answer 1

Usually, the client has its own database (Core Data for iOS or sqlite storage) with which the application works and which is synchronized with the remote database (REST? ). This architecture, in principle, should not depend on how the most remote database is implemented. And there must be a network layer of the application, whose task is to synchronize and update data.