Healthcare app development is two products

Healthcare app development is not a vertical we “do.” It is either clinic booking or healthcare procurement. Mixing them is how the schema, the admin, and App Review fail.

Naqrah.app books visits in Oman. WOSTA sources supplies in Saudi Arabia. Two products. Two markets. One studio. Flutter is the mobile default. React is the admin. One Supabase project. That stack is already written. This note is the split.

The split

• Clinic booking — the patient is on the phone. The clinic is at the desk. The service is a real visit. Money, if it moves, is Apple Pay or a card, not IAP. Proof: Naqrah.app, mobile, Oman.
• Healthcare procurement — the buyer is a clinic, hospital, or pharmacy. The supplier is at the desk, often across branches. The work is quotes and invoices. Proof: WOSTA, web, Saudi.

A healthcare marketplace, here, is medical supplies. It is not HealthCare.gov. It is not a doctor aggregator. If the brief mixes both jobs, Frame says no — or it says two products.

Clinic booking — Naqrah.app

Naqrah.app is a mobile booking platform for Oman’s private healthcare market. Patients search by specialty or location. They see services and prices before they book. Reviews are verified, and they appear after the visit only. Reminders go out ahead of the appointment. Points accrue on every visit: 100 points equal 1 OMR.

The clinic gets the other face. Appointments sit in one place. Bookings arrive online. Reception is not doing the day on WhatsApp.

This is not diagnosis. It is not a medical device. It is not telemedicine as published. We will not invent an EHR. We will not hang a stack on the name.

Healthcare procurement — WOSTA

WOSTA is web. Say web. A B2B procurement marketplace for Saudi healthcare. Clinics, hospitals, and pharmacies post requests for medical, dental, surgical, and lab supplies. Verified suppliers compete with quotes. Arabic is the primary voice. English is there. Sign-up is phone OTP. No email required.

Buyers compare offers, track quotes and invoices, and chat with suppliers. Suppliers run more than one warehouse or branch, each with its own requests, offers, and invoices. The supplier model is a subscription, not a cut of every sale. The homepage caption is the geography we will name: live in 10 Saudi cities, including Riyadh, Jeddah, and Dammam.

Do not call WOSTA a healthcare app in the store sense. It is a desk product. The chat is published as in-app. We will not upgrade that into an iPhone listing.

The clinic or supplier lives in the admin

Patients and buyers do not run the day from the consumer surface. The clinic confirms the slot. The supplier owns the quote. That work lives in a React admin on the same rows. There is no sync job. There is one appointment. There is one request.

If the customer is an organization — a clinic, a supplier with branches — the admin is also multi-tenant. Platform owner and clinic admin are not the same login. Row-level security is the gate. A second database for the dashboard is a mistake. That argument is already written. This note only names who sits where.

App Review extra care

Apple’s guideline 1.4.1 is the medical-specific line the stores note only named as a slower tail. Medical apps that could provide inaccurate information, or that could be used for diagnosing or treating patients, may be reviewed with greater scrutiny. Apps that claim health measurements from the phone’s sensors — blood pressure, temperature, glucose, blood oxygen, an x-ray — are not permitted. Apple wants a reminder to check with a doctor before medical decisions. If the product has regulatory clearance, submit the link with the app.

Booking a visit is not diagnosing. The moment the product offers a symptom checker, a camera measurement, or treatment advice, 1.4.1 applies. We do not build drug dosage calculators. Guideline 1.4.2 wants those from a manufacturer, a hospital, or an approved entity. Fluids has no such product.

Naqrah reviews are user-generated content. Guideline 1.2 wants a filter, a report path, a block, and published contact. Play wants a Health apps declaration. Non-device health listings carry a disclaimer: the app is not a medical device and does not diagnose, treat, cure, or prevent a condition. Clinical-service transactions do not use Play billing. A clinic visit is a real-world service. Guideline 3.1.3(e): Apple Pay or a card, not IAP.

Healthcare-class Play accounts belong on an Organization listing. That is already on the stores note. One clause is enough.

What we will not put in the first product

• HIPAA as a badge. We are not a US clinic vendor.
• PDPL certification. The law exists. We are not certified, and we do not give legal advice.
• Nafath as a Fluids case study.
• Diagnostic claims, treatment claims, dosage calculators.
• “We are a health-tech studio.”
• Hospital counts. Conversion lifts. A mixed booking-and-procurement MVP.

The 20-day offer is not a default for a regulated diagnostic device. Frame can say no. Write to us with the job — a visit, or a request for supplies — not with a vertical.