Project Info
Inspiration
Modern calendar applications are frequently used to manage, track, and store an individual's schedule(s); however, there is a proper system to link schedules amongst friends, making it a hassle to coordinate shared events with one another.
What it does
Our application allows users to coordinate events with friends by allowing them to upload personal .ics files from modern calendar applications (ex. Google Calendar). Users can register for accounts and add friends to access their availabilities and schedule (in-person) meetings. Additionally, users can be recommended events based on their preferences and their (stored) meeting history.
How we built it
We created a Next.js 13 application, using Tailwind to style our webpage. We integrated CockroachDB using the Prisma ORM to manage user administration (register, login). To both find available meeting times and recommend potential events between users, we queried the users' event and meeting history and sent it to TogetherAI's
Challenges we ran into
We ran into various issues in setting up the CockroachDB database using the Prisma ORM, as our groupmates only had experience with nonrelational database management systems (ex. MongoDB). A lack of documentation for the new Next.js 13 with our technologies combined with a need to translate and parse .ics files and unfamiliarity with TogetherAI's API, caused many roadblocks along the way to our final project.
Accomplishments we're proud of
We were able to implement all of the features that we originally planned, resulting in a minimum viable product that highlights our projects' main premises. We had a discouraging slow start to project development, so we're all extremely proud of our turnaround in creating a functional web application with previously foreign technologies.
What we learned
The greatest takeaway for our group was the importance of technology documentation. A lot of our early struggles were eventually solved once we understood the documentation, leading to lots of time wasting that could have been avoided.
What's next
We'd like to implement more direct connections to modern calendar applications, specifically Google Calendar, given the availability of Google Calendar's API. Additionally, we'd like to rework the application's UI, creating a more visually appealing interface for users to streamline their schedules around.
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
- 27
- 27
- 24
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
- JavaScriptIn code
- Next.jsIn code
- PostgreSQLIn code
- ReactIn code
- SQLIn code
- Tailwind CSSIn code
- TypeScriptIn code
8 of 8 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
34 KB
Source files
22
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
steeevin88/schedulerAI
29 files · 211 KB · @ f96716f
Structure
Interface
9 files · 31%Screens, components and styles rendered to the user.
+1 moreAPI & routing
5 files · 17%Request entry points: routes, handlers and controllers.
Application logic
1 file · 3%Domain rules, services and shared utilities.
Data & schema
4 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
- TypeScript69%
- JavaScript24%
- Markdown4%
- SQL3%
- CSS0%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
package.json
npm · 18- @next/font
- @prisma/client
- axios
- next
- node-ical
- pg
- prisma
- react
- react-dom
- +9 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.