Project Info
This project did not submit a demo video on Devpost.
Inspiration
Drawing inspiration from platforms like Ebay, Craigslist, and Facebook Marketplace, which facilitate the exchange of goods and services, we envisioned a unique approach. Our goal was to redefine the transactional aspect by introducing a goodwill system, where users engage in mutually beneficial exchanges.
What it does
Our platform allows users to showcase items or services they are willing to share, seeking something in return. The essence lies in fostering connections as users can reach out to potential trading partners through their profiles to initiate a "trade."
How we built it
Utilizing Next.js, Material UI, and Prisma (SQL) for database management, we meticulously crafted the platform. The synergy of these technologies enabled a seamless and efficient development process. Challenges we faced While some team members were adept with the tech stack, opting for the latest version of Next.js posed a challenge. Despite a learning curve and increased time spent on documentation, we navigated through, emphasizing collaboration over individual familiarity. Accomplishments we're proud of For many team members, it was a journey of first-time experiences with Next.js and React. Despite two team members facing unforeseen obstacles, the remaining two exhibited commendable resilience. Our collective progress and expanded skill set showcase our commitment and determination.
What we learned
Exploring Next.js's unique features in web development, such as server components, enriched our understanding. Many of us gained insights into API interactions, including calling external APIs and creating our own within Next. Implementing a Google Authentication system restricted to @ucsc.edu domains added a layer of security and expertise to our skill set.
What's next
Our future goals include finding a suitable CDN service for hosting images. Although we encountered challenges due to paywalls within the available options, the importance of image hosting in our project's growth is undeniable. As we expand, securing a reliable CDN becomes a priority.
bartr
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Inter, a custom Google Font.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.
Analysis
View
Metric
- 32
- 28
- 26
- 13
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- CSSIn code
- Next.jsIn code
- ReactIn code
- SQLIn code
- TypeScriptIn code
5 of 5 appear in the indexed code.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
41 KB
Source files
30
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
apolyeti/bartr
42 files · 486 KB · @ d0ad570
Structure
Interface
14 files · 33%Screens, components and styles rendered to the user.
API & routing
6 files · 14%Request entry points: routes, handlers and controllers.
Application logic
5 files · 12%Domain rules, services and shared utilities.
Data & schema
6 files · 14%Schema definitions, migrations and data access.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- TypeScript92%
- SQL5%
- Markdown3%
- CSS0%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
package.json
npm · 30- @cloudinary/react
- @cloudinary/url-gen
- @emotion/cache
- @emotion/react
- @emotion/server
- @emotion/styled
- @mui/icons-material
- @mui/material
- @mui/material-nextjs
- @nextui-org/react
- @prisma/client
- @uploadthing/react
- axios
- cloudinary
- fs
- next
- next-auth
- node-fetch
- +12 more
Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.