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 worked on enterprise-level React applications for the airline industry, contributing to customer-facing products used by thousands of users.
One of my key projects involved refactoring and enhancing the seat map experience for Copa Airlines. I participated in the full development lifecycle, from analyzing requirements and implementing new features to testing and deploying changes to production. The project required building reusable React components, integrating APIs, managing application state, and optimizing rendering performance in a highly interactive interface.
In addition, I have experience maintaining existing applications, resolving production issues, implementing UI enhancements, and collaborating closely with product owners, QA engineers, designers, and backend developers to deliver reliable and scalable solutions.
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
@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
Finally put all my work in one place.
This is a live showcase of 24 web applications and interactive 3D concepts I've built. Instead of just static screenshots, everything is built to show how I handle animations, responsive UI, and performance optimization (especially with Three.js and Framer Motion).
The full setup and live links are up on my profile. Let me know what you think of the 3D components!
24 projects in one place is a serious body of work. The mix of 3D and web apps in the grid tells a story on its own before anyone clicks into anything.
UI/UX Designer and Web Developer.
nice
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?