Hi,
If we want to create a mobile app and an admin panel to manage it.
1. Do we suppose to create a separate web application for the admin panel and another separate application for the mobile app? Or should we combine it and create one application?
2. If we create two apps, how do we pass data from one application to another?
(Do we need to setup rest apis from admin panel?)
3. Why do we have server functions (tables) available in the mobile environment? (Aren't the web server suppose to execute all crud on behalf the mobile app, via GET/POST requests?)
Does OutSystems automatically converts all the aggregate functions to Rest API's and consume them after we export it to Android/iOS?
Thanks for the help!
Hi Chamika,
Let me try to answer these questions:
I hope this helps, if you have any further questions, don't hesitate to ask them.
Kilian Hekhuis wrote:
Hi Kilian,
Thanks a lot for the quick reply. Your answer cleared most of my doubts.
In this particular requirement I want to have a separate admin website to handle all the administrative work and mobile app just for the users to fill a form and submit (system will be mainly handled by the admin panel).
So will it be a good idea to create a separate module for the entire database(DB_Core) and add this database into the mobile and admin applications as a dependency?
And also, is it correct to say that I don't have to use any Logic > Integrations > Rest/SOAP to get data from the server as I can directly use the server actions with aggregates?
Thanks!
Chamika Sanoj wrote:
For this yes it is a good solution to make a admin approach by a webpage. The communication is always by database. So you do not need any admin rights on your mobile app.
You cannot query server-side databases directly from a mobile app, but you can create a server-side action (or consume one) and call that from mobile. So if your mobile app must be on-line in order to function, and the data connection is fast enough, you can have a DB_Core that contains all the Entities, and use that in both apps.
And yes, there's no need to use REST (I'd forget about SOAP unless you must connect to some external service that uses it) if you are only retrieving data from the core module. But REST may be a good abstraction if you are also getting data from other places, so you don't end up with a lot of references.