Why EasyCord

Explains the technical architecture choices behind EasyCord.

Overview

Building native mobile applications requires learning new UI paradigms or managing complex native bridge architectures. Legacy WebView wrappers can have performance and security limitations.

EasyCord allows developers to build native apps using existing web technologies without writing native code.

Architecture Decisions

Zero Boilerplate

EasyCord does not require NPM packages for hardware access. The native shell injects the window.easycord API directly into the web application at runtime.

Security Model

EasyCord operates on a strict permission model to prevent malicious scripts from accessing device hardware.

Origin Locking: The native bridge only responds to the app's domain. The WebView blocks external links to prevent cross-site scripting.
Iframe Isolation: Third-party widgets inside iframes cannot access device hardware.
Capability Whitelisting: Native features must be explicitly allowed in the easycord_permissions.yaml file.

Performance

EasyCord uses the Flutter rendering engine for the native shell.

ProMotion displays are supported on compatible devices.
The framework provides access to hardware haptics and OS-level UI controls.

Flexibility

EasyCord can build new applications, embed web dashboards into existing Flutter apps, or wrap existing websites.