For most new apps, start with Capacitor 243,123 : a current toolchain and the ecosystem's momentum. Cordova 129 is still a sound choice in a few cases:
You maintain a Cordova app. Keep it on the latest cordova-android, which is what Google Play 1 's yearly target rule requires (Play Console Requirements), and migrate when a plugin or requirement forces you.
You depend on a plugin that only Cordova runs, such as one that relies on hooks, install variables or its own splash screen or WebView (Plugin Compatibility).
You want the simplest possible wrapper, a regenerated native project you never open, and accept the smaller plugin shelf.
Your tooling expects it, as Monaca, VoltBuilder and the visual IDEs of Alternatives and Tools do.
Choosing Cordova today does not lock you in. Everything this chapter built carries over: the www folder becomes Capacitor's webDir, most plugins keep working, and your config.xml settings move into capacitor.config.json and the native files. Keep your versionCode rising and avoid cordova.platformVersion checks, and the move is mostly mechanical. Capacitor wraps the Framework7 572,986 BookNest in Capacitor from the start, and Migrating from Cordova walks through migrating a Cordova app step by step.