Project Info
This project did not submit a demo video on Devpost.
Inspiration
Our inspiration started with us both seeking new living accommodations or looking for a new housemate to move in for next year.
What it does
Our mobile app takes in user admitted data during the profile set up stage to showcase who you are as a person and as a potential roommate/housemate. Others can then view your engaging profile with our swiping feature to which you can express interest and reach out. If both users swipe right, there is a match! This match will show up on our feed with their contact information.
How we built it
We built our app using React Native, Expo, and TypeScript.
Challenges we ran into
Setting up our app was a huge challenge as we never used these frameworks before. We would often run into configuration issues, caching stalls, and Expo CLI / Metro bundler errors.
Accomplishments we're proud of
We are proud of not giving up on our initial idea even though setting up the app took way longer than anticipated. It was an ambitious project and it wasn't easy to work on it with just two people, which made our progress all the more rewarding.
What we learned
We learned new frameworks and how to integrate our ideas into a mobile app!
What's next
We would love to implement a messaging feature next. Stay tuned.
BananaBunks
npm run start to automatically run all the right commands
MVP:
-
let a user make an account and login [DONE]
-
outline edit profile workflow on the frontend
-
store user data like living prefrerences, hobbies, etc. in JSON in firestore [DONE]
-
implement UI from figma for edit profile pages, main profile page, swiping page, matched page [DONE]
-
once you have a lot of user data created, implement simple swiping functionality where you're just listing all other users on the platform in arbitrary or sequential order [DONE]
-
if a match is mutual, have the corresponding person's profile show up on the "matched" section of the app [DONE]
-
once all this is done, see if you can implement some kind of matching algorithm
-
continue tweaking UI/UX
-
project inspiration : has utility to both of our lives, angelina trying to fill single, I'm trying to find housing for the next year
-
our struggles : expo compatibility, nativewind/babel stuff use screenshots if you have any
-
this isn't supposed to handle every single aspect of shared living, we give some responsibility to the user to reach out to the people they've matched with using their email handles to discuss the more specific things
-
this is also why we've provided the personal description field so users have the flexibility to truly show what they're prioritizing.
-
there could still be more improvements like having different user roles for people wanting a place to live and people looking to fill spaces in their existing accomodation, as well as discussing location, but we wanted to focus more on personality compatibility since your housemates are people you will most likely see every day and it's important to make that home environment as welcoming and supportive as possible whilst trying to take away the stress and anxiety that comes with living with new people!
What's beyond the scope of the MVP:
-
user can go back and update information (will require recalibrating all the matched algorithm stuff so for now we'll keep initial preferences fixed however, we will set up the workflow for it)
-
add a "price range" field : maybe one line that contains two sliders? So people looking for a place can specify the monetary range they're looking for and people looking to fill their vacancies already have a definite idea for how much it will cost them, so they will put a more narrower interval down. We just need to check to see if their price interval falls inside the price range of someone looking for housing. (vacancy filler user's range is a subset of house searcher's price range)
Analysis
View
Metric
- 18
- 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
- FirebaseIn code
- JavaScriptIn code
- ReactIn code
- Tailwind CSSIn 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
63 KB
Source files
23
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
Techgirl2/BananaBunks
33 files · 999 KB · @ e294bbf
Structure
Interface
13 files · 39%Screens, components and styles rendered to the user.
Application logic
5 files · 15%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
- TypeScript95%
- Markdown4%
- JavaScript1%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
package.json
npm · 30- @react-native-community/checkbox
- @react-native-community/slider
- @react-navigation/native
- @react-navigation/native-stack
- expo
- expo-image-picker
- expo-linear-gradient
- expo-status-bar
- firebase
- lodash
- react
- react-icons
- react-native
- react-native-deck-swiper
- react-native-paper
- react-native-safe-area-context
- react-native-screens
- react-native-svg
- +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.