Mooch is an application that allows users to share their different subscription services and 'mooch' on memberships from their close friends!
This project was created as a Full Stack Group Project while attending Nashville Software School's Full Stack Web Development Bootcamp. All planning and development was completed over the course of 4 weeks.
- Chase Burnett | Github | LinkedIn
- Cristi Neames | Github | LinkedIn
- Jeremy White | Github | LinkedIn
- Robert Stroud | Github | LinkedIn
- Yogi | Github
Many of us subscribe to a host of different services. Woudn't it be nice to share a subscription with a friend when you don't need it? Like if you're travelling outside the country, you probably aren't going to be using that YMCA service that much!
Mooch solves this problem by allowing users to browse and search for membership subscriptions that other users are willing to share. Users can manage their memberships, create new Mooch Posts when they want to share a membership for a specific time, and manage incoming Mooch Requests on their posted mooches to decide who they want to share that mooch with!
Interactive homepage with collapsing sections
Realtime search feedback as you type
Suggestions for mooches, all in one effecient backend request
Requesting another users Mooch Post
Add a membership to your account from the list, then post a Mooch yourself!
One Specific difficulty Jeremy faced was getting the Authentication and Authorization flow to work properly and manage the JWT correctly to protect the endpoints. It took some googling to understand where and how in program.cs to setup the JWTBearer and how to handle that in the frontend as well. He was eventually able to accomplish this, but as the team was primarily using swagger rather than postman for API testing, constantly reauthenticating the JWT during endpoint testing slowed development significantly. The JWT Authorization was removed from the endpoints. Incorporating Postman earlier into the process and setting the JWT as an environment variable in postman would've allowed the endpoint jwt to stay in place and would've probably singificantly improved development velocity in general.
For this project, we primarily worked in horizontal slices:
- Planning/basic prototyping with Figma (Link to Wireframe here)
- Creating an ERD to understand the data relationships we were going to be managing (link to ERD here)
- Creating Backend issues in Github Project Board
- Completing the majority of Backend Issues before moving to frontend
- Creating Frontend Issues in Github Project Board
- Completing Frontend Issues
While this approach did allow us to stay relatively focused, it became evident as the project went on that we had spent a lot of time on backend CRUD that we weren't even going to be able to incorporate in the frontend due to time constraints. Had we worked more vertically, we could've ensured that upon each merge to main, that merge included a complete, vertical (frontend to backend) set of value to the user.
- Users must login and create an account to use Mooch
- On the homepage, Users can search Mooches by Membership, Organization, or User
- Users can view details about an organization
- Users can view Mooch details, see other suggested Mooches by that user, and see other Mooches in that category
- Users can request a Mooch
- Users can add a membership to their account
- Users can view their memberships, Mooches, and Mooch Requests
- Search for mooches based on Location
- Ability to see more information (username, etc) when reviewing mooch requests
- Ability to edit or delete a Mooch Post
- Ability to accept, or deny a Mooch request
- Start a conversation thread with a requestor when a Mooch is requested
Dependencies You will need npm, Visual Studio, .NET 6, SQL Server, and whatever SQL Client you prefer (We used SQL Server Management Studio)
- git clone this repo to your local machine.
- Setup Firebase project for authentication. For step-by-step instructions for this process, check out this file here.
- Navigate to the repo on your machine and run the following commands in the terminal:
cd mooch-client
cp .sample.env .env.local
- Update the
.env.localfile with the Firebase API keys created in the previous step. - Make sure that Node.js and npm are installed on your machine. Click here for installation.
- Run the following command in the terminal from the
mooch-clientdirectory:
npm install
- Open your SQL Server and copy/paste the SQL script located in
Mooch-Lightning/DataDirectory - Paste the script into your SQL client and run. This will create the database and schema, and create some seed data as well
9.In Visual Studio, open the Mooch-Lighting.sln
10. Right click on the Dependencies folder and select Reload
11. Right click on theMooch-Lightning project in the Solution Explorer and select Manage User Secrets
12. Fill in the following JSON data, including the location of your database server and the firebase config data.
{
"ConnectionStrings": {
"DefaultConnection": "server=<YourLocalSQLServerDatabaseConnection>;integrated security=true;Trust Server Certificate=true"
},
"FirebaseProjectId": "mooch-lightning",
"FirebaseConfig": {
"apiKey": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"authDomain": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX",
"projectId": "XXXXXXXXXX",
"storageBucket": "XXXXXXXXXX",
"messagingSenderId": "XXXXXXXXXX",
"appId": "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
}
}
-
Run the Backend from Visual Studio
-
Run the Frontend by navigating to the
mooch-clientfolder and runningnpm start -
The frontend should start on
http://localhost:3000/ -
Enjoy the App!
We want to thank everyone in our NSS Cohort that helped us out with this project. The instructors gave meaningful insight into what would be best to focus on in this application.