In order to use web applications in your native applications, you'll need to properly setup your project to be able to include a web bundle.
Your web application needs to be copied into your native application. On iOS, put your web assets in a directory at the same level that contains your main source and the
You will need to include the folder in XCode (and not just simply copy the folder to the right directory).
PortalManager.newPortal("myPortalWebApp").create() // or...using a different portalId and starting directory PortalManager.newPortal("help") .setStartDir("myPortalWebApp") .create()
In Android, your web application needs to be in the assets folder; which by default is
src/main/assests. For example, if your web application is a help page, you can put your web application in the
src/main/assets/help folder. From there, you can either set the
portalId for the Portal to
help or you can manually specify
help as the directory using the .setStartDir() function.
PortalManager.newPortal("help").create() // or... PortalManager.newPortal("MY_PORTAL_ID") .setStartDir("help") .create()
PortalManager.newPortal("help").create(); // or... PortalManager.newPortal("MY_PORTAL_ID") .setStartDir("help") .create();
Once you have your web code and native code linked up, you will need a process to continually copy in new versions of the web application into your mobile projects.
We recommend having some type of automation set up so the mobile developer doesn't have to manually copy over the web code every time there is a new change. We have a few guides for ideas to do so in a monorepo or git submodules.