Mobile Capability demo JavaScriptHTMLCSS

An online-pharmacy & chronic-care app, built as a working sample

A functional sample medicine-ordering app — shop by condition, upload a prescription, get a transparent bill, track delivery, and set monthly refills. Built to show how we approach a regulated healthcare flow.

info This is a capability demo — a concept we built to show our approach in this area, not a live or shipped product.
RoleDesign + Build (sample)
Timeline2026
PlatformWeb (mobile-first)
TypeCapability demo

Context

Healthcare delivery — pharmacy, diagnostics, chronic-care — is one of the domains we're asked about most in India. The build problem is specific: you're selling regulated products, so a prescription check has to sit in the flow without killing conversion; a lot of the value is in repeat orders for people managing a long-term condition; and trust matters, so the pricing has to be legible rather than hidden behind a "view bill" tap.

We built this sample to show how we'd approach an online pharmacy end to end, before touching a client's codebase.

What we built

A working, mobile-first pharmacy app you can click through:

  • Shop by condition — chronic care, diabetes, heart & BP, wellness — plus search and a "buy again" row built from past orders.
  • A prescription (Rx) gate that doesn't block browsing. Regulated items are marked Rx and can go in the cart freely; the prescription is only asked for at checkout, once, with a clear "what happens next" (pharmacist verifies → cart is built → you approve → it ships).
  • A transparent bill — MRP, the discount, delivery fee and total are all shown on the cart screen, not hidden. Free delivery threshold surfaced inline.
  • Checkout — saved addresses, add-new, a delivery-slot picker, cash/UPI on delivery.
  • Order tracking — a status timeline (Confirmed → Prescription verified → Packed → Out for delivery → Delivered) so "where is my order" has a real answer.
  • Refills & chronic care — the piece that makes healthcare different from retail: a monthly repeat-delivery plan for medicines someone takes every month, with skip / deliver-now controls. Verify the prescription once, deliver on schedule.
  • Persistent state — cart, addresses and orders stick around in the browser across the session, so the demo behaves like a real app.

Plain JavaScript, HTML and CSS in one file, no dependencies — the point is the product thinking and the regulated-flow handling, not the framework.

What this demonstrates

  • Regulated-commerce UX — a prescription requirement folded into the flow at the right moment instead of a hard gate at the front door.
  • The chronic-care model — recognising that the real product for a long-term-condition user is a subscription, not a series of one-off orders, and designing for skip / pause / bring forward.
  • Pricing you can trust — the full bill on screen before you commit.
  • The build discipline we bring to client work — a real screen/router structure, real state handling, accessible controls, reduced-motion support, and a healthcare design system of its own (not this site's palette).

Medicine names in the catalogue are real generic drugs used only as sample data. Nothing is dispensed, prescribed or sold.

Try it

Open the live demo →

It opens in a new tab. It is not a pharmacy, places no real orders, and every price, stock figure and delivery detail is illustrative — a banner at the top of the app says so. This is a demonstration of capability, not a product we operate.

Want something like this built properly? See Mobile apps or start a project.

6
core screens: catalogue, cart, Rx upload, checkout, tracking, refills
illustrative
Rx
prescription gate on regulated items, deferred to checkout
illustrative
Demo
no real pharmacy, orders or medicines

Built with

JavaScriptHTMLCSSHealthcare UXPrescription (Rx) flowSubscription / refills
Next An operations dashboard, mocked for a small logistics team arrow_forward

Ready to build

Have something to build?

Send a few lines about your project. We reply within one business day with an honest read.

Start a project

Not ready to commit? Book a 15-minute build-readiness call instead — leave with a rough scope, the likely risks, and the next sensible step, even if we're not the right studio.

Best for founders with a product idea, rough spec, or existing app that needs senior builders.