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 real-time operations dashboard for managing drivers, rides, and pricing across an entire ride-hailing fleet.
Short description:
The TaxiFi Admin Panel is the central control room for the platform — giving operators live visibility into every active ride, driver, and transaction, with tools to manage onboarding, monitor the network in real time, and adjust pricing on the fly.
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
BOND - Verified Connection App for College Students
A mobile-first connection platform solving the dating app crisis through
verification-first design and intelligent matching.
🎯 The Problem:
College students struggle with dating apps filled with bots, paywalls,
and shallow matching that doesn't work.
✨ The Solution:
BOND introduces three matching modes:
Connect (interest-based matching)
Vibe (personality compatibility)
Collab (project partnerships)
All verified members, no bots, real connections.
🛠️ Built With:
Figma for design system & components
Figma Make for code generation
React + Next.js for frontend
Supabase for backend & real-time messaging
Tailwind CSS for styling
📊 Design System:
Professional color palette (#2E7D99, #FF6B6B, #4ECDC4)
Complete typography system
20+ reusable components
8 fully designed screens
🚀 Features:
✓ Email/password authentication
✓ Profile setup with photo uploads
✓ 3 intelligent matching modes
✓ Swipe-based discovery interface
✓ Real-time messaging
✓ Match notifications
✓ User settings & preferences
✓ Verification system
Timeline: Built in 2 weeks for Config Makeathon using Figma's AI tools.
Made for the Config Makeathon with Figma Make, Figma Agent, and Supabase.
Live Website: https://cursor-growl-93665217.figma.site/
Twitter/X Post Link: https://x.com/SurajShah2005/status/2065863278753112486?s=20
LinkedIn Post Link: https://www.linkedin.com/posts/surajshahofficial07_configmakeathon-figmadesign-productdevelopment-ugcPost-7471627931799154688-7A_a/?utm_source=share&utm_medium=member_desktop&rcm=ACoAAE6M-BoBcHgroi8LWoEfIjzjeEdSSOeNp8k
#ConfigMakeathon #FigmaMake #ProductDesign #AppDesign #DesignToCode
#UIUXDesign #Startup #React #IndieHacker #AppDevelopment #TechInnovation
#FrontendDevelopment #Supabase #AIDesign #NoCode
Incredible!
Genzeb AI — Dashboard Design
Designed a dashboard concept for an AI-powered productivity platform focused on workflow automation, performance tracking, and real-time insights.
The realtime metrics panel alongside the call management charts is a smart layout choice. Keeping live data and historical context in the same view without it feeling crowded is tricky to pull off in dashboard design.
@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?