bridge

The problem

Web applications need native capabilities: secure storage, biometrics, file access, share sheets, offline downloads. Each platform implements these differently. Without a shared layer, every application rebuilds the same bridges.

The approach

Bridge provides a single interface for native capabilities. One TypeScript API, implemented in Kotlin for Android and Swift for iOS. Applications call the web interface. Bridge handles the platform-specific work.

No unnecessary abstraction. No generic frameworks. Just small, focused plugins that solve real problems shared by multiple projects.

Principles

Quiet. The interface should almost disappear.
Stable. API compatibility maintained across versions.
Documented. Every plugin includes examples and platform notes.
Tested. TypeScript, Android, and iOS tests for every plugin.
Shared. Added only when at least two projects need it.

Current state

Bridge has its first plugin: @palmshed/secure-storage. It provides secure key-value storage across Android, iOS, and web.

Bridge works with Capacitor. The example app includes full Android and iOS projects ready for native development and testing.

More plugins will be added when real projects need them. This is intentional. Premature abstraction adds maintenance without adding value. Real need drives real design.

Structure

packages/bridge-core/. Core utilities
packages/secure-storage/. Secure key-value storage
packages/example-app/. Development playground
docs/. Design language and philosophy

Resources