Configuring Your App
Capacitor embraces the idea of "Code once, configure everywhere": configuration is
managed per-platform instead of in an abstracted system like a
config.xml in Cordova, for example.
This is an important point, because it means that Capacitor requires you to be more involved in the native project configuration than with Cordova, for example. However, we think this is the right approach, because it makes it easy to follow existing Native iOS/Android guides, get help on Stack Overflow, and have full control over your project.
Additionally, because configuring a Capacitor project is no different from configuring an iOS or Android project, existing native development teams can easily work alongside web developers, with each side using the tools and SDKs they are familiar with. Of course, we believe web developers can handle all the required Native configuration on their own, and the Capacitor documentation exists to help web developers do just that.
Capacitor has some high level configuration options that are set in
capacitor.config.json. These generally don't modify native functionality, but control Capacitor's tooling.
The current ones you might configure are:
iOS and Android each have configuration guides walking through making common changes to their behavior: