Skip to content
← PortfolioLive at remedive.comNuxt.js · Healthcare

Remedive · Case study A medicine store and doctor booking in one Nuxt.js app.

Remedive sells medicine online and books doctor appointments in Bangladesh. I turned the HTML design into Remedive’s brand and built the whole Nuxt.js frontend on the backend developer’s REST API.

●Server-rendered store✓SSLCommerz checkoutDoctor booking
Routes55
Vue components52
API endpoints46
Booking routes14
My role
Front-end developer: branding, UI, Nuxt.js, REST API integration
Team
Me on the frontend, one backend developer
Scope
Medicine store, prescriptions, doctor booking
Stack
Nuxt 2, Vue, Vuex, Nuxt Auth, Axios
01 — Architecture

One Nuxt app, two businesses.

  • Make the HTML design look and feel like Remedive
  • Build every page of the store in Nuxt.js
  • Run every flow on the backend’s REST API
  • Book doctors in the same app as the pharmacy
Branded UI · 52 componentsRemedive lookteal palette · cards · slidersShared partsheader · side cart · searchForm fieldsphone · OTP · file uploadNuxt.js app · 55 routesMedicine storecatalog · cart · Rx · checkoutFind a doctorhospitals · slots · paymentMy accountorders · patients · pointsRESTapi.remedive.com · backendStore and orders15 endpointsDoctors and bookings13 endpointsAccounts and content18 endpoints
Nuxt.js app: Fifty-five routes cover the store, the doctor finder and a customer account. Product and category pages render on the server, so search engines read them.
02 — Key work

An HTML design, four working flows.

Design adaptation

An HTML design, rebuilt in Remedive’s brand

I took the HTML design and reworked it into Remedive’s look: the teal palette, the Medicine, Prescription and Help Line cards on the home page, and product grids. Then I polished it screen by screen down to phone width.

HTML/CSS · UI polish · responsive
The HTML design
  • Static pages, no live data
  • Markup repeated page to page
  • Not yet in Remedive’s brand
Rebuilt for Remedive ↓
remedive.com
  • Remedive’s teal look and cards
  • 52 reusable Vue components
  • Skeleton loaders while data loads
Nuxt.js + REST

A medicine store that takes real orders

Browsing, search, the cart and checkout all run on the backend’s store endpoints. Shoppers can also upload a prescription and let the pharmacy build the order.

Nuxt.js · Vuex · REST API
medicine store · flow
browse 24 categories, generics and manufacturerssearch Medicine search with its own results pagecart Add, remove, coupons and reward pointsrx Upload a prescription, track it in My accountpay SSLCommerz or cash on delivery✓ 15 store and order endpoints integrated
Appointments

Booking a doctor, from hospital to payment

Patients find a doctor by hospital, department or location, then pick a time slot from the doctor’s schedule. The booking is paid online and stays in My account.

Doctor booking · payments · REST API
find a doctor · flow
find Hospital, department or location filtersdoctor Profile with schedule, time slots and feespatientPick a saved patient or add a new onepay Online payment, then a confirmation pagetrack Appointment history in My account✓ 14 booking routes on 13 endpoints
Shared by both

One account for the pharmacy and the clinic

Sign-in is a one-time code by phone, or Google or Facebook. The same account holds orders, appointments, saved patients, addresses and reward points.

Nuxt Auth · OTP · social login
FeaturePageEndpoints
Phone sign-in/loginotp/send · auth/login
Google, Facebook/login/google/confirmauth/google/callback
Patients/my-account/patientspatient/list · create
Points/my-account/my-pointscart/point/apply
Addresses/my-account/addressaddress/add · edit
03 — The API boundary

46 endpoints, one frontend calling them all.

Pick a group to see what it covers.

15 / 46endpoints run the medicine store: the catalog, the cart, prescription orders, checkout and payment.
store/v1/item/liststore/v1/cart/item/addstore/v1/cart/coupon/applyorder/v1/user/order/prescription/addstore/v1/order/submitstore/v1/order/payment/start
I built

The whole frontend: the brand and UI work, every page and component, the Vuex store, sign-in, and the REST API integration behind every screen, with loading, empty and error states.

The backend developer built

The REST API at api.remedive.com: its endpoints, data, order and prescription handling, doctor schedules and payments.

Distinct endpoint paths the production frontend calls, read from its JavaScript; paging variants of one path count once.

04 — Screens

remedive.com, from search to cart.

Home, a product page, the medicine store, a category grid and the phone layout.

05 — Behind the build

Two developers, one split down the API.

How the work was split

The backend developer owned the API and its data. I owned everything the browser runs, from the brand work to the calls each screen makes.

What renders on the server

Nuxt renders the home, store, category and product pages on the server, with every product link in the HTML. Account pages and the cart load in the browser after sign-in.

Payments

Store orders go through SSLCommerz or cash on delivery. Appointments have their own payment step, and each flow returns to a status page that reads the result.

Smaller pieces

Shoppers can request a medicine the store doesn’t list or report a problem with one. Uploaded prescriptions can be PDFs, and they open in a preview.

Nuxt.jsVue.jsVuexNuxt AuthAxiosREST APISSLCommerzHTML5CSS3

Sources: my role as I describe it; routes, component and endpoint counts read from the production build served at remedive.com in November 2026; screenshots of its public pages, taken the same month. There is no repository history in these figures.

Lets work together

Need a successful project?

I’m available for freelance work.

Hire/Contact Me Now