Project Info
Inspiration
We searched the internet for ideas and came across several medical-related ideas. A lot of the ideas involved the usage of AI, helping improve the efficiency of medical health workers, etc. Then we started brainstorming, what if we created a website that helped patients remember exactly when they experienced symptoms?
What it does
Pulsify is a website that takes in user input (text/speech) and automatically logs down the symptom felt on the right day in the calendar. Through this way, the patient can accurately "recall" when symptoms occurred when visiting health professionals. This ensures a higher chance for quicker and accurate diagnosis. There's other features like the dark/light mode, login/logout, heat map, and live chat. The heat map color codes separate calendar based on how many symptoms were logged on that day. The live chat is an AI bot that takes in user input. They can also log in symptoms for you in the calendar.
How we built it
We started by inputting the basic folders and files into VSCode. Then, we created our own individual branches and began coding. Whenever we added a feature, we saved, committed, and pushed to our own branches. After we achieved most of our baseline features, we merged the 3 branches together and began debugging the main branch together as a group. We maintained constant communication to help speed up our debugging process.
Challenges we ran into
We ran into merge conflicts. We all independently worked on our own branches, but didn't merge the changes while they were still little. As a result, it was more difficult to navigate through all the new files and folders when debugging and adding new features. For instance, we had accidentally created 2 different aspects of the navbar separately and they overlapped each other, preventing the interaction of some buttons.
Accomplishments we're proud of
We are all relatively very new to hackathons, so we're proud of producing a website with this much capability in a short time. We're also proud of our drive to keep coding through the night and motivation to fix our bugs.
What we learned
Not only did we learn how to code in new languages or build new features we've never done before, we learned how to collaborate efficiently. Whether it was through how GitHub operates, we learned that taking initiative is key to improving and developing our project. Regular communication and group agreement on ideas is equally as important as to prevent multiple people from working on the same things together.
What's next
We plan on debugging and beta testing the website for further improvements. Once that is done, we plan to add more features or expand our project scope, such as the following: Turn this website into a downloadable app available on all platforms/browsers and devices Improving the features to make usage of the website more intuitive for users Improve the accessibility within our website (apply WCAG AA standards) Add on MFA for extra security
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.js. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
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
- 23
- 20
- 12
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
- Google GeminiIn code
- JavaScriptIn code
- MongoDBIn code
- Next.jsIn code
- ReactIn code
- Tailwind CSSIn code
- TypeScriptIn code
- HTMLClaimed
8 of 9 appear in the indexed code. 1 claimed on Devpost could not be matched to code, which may simply mean the tool leaves no trace in the repository.
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
139 KB
Source files
40
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
misotofu7/personal-health-log
55 files · 905 KB · @ 077b1a5
Structure
Interface
25 files · 45%Screens, components and styles rendered to the user.
API & routing
7 files · 13%Request entry points: routes, handlers and controllers.
Application logic
6 files · 11%Domain rules, services and shared utilities.
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
- JavaScript87%
- CSS7%
- Markdown5%
- TypeScript1%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
package.json
npm · 18- @auth0/nextjs-auth0
- @google/generative-ai
- better-sqlite3
- clsx
- lucide-react
- mongodb
- next
- react
- react-dom
- tailwind-merge
- uuid
- +7 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.