Skip to main content

【Foxconn】 A Telehealth Platform Built to Make Medical Care Faster and More Convenient

Project Overview

Foxconn Telecare Platform

Foxconn's telehealth platform covers three parts — a patient app, an NHI-compliant physician reporting system, and a bedside tablet for clinical vitals. My contribution was the patient-facing app, which I built independently end-to-end with React Native + Redux-saga over a six-month project.

What I solved?

Patients had no self-service way to actually use telemedicine — book a doctor, join a video consultation, pay for it, link family members' accounts, and, for select consultations, share live vitals like blood oxygen without a separate clinical device. I independently built the patient app that covers all of that.

Who actually uses it?

Patients, through the app — for doctor appointment booking, video consultations, third-party login and payment, linking family member accounts via QR code, and real-time Bluetooth blood-oxygen monitoring during select consultations.

What results did it produce?

The app shipped and the project generated over 8M+ in revenue across its six-month build.

What key decisions did you own?

As the sole developer on the patient app, I owned the full frontend implementation:

  • Built the doctor appointment calendar UI.
  • Integrated the Jitsi React Native SDK for video consultations, using polling to control when a consultation ends.
  • Integrated third-party login (Facebook, Google, Apple), third-party payment, and QR-code scanning to link family member accounts.
  • Used React.memo to cut unnecessary re-renders on the appointment list.
  • Integrated a Bluetooth blood-oxygen meter via react-native-ble-manager for real-time readings during consultations.

What constraints did you face, and how did you trade off?

Working solo meant integrating several third-party SDKs — Jitsi for video, BLE for the blood-oxygen meter, three OAuth providers, and payment — into one coherent app rather than splitting that surface across a team. Ending a video consultation reliably was a specific problem: rather than trust SDK event callbacks alone to signal call-end, I used polling as a more robust source of truth, trading a small amount of latency for reliability. On the appointment list, I addressed rendering performance with React.memo at the component level instead of a heavier state-management restructure, since it solved the actual bottleneck without touching the rest of the data layer.

Project Details

FieldDetail
CategoryHealthcare / Long-term Care
ServicesTelehealth systems, App development, Digital product design
Tech StackReact Native, Redux-saga, Jitsi SDK, react-native-ble-manager
Year2023 – 2024
ClientHon Hai Precision Industry Co., Ltd. (Foxconn)