Use ODC to build multiple mobile apps, where some data needs to be shared across these apps. Additionally, there will be a web app for data management. The question is whether the database should be hosted under a dedicated mobile app for all apps to reference, or instead be placed under the web app for mobile apps to reference the web app.
The ODC architecture best practice don't mention about the data management app should be mobile app or web app so it's your choice.
personally I prefer web app because it's easier for UI implementation than a mobile app.
For general data management or backoffice screens, i think we always want to change the data immediately and not use local storage so my team usually use web app because it's easier to implement UI for than mobile app.
You are a breath of fresh air in this field.
Hello,
I think the web app is the better option for hosting the database.
The main difference between mobile and web apps in OutSystems is that a mobile app is built using Apache Cordova and supports offline data management, such as local storage. This is essentially why we use a mobile app in the first place.
In a web app, things are different. All data management is done online, with no offline capabilities.
Because of that, I think there is no real need for offline capabilities in data management, as they are generally not required by end users, but rather apply to specific business use cases.
Another thing if it is possible for you, use a centralized external database that can be shared by both mobile and web applications.
Hello.
By default we do the centralized database in a web app because you can build a nice backoffice to monitor, edit and analyze data.
If all your apps are OutSystems do not use an external database as you have no advantages in adding complexity. Keep it inside OutSystems and you will have faster times.
All mobile app and web app are built on OutSystems. Would it be more reasonable to create a separate web app for data management, with all other applications referencing this one? And would this approach cause any performance issues?
Be aware that the architecture will depend on your project. A single app for the full DB may not be ideal.
The same applies for having the database and the backoffice in the same app. If you have multiple mobile apps consuming it, I say you will probably have frequent changes to the diagram. Will your data always stay in a single app and the data management app always evolve as fast as mobile apps? In some cases I think so as it is a small adjustment or a page done by scaffolding, and you can do it in the same app.But again, you have many mobile apps so many people asking for changes in a near future. If you may want to split the database, or start to add complexity and business rules, make it in an isolated app.
I'm with @Nuno Reis on this,
the question should primarily be what data belongs together, and based on that, you might want to split them up across several apps, each with their own change agenda/lifecycle.
Whether the app holding your data happens to be mobile or web is less important, i.m.o., as both the data itself as the entity actions are happening server side, doesn't really matter what technologie the frontend of that app is.
Dorine