Mobile app development: native Android, PWA and cross-platformMobile app development: native Android, PWA and cross-platform

Mobile app development cost is not driven by screen count. A five-screen app with payments, real-time chat and offline sync costs more than a twenty-screen app of simple content. The main drivers are target platforms, backend complexity, integrations and how much custom design you need. We usually recommend starting with a small, shippable first version, getting real feedback, and investing from there. After a discovery session we put the scope and estimate of each phase in writing.

Go native if you need the camera, Bluetooth, reliable notifications, heavy background work or store in-app billing, or if your audience expects to install from a store. If the product is mostly forms, dashboards or content and you want lower cost, instant releases and iOS reach without the App Store, a PWA is enough and often better. For Paradise Desk we built both side by side, so each user can come in through the route that suits them.

Kotlin is Google's recommended language for Android, and Jetpack Compose is today's standard toolkit for Android UI. Compose code is shorter, easier to test, and handles dark mode and right-to-left layouts cleanly, and new Android libraries land there first. The same skills also extend to web and desktop through Kotlin Multiplatform and Compose Multiplatform, which is how one shared rules engine in Hamdor runs in both the Android app and the web build.

Usually not exactly half, but the savings can be real. Business logic, networking and data are written once, and only the parts that must sit close to the operating system are built separately. The hidden cost is that the architecture must be right from the start, and some platform-specific behavior needs extra work. We use Kotlin Multiplatform because it keeps native UI and performance and lets us drop into platform code wherever needed.

Yes. We prepare release builds, sign the app, produce store listings and submit for review. In-app payments are verified on the server so forged or duplicate purchases are rejected, and if the app is also distributed outside the stores we connect a separate payment gateway. In Hamdor we implemented four payment routes: Cafe Bazaar, Myket, ZarinPal and the Bale wallet.

An app is not finished at launch. Every year brings a new Android version and new store requirements, libraries move on, and users hit issues on phones you never tested. We monitor crash and performance reports, keep dependencies current and ship fix releases. The source code and store accounts always belong to you, so if another team ever takes over, you have no dependency on us.