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
I built a production-ready mobile app in 3 days using AI (Everything from UI/UX to production-ready).
It's a Rare Coin Value Analyser, you snap a photo of a coin, and the app identifies it and detects its current market value. Real users, real coins, real valuations.
The stack:
→ React Native (cross-platform mobile)
→ Supabase (auth, database, storage)
→ n8n + Gemini (the AI workflow that analyses the coin image and pulls market pricing)
3 days. Zero to production ready. Solo.
This is what AI-augmented development actually looks like in 2026. The bottleneck isn't engineering anymore, it's clarity of thought and shipping speed.
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
recently shipped a mobile App for the french real estate market. fully designed and builded by me in React Native..
I think I'll take more projects like this.
What do you guys think of the UI ?
@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
🌱 Smart Farming Dashboard, designed to grow results.
-> Real-time field intelligence metrics
-> Optimal planting condition tracker
-> Live sensor monitoring across zones
-> 24-hour weather trend insights
-> AI-powered yield predictions
Clean. Smart. Built for farmers who think ahead. 🚜
Smart use of data + agriculture.
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?