General guidelines and workflow for new quasar/capcitor dev #17910
Unanswered
mikekotas
asked this question in
CLI - Capacitor / Cordova modes
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello team,
I have started experimenting with quasar and the addition of capacitor.
I am mostly orientated to the web apps but now that i can have one single code base abd build a mobile app i will give it a shot
I have gone throuh the docs and i have installed the quasar cli, i have created the default SPA from the boilerplate guidance, i then added capacitor and created the src-capacitor dir, i installed and configured android studio and i can see it being opened when i run the dev capacitor command , i can start the emulator medium API and see the changes in the app.
So i have the default quasar SPA template installed and i simply added a custom logic to check for the app's version so i offer in app updates rather than publishing it ot the store(Android). I have created a github page where i store the signed apk and a json with code version version name and the url of the apk. I have some conosle.logs when the version is grabbed so i can see what it reads etc.
I have read that the way to debug is with the//inspect in chrome, but honestly i have tried like a mililon times and all i get there is for example my nvidia shield device which is in the network, then most probably i ee the emulator since it is a random name there, but all i see is the names of those devices, not clickable no other details under or around them. I do not know what am i missing or what i do wrong with this. All i know is for sure i cannot continue without reading the logs 😄 . If there is any other way to see console.log logs please let me know so i can try, either in android studio or vscode directly(I checked there the ionic plugin, but ....nothing i could work with , i think it is meant if you want to start a capacitor project from start even though if they have the option to add it in an existing project)
Apart of all this which is my main problem for now, what would be your suggestion for starters like me in regards to the creation of the app progress? Since the intention is a mobile app, should we stick with the classic web using the dev tools and mobile simulation in chrome till we have everythign set up and then just spit out the apk with the build?(saying this since those coming from web past might be more easier to work with it , using logs etc)
Additionally when we want to install plugins, should we do in the root of the project so the root package has those dependencies, or in the src-capacitor dir??? is there some kind of distinction on what shoudl we do in the src-capacitor if any to do there?
The name of the app after thee apk is installed, so the one we see app info either in the emulater or in the physical device arrives from the src capacitor cconfig file or from else?
Thanks in advance for any help!!! Really appreciated!!!
Regards
Beta Was this translation helpful? Give feedback.
All reactions