The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Share Pray’s developer, Arsenii Lisunov, says he built the prayer-request app with Kotlin Multiplatform across its iOS and Android clients and its backend. The project shares business logic such as community handling, filtering, validation, and purchase integration, while still relying on platform-specific work for sign-in, notifications, and other integrations. It is a practical example of how one builder applied KMP—not a measured comparison of development speed or code reuse.
What Share Pray does
Lisunov describes Share Pray as an app for sharing prayer requests at different levels of privacy. A user can post publicly, share with a community, or keep a request private. Users can create or join communities, add requests to a personal praying list, and mark requests as answered. The author says answered requests remain visible for a while so participants can see the outcome.
Requests can be tagged and filtered by tag or community. According to Lisunov, each user can create up to five communities and join others. The app also includes feedback submission and a reporting flow. Its admin panel lets moderators hide spam, ban toxic users, and respond to reports and feedback; urgent items are sent to moderators through a Telegram bot integration.
How Kotlin Multiplatform was used
Lisunov says Kotlin Multiplatform was used for both mobile clients and the server. The Android code is described as Kotlin/JVM, while the iOS app uses Kotlin/Native binaries. Compose Multiplatform provides the UI, and shared modules contain business logic.
#1 Best Overall
The shared areas the author names include community logic, filtering, admin-panel data, and RevenueCat purchase integration. The report also says the server reuses models and validation logic. These are the project author’s descriptions; they are not the result of an independent code audit.
The architectural appeal is straightforward: a developer who prefers Kotlin can keep much of the application’s rules in shared code instead of implementing the same behavior separately for iOS and Android. However, the report gives no shared-code percentage, development-time comparison, performance benchmark, or measured maintenance savings.
Rank #2
What still needed platform-specific work
Sign-in and account linking
Lisunov identifies authentication as the trickiest part of the project. Google Sign-In and Sign in with Apple involve platform-specific handoffs, while the backend must validate tokens and link accounts. A shared codebase can centralize related application logic, but this project still required platform-aware integration work around identity providers.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated 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 matchNotifications and moderator alerts
The author says notifications and the Telegram integration needed platform-specific glue. The logic that triggers a notification and the content of messages could be shared, but connecting that logic to platform services or the Telegram bot was not entirely common code.
In-app purchases
Purchase integration was another challenge. Lisunov says RevenueCat made it less difficult than implementing StoreKit and Google Billing separately and keeping the two flows synchronized. That is his experience with this app, not a general guarantee that a purchase SDK removes platform-specific work.
Compose Multiplatform and the iOS interface tradeoff
Share Pray uses Compose Multiplatform for its UI. Lisunov’s stated tradeoff is that the iOS interface can feel less native because Compose Multiplatform uses its own rendering engine rather than UIKit widgets. He considers that compromise worthwhile for the code sharing it enables and compares the choice with Flutter.
That is a preference, not a universal verdict on the look or performance of Compose Multiplatform. Teams deciding whether to use it should weigh how important a UIKit-native feel is against the value of sharing UI and application logic. The project report does not provide controlled comparisons with Flutter or fully native Swift and Kotlin apps.
Free tools Windows power users keep installed
One-click scans. No signup required.
What this project suggests when evaluating KMP
Share Pray illustrates that Kotlin Multiplatform can be applied beyond a shared mobile library: in Lisunov’s account, it supports the clients and backend, with some models and validation reused across the system. Whether that design fits another product depends on team preferences and on the boundaries between shared rules and platform services.
Best Value
- Consider it when: the team prefers Kotlin and wants to share substantial business logic across clients, or reuse server-side models and validation.
- Plan for platform work: identity-provider handoffs, notifications, and integrations may still need platform-specific implementation.
- Evaluate the UI separately: sharing UI can come with a different iOS look and feel than UIKit-native components.
- Assess purchase complexity: a service such as RevenueCat may simplify coordination, but the report does not establish that it eliminates store-specific concerns.
Template and release status
Lisunov says he extracted reusable pieces—including community features, admin tools, filtering, RevenueCat wiring, and related scaffolding—into an open-source GitHub template named Poster. The available account does not establish the repository’s current contents or license, so check those details in the repository before adopting it.
At the time of Lisunov’s report, he said the iOS app was live in the App Store and Android was in open testing on Google Play, with a full release expected later. That is a dated status report, not confirmation of either app’s availability today.
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.
