Skip to content

Commit b0a5ce5

Browse files
authored
Remove benefits section from README.md
Removed sections explaining the benefits of ComposeNativeWebView, including native engines, tiny desktop footprint, and familiar API.
1 parent 39ea8e8 commit b0a5ce5

1 file changed

Lines changed: 0 additions & 37 deletions

File tree

README.md

Lines changed: 0 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -40,43 +40,6 @@ Desktop engines:
4040
* **macOS**: WKWebView
4141
* **Linux**: WebKitGTK
4242

43-
---
44-
## Why ComposeNativeWebView? ⚡
45-
46-
### Native engines. No bundled Chromium.
47-
48-
Unlike KCEF-based solutions, **Desktop uses the OS webview**:
49-
50-
* **Windows**: WebView2
51-
* **macOS**: WKWebView
52-
* **Linux**: WebKitGTK
53-
54-
👉 Smaller binaries, faster startup, system-level rendering.
55-
56-
---
57-
58-
### Tiny desktop footprint 📦
59-
60-
Desktop ships only:
61-
62-
* a **minimal JVM bridge**
63-
* **native bindings** (UniFFI + Rust)
64-
65-
No embedded browser runtime.
66-
67-
---
68-
69-
### Familiar Compose WebView API 🧩
70-
71-
Same mental model as `compose-webview-multiplatform`:
72-
73-
* `WebViewState`
74-
* `WebViewNavigator`
75-
* observable loading state
76-
* cookies
77-
* JS ↔ Kotlin bridge
78-
* request interception for app-driven navigation
79-
8043
---
8144

8245
## Quick start 🚀

0 commit comments

Comments
 (0)