É válido mencionar que Capacitor só tem 1800 perguntas cadastradas no stackoverflow, contra 61 mil do cordova. Acabei optando neste momento por utilizar cordova, pra evitar esbarrar em problemas simples sem respostas
As a web dev I did some small mobile projects when the mobile apps were getting hot. I used Android SDK on my own (brutal), then discovered Cordova and really liked it, then discovered Ionic and liked that too. Cordova and Ionic have lots of plugins to handle a lot of complexities. I think most web devs will prefer a framework that nicely abstracts all the crud away (ever tried getting a simple dialog box to pop up in Java? Or have JAVA throw cuss words at you like 'Runnables'?). Much like Angular (both owned by Google surprise surprise) the learning curve is steep and suited for the JAVA/C heads. I'm glad I slogged through those projects but think most devs will opt for abstraction vs. close-to-native where possible. Cordova, then Ionic and most likely Cap then Android SDK would be the order for me.
Hello, Hoping you are fine I want to convert my existing Angular 9 web application into mobile and it's a big project so we don't want to start it from scratch, so I am looking for a technology that helps me to do it without lots of effort but I am conscious about the plugin that we are using like camera, WebSocket, microphone access, attachments will work or not. is capacitor helpful in this situation?
Two things I think are missing from this discussion. 1. The capacitor docs say "at the moment" you have to run it via android studio. I get the impression more tooling is going to be built. 2. According to their "design philosophy", capacitor are hands off with the project code. This unfortunately seems to mean that installing plugins are more involved as you are responsible for setting the install variables, app permissions, etc. At the moment the community doesn't seem to have embraced this in their plugin docs so you have to fish through the plugin.xml looking for what needs to be done, and then translate that to the android project manifest. It was a blocking point for me. To be fair, capacitor is not released yet so the comparison is premature, but I think in the long run it is going go evolve into a great option.
@@suki5593 you're probably right. Do you base that assessment on the terrible situation with third party plugins? My thing has been to write my own for the non standard stuff as then I can control em.
Yes, but don't install Cordova itself into your Ionic app. Capacitor allows you to install NPM plugins (including Cordova ones) and in the Ionic docs there is a quick tutorial on how to do this.
Depends. What do you need? Cordova is easier to use but its functionality is limited to what third-party plugins are available out there. Capacitor is new and still in beta (according to the Ionic team, it still isn't production-ready) but is a better choice if you're experienced with native mobile development. [Opinion and can be better explained.]
Watchin this video was to me like one of those "ooooh so that's why..." moments that I love when I'm learning sth mew!!! The capacitor file structure was causing me some trouble becouse of the assets folder with some plug-ins....
All of that symlink stuff in the tutorial was unnecessary. I'm not sure what the motivation was with the project setup they used. Normally you would just add cap/cordova to the actual app, not in a sub folder with a symlink of the www folder. You can read the official getting started guides for each of capacitor /cordova and they will explain it to you. This was more of a comparison / overview than a tutorial.
É válido mencionar que Capacitor só tem 1800 perguntas cadastradas no stackoverflow, contra 61 mil do cordova. Acabei optando neste momento por utilizar cordova, pra evitar esbarrar em problemas simples sem respostas
As a web dev I did some small mobile projects when the mobile apps were getting hot. I used Android SDK on my own (brutal), then discovered Cordova and really liked it, then discovered Ionic and liked that too. Cordova and Ionic have lots of plugins to handle a lot of complexities.
I think most web devs will prefer a framework that nicely abstracts all the crud away (ever tried getting a simple dialog box to pop up in Java? Or have JAVA throw cuss words at you like 'Runnables'?). Much like Angular (both owned by Google surprise surprise) the learning curve is steep and suited for the JAVA/C heads. I'm glad I slogged through those projects but think most devs will opt for abstraction vs. close-to-native where possible.
Cordova, then Ionic and most likely Cap then Android SDK would be the order for me.
Hello, Hoping you are fine
I want to convert my existing Angular 9 web application into mobile and it's a big project so we don't want to start it from scratch, so I am looking for a technology that helps me to do it without lots of effort but I am conscious about the plugin that we are using like
camera, WebSocket, microphone access, attachments will work or not.
is capacitor helpful in this situation?
Two things I think are missing from this discussion.
1. The capacitor docs say "at the moment" you have to run it via android studio. I get the impression more tooling is going to be built.
2. According to their "design philosophy", capacitor are hands off with the project code. This unfortunately seems to mean that installing plugins are more involved as you are responsible for setting the install variables, app permissions, etc. At the moment the community doesn't seem to have embraced this in their plugin docs so you have to fish through the plugin.xml looking for what needs to be done, and then translate that to the android project manifest. It was a blocking point for me.
To be fair, capacitor is not released yet so the comparison is premature, but I think in the long run it is going go evolve into a great option.
Hey,
can I turn a php website into an app, using one of these both?
Thanks
The cordova approach is way better in my opinion. Having an abstraction away from the native tools is the reason to use this approach at all.
It gives you a lot of problems. Capacitor is better
@@suki5593 you're probably right. Do you base that assessment on the terrible situation with third party plugins?
My thing has been to write my own for the non standard stuff as then I can control em.
@@judgewest2000 yes, i had issues with Bluetooth LE and I found capacitor easier
you are the best thankssssss
Can you make a video on using Cordova plugins in an angular application?
Can we use capacitor as well as Cordova plugins in an ionic angular project?
Yes, but don't install Cordova itself into your Ionic app. Capacitor allows you to install NPM plugins (including Cordova ones) and in the Ionic docs there is a quick tutorial on how to do this.
4:30 lol
We can also take a look at the strategies for these two toolchains!
two twoolchains
too toolchains
He didn't edit that out in post.
I thought my phone was stuck
I don't typically comment on a video but you just coded by your own and didn't explain much
any recommended resources for learning angular?
The tutorial on angular.io is great for some people. Others like courses like this one on Udemy: www.udemy.com/the-complete-guide-to-angular-2/
Google search Ultimate Angular, great courses as well!
Search jump start angular on RUclips.
So what do i use with ionicframework and ng6, Cordova or Capacitor?
Depends. What do you need? Cordova is easier to use but its functionality is limited to what third-party plugins are available out there. Capacitor is new and still in beta (according to the Ionic team, it still isn't production-ready) but is a better choice if you're experienced with native mobile development. [Opinion and can be better explained.]
Watchin this video was to me like one of those "ooooh so that's why..." moments that I love when I'm learning sth mew!!!
The capacitor file structure was causing me some trouble becouse of the assets folder with some plug-ins....
Plz I want to know the command prompt steps for windows
All of that symlink stuff in the tutorial was unnecessary. I'm not sure what the motivation was with the project setup they used.
Normally you would just add cap/cordova to the actual app, not in a sub folder with a symlink of the www folder.
You can read the official getting started guides for each of capacitor /cordova and they will explain it to you. This was more of a comparison / overview than a tutorial.
In my experience Capacitor is much much better. Less problems and easier
But If I'm not misunderstanding, The Capacitor is not have many plug in like cordova. Is it right?