مساعدات التحقق في نماذجكم

A model should know what valid looks like. Adding validation to shared code means both apps enforce the same rules.

A computed property derives a value from the model's fields. It runs whenever you read it, with no stored state.

Give the model an isValid property that bundles all its rules into one boolean both apps can trust.

A function on the model can run a check and return a result, keeping the logic right next to the data.

Instead of a plain boolean, return a list of messages so the UI can tell the user exactly what to fix.

Extract a small helper so several models can share the same rule, like a reusable email or length check.

Keep every rule in commonMain so Android and iOS validate identically and your forms never disagree.

An init block with require can reject bad data the moment a model is built, stopping invalid objects early.

Validation should only read fields and return results, never touch UI or network. Pure rules stay portable and testable.

Because the logic is plain Kotlin, you can test it once in commonTest and trust it on every platform.

Shared validation means a rule changes in exactly one place and instantly applies to both apps. 🙂

Add validation as computed properties, methods or init checks in commonMain, keep it pure, and both apps enforce identical rules.