Thanks George. I think it would be great if the way in which Wappler deploys it’s template documents and Projects (desktop and possibly mobile) would match the same structures as the majority of the documentation that relates to them.
After working with Electron for a couple of months now I’m quite sure the above outline for the structure is quite a standard implementation you can find across the web so documentation all matches up and file locations and the naming conventions all are relevant to the available information on sites like Stack Overflow etc. The current template for Electron is quite confusing and throws Cordova in quite unnecessarily. Example would be to use the actual stock Electron Boilerplates over the Corodva based alternative would be a great start, and to follow the outlines discussed here:
As you can see the suggested structure for new Electron apps is:
And then simply from the terminal issue:
npm install --save-dev electron
And the job is all good!
Where as Wappler’s current template contains so much unnecessary bloat due to its reliance upon Cordova. Would going this way make it easier for your team at Wappler? A lot less requirements and a lot cleaner result for the end user would be the outcome, and as I mentioned documentation and learning resources would then make more sense.
Won’t comment too much on the Mobile side despite having deployed several applications we never went too far down that rabbit hole as until there is a way to build cross platform mobile applications without all the grief we have to go through right now (man its head banging tiring work, very frustrating, and incredibly time consuming, by whichever way we attempted to undertake such developments, Android Studio is terrible to say the least, then there are the market places for Apple and Android which is another different ball game conforming to standards), no fault of Wapplers that is, we have pretty much abandoned developments in this area, hence really pushing Electron and desktop based applications to our Clients.
Maybe @mebeingken could suggest some structures which would be more in-line with the industry standard for mobile apps?
It’s all just a thought really, to help in moving people forward as fast as possible with using Wappler as a tool to aid in these popular areas of development. Probably not the correct place to discuss this in poor Kierens thread… Sorry Kieren! It just spurred me on to make this suggestion.