Situation: I have a use case where I want to nest multiple “sub-apps” under one “wrapper-app”
Further explanation:
I have written multiple stand alone Ionic apps (i.e. chat/messaging, calendar/events, budget/spending, …etc) and all of those are built and deployed as is and as a stand alone app (which is desired and still required).
What I am looking to do is package all of those apps under one “wrapper-app” (single download/url grants access to all apps).
The “wrapper-app” would function at a high level where it is pretty much in charge of a few primary functions;
- Basic page structure and themeing
- Custom home/dashboard page
- Core providers that manage stuff like api auth users config, etc
- Navigating to the “sub-apps”
* The “wrapper-app” can specify which/how many “sub-apps” it implements, for example my existing stand alone apps would implement the same structure, although they would only inlude 1 app from the “wrapper-app”, whereas the super-app would include multiple sub-apps…
The reason I am looking to structure the apps this way is I want the “sub-apps” reusable across multiple “wrapper-apps” and I also want just one “core” repo to manage changes to the “sub-apps” so once I make updates, the code will then cascade and be available to update everywhere
Am I thinking about the structure entirely wrong?
Should I scrap my ideas and go a different direction?
I was thinking I could just modify the folder structure a little bit to give it more structure and then manage the “sub-apps” through git
…maybe something like this could work and just handle everything with **.module.ts?
_wrapper-app-name (managed with git)
src
| app
| assets
| components
| models
| pages
| providers
| theme
* app-modules // create new folder (not sure what to name it…) to contain desired “sub-apps” (add .gitignore to wrapper-app for this folder)
_sub-app-name (managed with git)
src
| app
| assets
| components
| models
| pages
| providers
| theme