SprosiVracha

A mobile app for an existing service

In 2024, we launched the SprosiVracha app for Android and iOS. The product already operated on the web; the task was to bring its workflows to mobile while keeping one account across devices.

• Create a clear mobile interface
• Build a Laravel backend for the app and move to a distributed architecture
• Provide the existing doctor and patient workflows
• Synchronise the app and website so customers can use the same account

Users and consultation formats

The audience includes adults in remote areas and parents who find repeated clinic visits difficult. The service makes it possible to ask a question from home.

A question can receive answers from several doctors, giving users a way to compare professional opinions within the service.

The product supports free and paid public questions. In the workflow described in the case, free questions were published within five days, while paid questions appeared immediately.

Consultations remain open for seven days for follow-up questions and attachments, including test results and other documents.

A separate option provides a private chat with a doctor.

Doctors have to verify their qualifications before consulting. The platform supports around fifty specialties, from general practice to surgery and cardiology.

Navigation, typography and onboarding

People need to understand what happens after each action and find that the same controls behave consistently across screens.

We used branded typography and a clear hierarchy so that the important actions and information are easy to recognise.

Blue and green form the visual foundation of the app.

• Onboarding screens introduce the product on first launch
• Search, question creation and document attachments support the main user task
• Push notifications bring users back to updates

Architecture and shared accounts

The original website used Zend Framework. For the mobile product, we introduced Laravel and React Native.

We moved from a monolithic approach to distributed services that can run independently on different servers.

We organised separate storage for documents, test results, avatars and other files, separating file handling from the main service workflows.

The app uses a different backend but shares the database with the website. Users can therefore sign in with the same account across devices.

Doctor and patient functionality

Registration distinguishes doctors and patients. Each role receives its own functions, introduced through onboarding.

The app includes public questions, anonymous chat, ratings, reviews, payments, a question editor, search, operation history, notifications and comments. Doctors and patients can view each other’s profiles.

Doctor ratings are recalculated from several factors, including answers, activity, reviews and profile completeness.

We integrated Robokassa for service payments and implemented doctor payouts. Transaction history is available in the personal account.

After registration and profile completion, doctors submit education documents and certificates matching their selected specialties for review.

The referral programme gives partners individual links and account statistics. Both users and doctors can invite others under the product referral rules.

Moderation and content management

• We built a blog for medical information
• The administration panel provides content management and moderation

A central implementation task was coordinating public questions, private chats, attachments, payments and professional verification. We connected those workflows to the personal accounts and the existing platform.

The result

The mobile version retains the main web service functions and makes them accessible from a phone. It was released on the App Store, Google Play and RuStore.

For doctors, the remote format provides a way to work with patients in different locations and expand their practice.

SprosiVrachaWatch videoVK Video