The quickest framework is the one closest to what the team already writes.
Capacitor 243,123 asks the least of a web team: any framework or none, the same browser DevTools (Remote Debugging Android), and the same web build. The new skills are the native projects (Native Projects as Source), signing and store work (Building and Publishing), and reading Kotlin or Swift when a plugin misbehaves. A web app can also stay a web app: BookNest's Framework7 572,986 code runs unchanged in a browser.
Cordova 129 asks the same of a web team, but with an older toolchain, a regenerated platforms/ folder and a shrinking plugin base. Choose it only to maintain an existing app; Migrating from Cordova is the way out.
React Native 36,878 suits a React 7,897 team. Components, hooks and state carry over from MERN Stack Development, but the elements are View and Text, not div and span, styling is a subset of CSS in JavaScript, and web libraries that touch the DOM don't work (React Native). Expo 6,418 removes most native setup.
Flutter 16,720 means learning Dart and its widget model: layout by composition (Padding, Column, Expanded) rather than CSS. Dart is easy for anyone who knows TypeScript or Kotlin, but nothing from a web codebase carries over, and the web target renders to a canvas rather than to ordinary HTML.
Tauri 126,184 keeps a web front end but puts the app's native logic in Rust, called through invoke(). Its mobile setup adds the Android NDK and four Rust targets (rustup target add aarch64-linux-android armv7-linux-androideabi i686-linux-android x86_64-linux-android) to the usual Android SDK. It pays off mostly for teams already shipping a Tauri desktop app.
Every framework still needs someone who can open Android Studio 234 and Xcode 10 : for signing, store releases and native crashes, native knowledge (Android with Kotlin) remains part of the job.