UniSwap

Trade Skills, Not Money.

Comment

UniSwap: Democratizing Student Knowledge

💡 Inspiration

The idea for UniSwap was born from a common paradox I observed on campus: The "Cash-Poor, Skill-Rich" Student.

I noticed that while many of us are broke and cannot afford expensive tutors or professional services, we possess incredible skills ourselves. One student might be a Python wizard failing Calculus, while their neighbor is a Math major struggling to code.

I realized that the only thing missing was a marketplace. Existing platforms like Fiverr are too transactional and money-focused. I wanted to build a closed-loop ecosystem where Knowledge is Currency. The goal was simple: facilitate the exchange of skills without a single Rupee changing hands.

⚙️ How We Built It

We utilized Base44 to rapidly prototype and deploy a full-stack solution within the hackathon timeframe.

1. The Logic (Backend): We structured a relational database to handle the many-to-many relationship between users and skills. The core value exchange equation we modeled is: $$Value_{transaction} = Skill_{provider} \iff Skill_{receiver}$$ where $$Cost_{monetary} = 0$$

We implemented a "Karma System" to gamify the experience. Every successful swap increments a user's reputation score: $$Karma_{user} = Karma_{current} + \Delta_{verified_swap}$$ This ensures trust within the community—users with higher Karma are seen as reliable mentors.

2. The Interface (UI/UX): We started with a minimalist functional design but quickly pivoted to a "Vibrant Dark Mode" aesthetic to appeal to our Gen-Z user base. We utilized:

  • Glassmorphism: To give cards a modern, frosted-glass depth.
  • Masonry Grids: For a dynamic, Pinterest-style feed of skills.
  • Neon Accents: To highlight "Call to Action" buttons and keep engagement high.

🚧 Challenges We Faced

The biggest challenge was balancing aesthetics with functionality under strict credit limits.

  • The UI Struggle: Our initial MVP was functional but visually "plain." We learned that for a student-focused app, the "Vibe" is just as important as the code. We spent significant time iterating on the CSS (via Base44's styling engine) to move from a corporate look to a modern, engaging "Cyber-Social" interface.
  • Logic Routing: Connecting the "Request Swap" button to the correct user profile while maintaining data privacy was tricky. We had to ensure that the "Teacher" receives the request without exposing their private data to the whole public feed.

📚 What We Learned

Participating in the NIAT × Base44 Hackathon taught me that Low-Code does not mean Low-Effort.

  • I learned how to think like a Product Manager: prioritizing features (like the Trust System) that actually matter to the user.
  • I deepened my understanding of Relational Databases: linking Users, Skills, and Reviews efficiently.
  • Most importantly, I learned the power of Iterative Design—not settling for the first version, but pushing the design until it felt like a product I would actually use myself.

🚀 What's Next for UniSwap?

We plan to introduce AI-based Matching, where the algorithm suggests swaps based on your syllabus. If you have an exam coming up, UniSwap will automatically suggest a tutor who has already passed that subject with an 'A'.

Built With

  • base44
Share this project:

Updates