Rentify

Our logo

Inspiration

Neighborhoods today feel disconnected. People buy expensive tools, equipment, and gear they use only once or twice a year, while others nearby need those exact items but can’t afford or don’t want to buy them. Apps like Nextdoor help people talk, but nothing helps people share or rent items reliably, safely, and in an organized way.

We wanted to build something that strengthens communities, reduces waste, saves money, and helps neighbors help each other — all while giving people a way to earn passive income with the things they already own.

What it does

Rentify is a neighborhood rental marketplace built around trust, verification, and community.

With Rentify, neighbors can: • List items, gear, tools, or even spaces to rent out • Browse what’s available nearby • Request to rent with a secure and simple application • Approve or decline rental requests as an owner • Track active rentals, outgoing, and incoming requests • Message neighbors to coordinate pickup and returns

Everything stays hyper-local — the entire experience is designed around your block, your neighborhood, and your community.

How we built it

RRentify is built using a full-stack architecture that mixes a modern Next.js frontend with a fast, modular Go backend.

🟩 Frontend — Next.js (App Router + Modular Components)

We built the entire user interface in Next.js 14 using the App Router. The frontend is fully modular: • Reusable UI components (ListingCard, RequestCard, ActiveRentalCard) • A shared AppShell layout (Sidebar + Header + Main content) • Dynamic routes (/listings/[id], /requests/outgoing, /requests/incoming) • TailwindCSS for styling and responsiveness

This allowed us to build a true marketplace UX with minimal duplication.

⸻

🟦 Backend — Built in Go

We wanted the backend to be: • Fast • Extremely lightweight • Easy to deploy anywhere • Able to scale when the platform grows

So we built a custom backend using Go (Golang).

We used:

Go Fiber (Gin)

A minimalist, high-performance web framework that allowed us to create: • REST API routes • Middleware • Request validation • Struct-based models • Simulated database storage (in-memory for now)

Challenges we ran into

• Making the UI modular: Ensuring every part of the system could be reused later meant carefully structuring components and layouts.
• Simplicity vs. Power: It was challenging to keep the app simple enough for everyday neighbors while still supporting approval flows, messaging, and listings.
• Routing complexity: Managing deep routing (/requests/outgoing, /listings/[id], etc.) and making sure the sidebar highlights correctly took careful planning.

Accomplishments that we're proud of

• A fully modular, scalable architecture that is production-grade
• A smooth end-to-end rental flow: browsing → applying → approval → active rental
• Clean, beautiful UI/UX inspired by top modern apps
• A sidebar and layout system that behaves like a real marketplace product
• A very fast Go backend, which is hosted on a Docker Image

What we learned

• How to design two-sided marketplace flows (renter + owner)
• How to architect a real app using Next.js App Router with modular components
• How to structure pages and components so scalability is easy
• How important consistency and information hierarchy are in UI/UX
• The value of designing products around community, trust, and locality