ما يمكن وما لا يمكن مشاركته بعد

KMP shares a lot, but not everything. Knowing the real boundaries keeps your expectations honest on a production team. 🧱

Pure rules and calculations share beautifully. Your business logic has no platform ties, so it runs the same everywhere.

Your data models, the classes that describe a user or an order, are easy wins. Define them once and use them on every target.

HTTP calls and JSON parsing share well using multiplatform libraries. Your whole networking layer can live in shared code.

Databases and key-value stores have multiplatform options too. So your storage layer is also a strong candidate for sharing.

Most teams keep the UI native for the best feel. You can share it with Compose Multiplatform, but it stays a real choice.

Camera, sensors, and OS dialogs differ per platform. These platform features need native code, often behind a shared interface.

For things that differ per platform, KMP offers expect/actual. You declare a common API and give each platform its own version.

Not every Kotlin library is multiplatform. JVM-only libraries cannot go in common code, so check support before adding one.

A common starting line: share logic, data, and networking; keep UI native. Adjust the split as your team gains confidence.

The KMP ecosystem grows fast, so what is shareable keeps expanding. More libraries go multiplatform every year.

Let's test the sharing boundaries.

Share logic, models, networking, and storage freely; keep UI and device features native. Use expect/actual to bridge the gaps. 🎉