![]() |
![]() |
![]() |
![]() |
![]() |
UnBlush is the first dating app for people of all or no genders with STD(s). UnBlush is an online-dating application available on Web and iOS. With 1 in three people in the US contracting an STD before the age of 25, STDs are much more common than the average person would think. Our dating app allows users to disclose their condition(s) and list the condition(s) that they are open to a potential match having. By allowing users to disclose this taboo information upfront, the stigma of having an STD and fear of judgement is removed and you can focus on actually getting to know your matches. Finally an app that is aimed at taking the stigma out of being positive!!
You can find the project at UnBlush
Our project is also on IOS IOS UnBlush
* Sign up via email or Google Account
* Upload image to Profile
* Add bio information
* Check off which STD(s) the user has
* Check off which STD(s) the user is open to a partner having
* Match recommendations based off user's disclosed/"open to" STD(s), age, gender, and distance
* Swipe yes/no on other users' profiles resulting in a match if a yes is reciprocated
* In-App chat once users are matched
* React w/ React Hooks
* Firebase/Cloud Firestore, Firebase Functions
* Node.js
* Stripe
* ZipCodeAPI.com
* Firestore/Cloud Firestore noSQL database Firebase Functions
* Node.js
Authentication for users was accomplished by using the built-in auth feature in firebase
A simple login function that includes firebase.auth().signInWithEmailAndPassword(email, password);
And a simple logout function that includes firebase.auth().signOut();
There are no endpoints to point to but a list of functions as this is a noSQL database
Documentation - https://firebase.google.com/docs
We used Stripe API for our payment system, a sample function would look like so:
const stripe = require('stripe')('INSERT_YOUR_API-KEY');
(async () => {const charge = await stripe.charges.create({
amount: 999,
currency: 'usd',
source: 'tok_visa',
receipt_email: '[email protected]',
});
})();
The only necessary endpoint is to point your <StripeProvider apiKey="YOUR-API-KEY"/> to your API key
Documentation - https://stripe.com/docs
We used ZipCodeAPI.com to be able to match our users by the distance they choose in their profile settings
The only endpoint you need for this API is
const endPoint = 'https://www.zipcodeapi.com/rest/<YOUR-API-KEY>/radius.json/<USER-ZIPCODE>/<USER-DISTANCE>/mile';
Documentation - https://www.zipcodeapi.com/API
All packages used to create this application:
* @types/react-stripe-elements
* @types/stripe
* axios
* firebase
* moment
* prop-types
* react
* react-dom
* react-dom-confetti
* react-firebase-file-uploader
* react-firebaseui
* react-firestore
* react-icons
* react-responsive-navbar
* react-router
* react-router-dom
* react-scripts
* react-select
* react-spinners
* react-spring
* react-stripe-elements
* react-sweet-progress
* react-toastify
* react-with-gesture
* stripe
* styled-components
* typescript
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
}
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change. Please note we have a code of conduct. Please follow it in all your interactions with the project.
* If you are having an issue with the existing project code, please submit a bug report under the following guidelines:
* Check first to see if your issue has already been reported.
* Check to see if the issue has recently been fixed by attempting to reproduce the issue using the latest master branch in the repository.
* Create a live example of the problem.
* Submit a detailed bug report including your environment & browser, steps to reproduce the issue, actual and expected outcomes, where you believe the issue is originating from, and any potential solutions you have considered.
We would love to hear from you about new features which would improve this app and further the aims of our project. Please provide as much detail and information as possible to show us why you think your new feature should be implemented.
If you have developed a patch, bug fix, or new feature that would improve this app, please submit a pull request. It is best to communicate your ideas with the developers first before investing a great deal of time into a pull request to ensure that it will mesh smoothly with the project. Remember that this project is licensed under the MIT license, and by submitting a pull request, you agree that your work will be, too.
* Ensure any install or build dependencies are removed before the end of the layer when doing a build.
* Update the README.md with details of changes to the interface, including new environment variables, exposed ports, useful file locations and container parameters.
* Ensure that your code conforms to our existing code conventions and test coverage.
* Include the relevant issue number, if applicable.
* You may merge the Pull Request in once you have the sign-off of two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.
These contribution guidelines have been adapted from Good-Contributing.md-template
