The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
A Modern Doctor Appointment Platform š©ŗ
Booking a doctor's appointment shouldn't be a headache for the patient or a logistical nightmare for the clinic. I recently engineered a full-stack appointment booking system designed to make healthcare access as frictionless as possible.
What this platform delivers:
š¹ Seamless Scheduling: An intuitive UI that allows patients to find available slots and book appointments in seconds.
š¹ Provider Dashboard: A robust backend system for doctors and clinic staff to easily manage their daily schedules and patient flow.
š¹ Automated Management: Features designed to reduce no-shows and streamline the entire booking lifecycle.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Pip is a zero-friction health companion built to turn tracking your health (SYMPTOMS, DIET AND MORE) into clinical clarity. It abandons rigid 0ā10 numeric scales and replaces them with a compassionate, glanceable interface.
ā¤ Why It Was Built
Pip was born out of pure personal necessity. I built it because it was something I desperately needed, and something a few close friends and someone incredibly close to my heart needed too. I wanted to strip away the clinical coldness of modern software and create something beautifully simple that could be truly, deeply helpful on someone's hardest days
ā ļø The Problem
Traditional health apps suffer from "Data Collection Theater." They force users suffering from chronic illness or fatigue to rate dozens of variables daily, causing severe decision fatigue.
Worse, they act as data sinks, dumping raw, chaotic charts onto doctors. In a high-stakes, 15-minute medical consultation, physicians don't have the time to audit raw logs. They need high-yield, synthesized clinical signals, not noise. Pip bridges this gap by assuming "bad days are the default," capturing symptoms effortlessly, and compiling them into a clean, one-page summary sheet.
š The Figma Workflow Pipeline
To bring Pip to life, I leveraged the Figma ecosystem:
Figma Weave: Used to iterate and generate the visual asset layers for Pipās mascot.
Figma Agent: Brainstormed layouts directly on the canvas, instantly pairing elegant fonts and organizing simple, stress-free forms.
Figma Make: Instantly turned those canvas designs and components into a live, fully working, and responsive web application while allowing rapid iteration.
PRODIGI Studios' Internal Tool ā Public Showcase
We love Rive for interactive animations. But recording them for portfolios and clients? Painful.
So we built our own internal Rive Player.
Not a hack. Not a screen recorder. A purpose-built web tool our designers actually use every day.
We're shipping many new features as well soon.
But first ā we want your feedback.
If you work with Rive, what's one feature you wish existed?
And yes ā the talking avatar in our video demo?
That came from our upcoming SaaS platform (launching soon).
It generates up to 10 minutes of continuous AI talking head content ā lip-sync, natural pacing, no green screen.
Explainer videos. Course creators. Agencies who don't want to be on camera.
We'll share more very soon.
Youtube Video: https://youtu.be/FfcEoQsWMoU
Repost if you've ever struggled to record interactive animations.
ā¢ Jun 13
@figma x @contra #configmakeathon
Minor update: I finally got the QR Code scanner in the Check-In HUD tab to be fed live data from the current device's camera and the canvas needs to be alive.
Faced a few difficulties implimenting this, but I finally got it right.
The QR scanner had a critical bug: the scan function was wrapped in useCallback with [onScan] as dependency. The useEffect depended on [scan]. This created a situation where:
Every time onScan prop changed reference (which happens on every render since onScan is an inline arrow function), scan got recreated.
useEffect then re-ran, stopping and restarting the camera/scan loop.
This caused an infinite restart loop.
But more critically, the scan function was used as a useCallback but useEffect also depended on scan.
When the parent component passed a new onScan reference on each render, it triggered scan to be recreated, which then caused the effect to re-run and start a fresh camera stream every time. This created multiple overlapping streams and breaks the scanner functionality.
The solution was to move scan directly into the useEffect so it's not a separate dependency, and use a ref to store the onScan callback to prevent unnecessary recreations.
The root bug: scan was in useCallback([onScan]) and useEffect([scan]).
Next? I'll be fixing the register for event process (from the landing) and also the copy event link button at the top right corner of the event card modal, to display a link and ID needed by a user so they can be ale to find and register for an event.
@_radnolan #ConfigMakeathon #buildinpublic @tranmautritam @janm_uiux @thedesignely
Trending
Claude
Claude has entered the design space. How are you using Claude Design?
Contra University
Learn from expert creatives how to earn more using next-gen AI tools.
MagicPath
The canvas is infinite, and exploration is becoming the workflow. How are you using MagicPath?
creativeaiflow
Creative AI workflows are evolving. What tools do you use, and what are their strengths and weaknesses?
freelancerlife
Freelancer life is wins, pivots, and everything in between. Whatās yours right now?