Framework Comparison

Compares EasyCord against other hybrid mobile frameworks.

Overview

This page explains how EasyCord differs from Capacitor, Cordova, React Native, and Tauri. It highlights architectural differences, code reusability, and language requirements.

Capacitor

Capacitor wraps web apps in native shells. It requires specific NPM dependencies for native features.

Dependencies: Developers must install NPM packages like @capacitor/core to access native features. This couples web code to mobile dependencies.
EasyCord: EasyCord injects native APIs into the window object at runtime. The web frontend requires no mobile-specific NPM dependencies.
Languages: Capacitor plugins require Swift, Objective-C, Java, or Kotlin. EasyCord plugins use Dart.

Apache Cordova

Cordova relies on an older bridge architecture to communicate between JavaScript and native code.

Performance: Cordova uses older bridge methods that can bottleneck data transfer. EasyCord uses modern WebViewController message channels.
Maintenance: Cordova uses XML configuration files and older native languages. EasyCord uses a Dart plugin architecture.
Security: EasyCord enforces a central easycord_permissions.yaml file to explicitly define WebView permissions.

React Native

React Native translates specific React components into native UI elements. It does not run a web application in a WebView.

Code Reusability: Developers must rewrite UI using React Native components like <View>. Standard HTML and CSS are not supported.
EasyCord: EasyCord runs existing web applications, including HTML, CSS, and JS, directly in the mobile shell.

Tauri

Tauri provides a Rust-based framework for Desktop and Mobile applications.

Languages: Custom backend logic and native plugins in Tauri require Rust. EasyCord uses Dart for native plugins.
Ecosystem: EasyCord runs on Flutter, providing access to Dart packages on pub.dev.