Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchShare Pray is a prayer-request app whose creator, Arsenii Lisunov, says he built its iOS and Android apps and its backend with Kotlin Multiplatform (KMP). His account is a practical example of what that setup can share—and where platform-specific work still remains. It is one developer’s project report, not an independent code audit or a measured comparison with other app frameworks.
What Share Pray does
Lisunov describes Share Pray as a place to post prayer requests publicly, within communities, or privately for the author’s own use. People can create or join communities, add requests to a praying list, and see how many people are praying for a request. A request can be marked answered; the report says answered requests remain visible for a period so participants can see the outcome.
As an Amazon Associate I earn from qualifying purchases.
Requests can be tagged and filtered by tag or community. According to Lisunov, a user can create up to five communities and join others. The app also includes feedback submission and request reporting. Its admin panel lets moderators hide spam, ban toxic users, and respond to reports and feedback. Urgent reports and feedback are routed to moderators through a Telegram bot, he says.
How Lisunov used Kotlin Multiplatform
Lisunov says he used KMP for both mobile clients and the server. In his description, the Android app uses Kotlin/JVM, while the iOS app uses Kotlin/Native binaries. Compose Multiplatform supplies the UI, and shared modules contain business logic. The shared areas he names include group logic, filtering, admin-panel data, and RevenueCat purchase integration; he also says the server reuses models and validation logic.
#1 Best Overall
The aim was to avoid maintaining duplicate iOS and Android logic while continuing to work primarily in Kotlin. The report does not give a percentage of code shared, nor does it provide performance measurements, development-time figures, or maintenance comparisons. Its details describe this project rather than establishing what another KMP app will share.
What remained platform-specific
Sharing business logic did not remove the need to handle platform differences at the edges. Lisunov identifies authentication as the trickiest part: Google Sign-In and Sign in with Apple involve platform-specific handoffs, while the backend must validate tokens and link accounts. The report presents this as his implementation experience, not a universal estimate of KMP authentication difficulty.
Rank #2
Notifications and the Telegram integration also needed platform-specific glue, according to the author. He says the triggering logic and message content could be shared even though platform connections could not. This division—shared rules and data, platform-specific integrations—is a more useful expectation than assuming a single codebase means identical code everywhere.
Recommended Free Tools
Compose Multiplatform on iOS: the tradeoff
Lisunov says Compose Multiplatform on iOS can feel less native because it uses its own rendering engine rather than UIKit widgets. He considered that tradeoff worthwhile for the amount of code sharing in his project, and compares the approach with Flutter. That is a qualitative judgment from one builder; the report does not include user testing or a controlled comparison of native feel.
For a team evaluating the approach, the decision is less about whether KMP is simply “native” or “not native” and more about the desired balance: how much UI and business logic to share, how closely the iOS interface should follow UIKit conventions, and how much platform-specific work the team is willing to keep.
Purchases and other integration work
In-app purchases were another challenging area in the report. Lisunov says RevenueCat made the work easier than implementing StoreKit and Google Billing separately and keeping the two purchase flows synchronized. He also describes the purchase integration as part of the shared project scaffolding. The report does not quantify effort saved or provide a side-by-side implementation comparison.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Release status and reusable project material
At the time Lisunov published his account, he said the iOS app was live in the App Store and Android was in open testing on Google Play, with a full Android release expected later. That is a dated status report, not confirmation of present availability; check the relevant store listings for current status.
Lisunov also says he extracted reusable components—including groups, admin tools, filtering, RevenueCat purchase wiring, and related scaffolding—into an open-source GitHub template called Poster. The report invites developers to use it as a starting point or reference. Its current contents and license are not confirmed here, so inspect the repository before adopting or redistributing any code.
Best Value
What this project can—and cannot—tell you
Share Pray illustrates a plausible KMP architecture spanning client and server: shared domain logic and models, Kotlin on both mobile platforms, and platform-specific handling where operating systems or services require it. It also makes the costs visible: sign-in handoffs, notifications, and UI feel still deserve deliberate evaluation.
The account does not establish that KMP will reduce costs, improve performance, or yield a particular code-sharing ratio for another team. Those outcomes depend on an app’s UI, integrations, team skills, and requirements. A useful evaluation should identify which rules and data models genuinely belong in shared modules, then separately assess the native behavior and service integrations each platform needs.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
