Skip to content
/ bdate Public
forked from mpr-fbu/bdate

New version of mpr-fbu/bdate with custom backend, instead of Parse

License

Notifications You must be signed in to change notification settings

rgdagir/bdate

 
 

Repository files navigation

bdate

User flow

When users open the app: splash screen while things load.

Opening screen: login & signup User taken to home screen

Home screen: Button that will find a blind date and take you to the chat screen. When the user enters the app for the first time, there are no active chats, so the only thing on the home screen is the button. Later on, when the user has active chats, the match button will be by the bottom of the screen, below all active chats. Swipe left to see profile and settings Swipe right to see the current chats Between the button and the chat screen, open a map where thge user can choose the distance range of the possible match.

Chat screen: Basic chat screen When user has enough points to unlock features, pop-up notifications will show up If the user clicks on the other user's username, it is taken to another profile screen where information can be unlocked

Earn points by exchanging messages to unlock features Have a "show/give everything" button (the other person has to agree)

Profile screen: Add basic info and profile pic (integrate camera or choose from existing pics) This leads to camera screen or settings screen

Settings screen (does it need ot be implemented?): Basic configs

Evaluating Product Ideas What makes for a "good" app idea? When evaluating projects, be sure to consider the following five elements:

Mobile: How uniquely mobile is the product experience? What makes your app more than a glorified website? Try for 2 or more of these: maps, camera, location, audio, sensors, push, real-time, etc

Story: How compelling is the story around this app once completed? How clear is the value of this app to your audience? How well would your friends or peers respond to this product idea?

Market: How large or unique is the market for this app? What's the size and scale of your potential user base? Does this app provide huge value to a niche group of people? Do you have a well-defined audience of people for this app?

Habit: How habit-forming or addictive is this app? How frequently would an average user open and use this app? Does an average user just consume your app or do they create?

Scope: How well-formed is the scope for this app? How technically challenging will it be to complete this app by the end of the program? Is a stripped-down version of this app still interesting to build? How clearly defined is the product you want to build?

Good reads: https://www.huffingtonpost.com/david-wygant/the-shocking-truth-about-_3_b_4967472.html https://www.esquire.com/uk/life/sex-relationships/news/a6170/7-alternatives-dating-apps-to-tinder/ https://www.elitedaily.com/dating/use-tinder-for-same-reason-not-dating/1839174 https://theoutline.com/post/3402/tinder-is-not-actually-for-meeting-anyone?zd=1&zi=s5q3wkak https://www.theodysseyonline.com/7-reasons-why-tinder-is-bad-idea

About

New version of mpr-fbu/bdate with custom backend, instead of Parse

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • Java 100.0%