Back to selected work
HEALTHCARE · CROSS-PLATFORM DELIVERY

Profertility.

Healthcare workflows that connect patients, payments, and video consultations in one mobile app.

ROLEFlutter Developer
COMPANYAcuratech Global
PERIODNov 2022 — Dec 2023

Conceptual illustration of the product workflow, created for this case study.

01 / RESPONSIBILITY

What I owned.

Built healthcare workflows for Android and iOS, integrating REST APIs, payments, and video consultation features, and supporting production debugging and app store releases.

02 / CONTEXT

The problem behind the product.

The mobile experience needed to connect healthcare workflows to backend services, payment processing, and real-time consultations across two mobile platforms.

03 / SYSTEM DESIGN

Connecting the pieces.

Developed Flutter interfaces backed by REST APIs, integrated Razorpay payments and WebRTC consultations, and supported the app through profiling, debugging, and store releases.

  1. 01Patient workflow
  2. 02Flutter app
  3. 03REST services
  4. 04Payments & video
  5. 05Store release
Simplified logical flow; individual integrations have their own lifecycle.
04 / TRADE-OFFS & IMPLEMENTATION

The decisions that matter.

01

Connect the complete user journey

REST API integration, payment handling, and WebRTC consultations brought multiple service boundaries into a single mobile experience.

02

Build beyond the first release

Reusable components, performance profiling, and production debugging supported maintainability after initial implementation.

03

Carry features through delivery

Work extended to Android and iOS app store releases, connecting feature implementation with shipping responsibilities.

05 / DELIVERY

From architecture to working software.

  • Delivered healthcare workflows on Android and iOS.
  • Integrated Razorpay payments and WebRTC video consultations.
  • Supported production reliability and app store delivery.

Thinking about scale & reliability

For future iterations, I would examine recovery from network interruptions, clarity around pending payments, and degraded video-call quality. A connected healthcare journey needs understandable states when an external service becomes slow or unavailable.

Want to talk through the architecture?

Let’s get into the details
NEXT CASE STUDY

PinFacts