TimeSpare is an employment-oriented network service that provides users access to quick and temporary job openings in their local area.
It is aimed to provide hourly work opportunities to individuals with specific skillsets who are looking to fulfill their free time with meaningful work in their community.
Sometimes, you find yourself with some free-time. You’re tired of laying around in bed all Saturday, or waiting for your next customer as an Uber driver. TimeSpare fills those idle times with purposeful work by connecting you with locals around you who need your skills.
We believe that good things happen when people help each other, whether across town or towards their dreams. Opportunities appear, open up, and become reality.
- User Authetication: sign up and log in
- Posting new listings, and a log of all listings
- Viewing and editing bookings
- Search functionality based on categories or tags
- Calendar API
- Saving of user browsing data to database
- User profile page + Ratings
- Production README
- AWS
- Chat functionality
- In-site payment functionality
- Hosting on marketplace
HTML5 / SCSS / MongoDB / Express.js / React.js / Redux / Node.js / JavaScript / Calendar API / Animate CSS
Anticipated Challenges:
- Learning Node, Express, and MongoDB to handle the back-end and database
- Choosing the right Calendar API for bookings
- Splitting the load between our front-end and our back-end
- Having the correct shapes of state for our data
- All members of the team read the Git and MERN tutorials
- Set up MVPs and divide up work
- Wrote proposal README and planned work for the week
- Implement user authorization on database backend - Jin and Yinglan (completed on Sunday)
Yinglan Ou, Matthew Jang, Mengna Lin, Jin Chen
- Build skeleton React site (MERN setup) - Jin
- Backend User Authentication - Jin
- Build the sample states - Yinglan
- Frontend User Authentication - Yinglan & Mengna
- Components: Button, Modal, Navbar - Mengna
- Components: Forms - Matthew
- Production proposal/README - Matthew
- Investigate Calendar API methods and test - Everyone
Frontend (morning)
- User Auth Wrap-Up: Submit Button, input fields, CSS - Mena
- Frontend routes: where the buttons will lead to (Index Home Page)
- User Profile (aka. Listing Dashboard or User Show): (all the listings for that specific user + delete/edit buttons) (create new listing button) (user background) (dummy profile photo, aws?)
- Listings Index page: design decision (how the listing boxes will look like, display text for listings) - Matt/Mena
- Listing Show as a modal?
- Listing Create page (form) → date (calendar API) - Mena
- Reducers / Actions / Util - Yinglan
Backend (afternoon)
- Listings - get (10~15), id (current user), post, patch, delete - Yinglan/Jin
- Display 30 listings on the home page (db) - Jin
- Background (user profile) - not required - Jin
- Complete Production README.md - Matthew
- Refine design/CSS
- Finish testing, deploy, and debugging - All team members