Hi everyone.
I’m new to Wappler and have some what are probably regarded as ‘basic’ questions. Thing is I need to get this right from the start, I think.
I’m going to create a prototype web app. This app will be pulling info from various APIs. In the first iteration of the app I’m not planning on storing the info retrieved from the APIs to a database. This may be an option for the future.
I intend to also create a mobile app. I’d like this app to also display info from the same APIs the web app is consuming. I’m aware the mobile app can be configured in Wappler to use a ‘web app’ as the source of information.
My main question is…in order for the mobile app to use the APIs the web app is calling, will it be enough to use the web app as the source of info for the mobile app, or would the web app need to store the data that the mobile app needs access to?
A mobile project does not have a server side…it simply points to another project that does. So you can have project A that serves as your common backend along with a web front end, and project B would be your mobile project.
I’ll need to read more about the mobile framework and how that interoperates with the backend. It sounds like I’ve found the right tool (Wappler) to make my life a lot easier.
I assume I need to expose APIs from my Wappler built backend? Anyway, this is what I mean when I say I need to read the docs.
In Wappler you define server side actions with Server Connect. That is basically your API. So you can use them both on web projects as well mobile projects.
