Refine MVP (Minimum Viable Product) Definition

[WilliamDormer]

https://github.com/PullDating/Org/wiki/MVP-Definition

We want to specify the list of features, including detailed implementation specifications in the MVP definition wiki page. This will allow both the frontend and backend teams to have a clear understanding of what they need to construct for the MVP. This design effort is primarily the responsibility of the UX team, but should take input from both the frontend and backend teams.

[viktor-lesyk]

@WilliamDormer 2 things I'm a bit concerned about:

1. To me it seems like we're starting to build an engine without having a clear vision of the car as a whole and why it should be better than other cars on the market (maybe it should be a flying car? or it should use hydrogen?). Not that I'm saying we shouldn't (eventually) create the MVP - that's super important. I'm just afraid it might be not the best time for it (too early).

2. Going through the MVP definition - how can I contribute to it? I would like to suggest something or highlight and comment (discuss) a specific part. Can I somehow do it in GitHub or should we maybe consider another tool for such collaboration?

[ajbott]

@viktor-lesyk I kind of feel the same way. I have a vision on what I'd love to see the dating app be and I am currently working on a specification to detail how the engine would work. There are some key components of the app that are always going to be there though.

The dating app will at least need:

• Login
• User Profile
• Matches
• Communication
• Search (Matching/Searching/Algorithm/Swiping/ect)

I think starting something in these areas would be great. I think the main focus of the app should be the searching part. How can we help the users find who they're looking for in the most efficient way possible? I think that involves having the user specify what they're looking through through static filters. Much like OkCupid's way, but less of the irrelevant chaos that they present. I would like to see a categorical engine that shows you what filters people have set for what they're looking for and have the engine assist you in filling out the filters that will more quickly get you to who you're looking for.

[Oshyan]

Hey all, nice to see some activity around here again!

I agree a fair amount with the concern about whether focusing on an MVP is the right thing to do at this point. I haven't caught up on new activity yet, but from my recollection of the earlier start of this project, there was the idea that essentially starting with an MVP was necessary to prove to people that we were serious and could actually pull this off, etc. I was never fully convinced that this approach was actually going to give the app and community the start it needed. I definitely think that establishing trust in a prospective user base is critical, I'm just not sure that making an MVP first and foremost is the most effective way to do that.

From my perspective an MVP has value, but it's not the key piece to building a successful dating app that addresses the unmet needs of the dating population overall. There are hundreds of dating apps out there, many of them essentially also in "MVP" form 😄 and I think we need much more so to demonstrate that we have a realistic and defensible concept that actually addresses people's real needs.

The key thing that needs to happen from my perspective is to understand what the main issues are with the existing tools and then to come up with a convincing proposed solution (set of features, incentives, etc.) to at least one and ideally several of those issues. This also has to include a realistic marketing and growth strategy that doesn't involve large amounts of marketing dollars. And I also think that it's important for revenue of some kind to be a part of this proposed plan because everyone is wary of a "free lunch" at this point, and with good reason. This is what almost every eventually-toxic start-up social network, dating app, or whatever does early on: everything is free, they gain users, and then at some point they start charging for stuff or flooding it with ads or whatever, i.e. they have to figure out how to monetize. If we can't figure out how to make this project financially sustainable from an early stage, we can't provide assurance to our users that the app is worth investing in vs. the hundreds of other options.

So coming up with the MVP concept, i.e. describing how we'd solve problems we identify, is definitely something we should be focusing on. But the degree to which I would aim to build an actual MVP app at this stage would depend most on the available resources, the talents and time of those who are involved and committed to the project. If we happen to have some great devs who would build a solid basis for the project that wouldn't have to be totally redone later to reach production, then I think having an MVP would only be an asset and could be done in parallel to other aspects that I see as more key to the eventual, long-term success one would hope for. But if we don't already have that level of talent (or talented people with that amount of time they can invest) then I think spending limited resources to find those people at this stage may be premature.