docs: highlight no frontend/backend split — modular separation, not network boundaries

Author: kdroidFilter

docs/index.md

@@ -50,6 +50,7 @@ Compose Multiplatform is not "React Native for desktop". It is a **compiled, typ
 - A reactive state model that makes React look verbose
 - Hardware-accelerated rendering via Skia — animations at 120fps without thinking about it
 - Shared code across Android, iOS, desktop, and web — write once, render natively everywhere
+- **No frontend/backend split** — No REST API, no serialization layer, no JSON over HTTP between your UI and your logic. Your UI calls your business logic directly, in the same language, in the same process. Separate your concerns with **modules**, not with network boundaries.
 
 And on top of Compose sits **[Jewel](https://github.com/JetBrains/jewel)** — the most advanced desktop UI framework in the world. Not a web framework adapted for desktop. A desktop framework, period. Jewel carries behind it the entire experience of JetBrains and its IDEs — IntelliJ IDEA, Android Studio, Fleet — applications used daily by millions of developers and built with desktop in mind from day one. It is the same design system, the same component library, the same pixel-perfect attention to detail that powers the tools professionals trust most.