Project Info
This project did not submit a demo video on Devpost.
Inspiration
A few weeks prior to this hackathon, our team was struggling to plan a trip to Japan. That's when we realized how nice it would be to have a tool that plans the trip for us! So, we decided to take on the challenge to build this ourselves.
What it does
WanderWise uses an AI model to generate itineraries based on users' desired destination and timeframe. In addition to itinerary generation, WanderWise's simple and clean design makes it easy to visualize your itineraries the next time you plan to travel.
How we built it
We used React to build the frontend and Express for the backend server. We utilized MindsDB to link our real-time data stored in CockroachDB to an OpenAI model API.
Challenges we ran into
It was our first times using MindsDB and CockroachDB, so it took a while for us to get started and familiarize ourselves with the new technology. Also, integrating all different technologies caused unexpected issues.
Accomplishments we're proud of
/
What we learned
We were able to connect our MindsDB application to our CockroachDB database. With that, we were able to take advantage of the AI workflows that MindsDB offers. This is just one example the many new technologies we've learned to use while building this project.
What's next
We have several goals for our app in the future: Persist itinerary data for different users so that users can look at their previously generated itineraries Improved UI for better UX (e.g. adjustable schedules, multimodal representation for landmarks) Adjusting queries to match users' budget as well as displaying the estimated costs Share/Save/Export itineraries Calendar integration for a better curated response
WanderWise
Inspiration
A few weeks prior to this hackathon, our team was struggling to plan a trip to Japan. That's when we realized how nice it would be to have a tool that plans the trip for us! So, we decided to take on the challenge to build this ourselves.
What it does
WanderWise uses an AI model to generate itineraries based on users' desired destination and timeframe. In addition to itinerary generation, WanderWise's simple and clean design makes it easy to visualize your itineraries the next time you plan to travel.
How we built it
We used React to build the frontend and Express for the backend server. We utilized MindsDB to link our real-time data stored in CockroachDB to an OpenAI model API.
Challenges we ran into
It was our first times using MindsDB and CockroachDB, so it took a while for us to get started and familiarize ourselves with the new technology. Also, integrating all different technologies caused unexpected issues.
Accomplishments that we're proud of / What we learned
We were able to connect our MindsDB application to our CockroachDB database. With that, we were able to take advantage of the AI workflows that MindsDB offers. This is just one example the many new technologies we've learned to use while building this project.
What's next for WanderWise
We have several goals for our app in the future:
- Persist itinerary data for different users so that users can look at their previously generated itineraries
- Improved UI for better UX (e.g. adjustable schedules, multimodal representation for landmarks)
- Adjusting queries to match users' budget as well as displaying the estimated costs
- Share/Save/Export itineraries
- Calendar integration for a better curated response
Analysis
View
Metric
- 15
- 13
- 2
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
- ExpressIn code
- HTMLIn code
- JavaScriptIn code
- ReactIn code
- OpenAIClaimed
- PostgreSQLClaimed
- SQLClaimed
5 of 8 appear in the indexed code. 3 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
23 KB
Source files
21
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
winnie-zhu/calhacks-wanderwise
31 files · 279 KB · @ af17fc9
Structure
Interface
12 files · 39%Screens, components and styles rendered to the user.
Application logic
7 files · 23%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
- JavaScript76%
- CSS14%
- Markdown8%
- HTML2%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
frontend/package.json
npm · 15- @react-oauth/google
- bootstrap
- jwt-decode
- react
- react-bootstrap
- react-dom
- react-router-dom
- +8 more
backend/package.json
npm · 11- axios
- body-parser
- cors
- dotenv
- express
- express-async-handler
- mindsdb-js-sdk
- nodemon
- pactum
- sequelize
- sequelize-cockroachdb
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.