Our work-flow is generally as follows as all components make the package:
- Create blank HTML Project. Add your Frameworks etc.
- Set-up what will be the API as a second Wappler Project. Can use PHP or Node as its the back end (Android will not natively pass PHP but on the back-end is fine).
- Clone the website Project (we run a cron job on the directories to sync them, could use GIT).
- Clone is for mobile. So we add Android as the Platform, update Cordova if prompted (and dependencies like Gradle etc).
Both Projects share the same synced assets and new pages (if they don’t exist).
Could also have a second clone and add Electron and do the same, and the same for any other Platform you pick.
Keeps things simple for us and maintains a lot of style uniformity among all the Projects. Easy to maintain. Both the Android and HTML projects then use the API Project for data etc. You can use anything you like from Wapplers vast library of features. We have not found one that doesn’t play well. As for the other features specific to Android there are many plugins available. Just remember to backup a lot as now and again things can go a little Pete-Tong (UK slang for wrong)…
Hope that helps a little?