One product, complete responsibility
Vajeh is a Persian five-letter word puzzle published on Google Play and the App Store for iPhone and iPad. Players have six attempts, with hints, word meanings, streaks, statistics and shareable results supporting the core game. It is deliberately focused, but it covers the parts of mobile engineering that are easy to miss inside a large organisation: shaping the product, finishing the language and interaction details, managing store releases and responding once real people have the app.
The product has passed 500 downloads and continues to evolve. That number is modest by consumer-platform standards and useful precisely because it is real. It represents users whose devices, language settings and expectations cannot be controlled in a test environment.
Kotlin Multiplatform as a product boundary
Vajeh is my end-to-end Kotlin Multiplatform product. Shared Kotlin owns reusable game rules and product behaviour so that the most important decisions have one source of truth. The application layer stays close to the platform experience, including Persian right-to-left presentation and the details that make a word game feel immediate rather than generic.
This is practical KMP rather than a technology showcase: sharing is valuable where it prevents product drift, while platform work remains explicit where users feel it.
What this demonstrates
Owning a live app keeps architectural decisions honest. Release friction, product clarity and operational feedback matter as much as an elegant module boundary. Vajeh is where hands-on KMP and Android craft meet the full responsibility of shipping and continuing to improve a product.