MVP Release Date, Public Code and Development Updates

After nearly two years of ideation, planning and development, the RepMe team is incredibly excited to announce the release date for the RepMe MVP v1.0. However, before we go any further, we’d like express our gratitude for the community’s support over the past months.

When the team first came together, we could only envision an ardent group of supporters rallying around this project to drive our collective vision. Now that we see what’s taking shape, we are humbled and inspired. For that, we offer great thanks.

It should be noted that a revolutionary platform can only take root with the help of our fellow visionaries and we believe this loyalty should be rewarded. As big data has been likened to crude oil on so many occasions, we feel that RepMe is tantamount to the American prospectors striking oil in the late 19th century.


RepMe MVP v1.0 — Dates and Features

The first version of the MVP will be released January 21, 2019. While we fully expect development to be complete roughly two weeks before that, we’d like to use this buffer for acceptance testing, extended review and any unforeseen circumstances that might arise. The v1.0 MVP will include many of the platform’s core features such as:

  • User Account Creation
  • Credentials Management
  • User Profile Creation and Editing (Photo, Skills, Location, Interest, Etc.)
  • RPM Wallet — Adding & Editing
  • RPM Wallet — Deposits, Withdrawals and Transactions Interface
  • RPM Connection Incentivization
  • Escrow System
  • Network Connections Lists
  • User Profile Search

MVP Public Testing

Shortly after the release date, we will open up the MVP to the public in tiers. We will begin modestly and grow in size with each successive wave. The aim is to initially identify and address any potential issues with a small group of users, bring more on, then rinse and repeat. It is also critical to effectively organize user feedback, thus we’d like to make sure our system for collecting this information is optimized.

We shall solicit feedback from the early adopters of the platform and do our best to implement suggestions. While we have a concrete roadmap for the v2.0 and v3.0, it has been our experience that a user-testing feedback cycle can improve the product in ways that can not be readily anticipated.

Weekly Development Updates

It is important for us to keep our community connected to the development of the project, therefore we will be publishing weekly updates leading up to the release of the MVP. We will, in plain English, provide a summary of the previous week’s work and what the team’s focus will be in the week to come.

Public Code Repositories

While we initially intended for our repositories to be made public, we have been strongly advised against doing so. This resulted in some lengthy internal discussions and while we understand the desire to have a peek at some written code, it is not currently in our best interests to have our work forked and repurposed. To achieve a middle ground, we will be making portions of the code public while leaving enough out that it would be difficult for a third party to pick up where we left off. It is still in our eventual plans to open source the code (and we do have some exciting news in this arena) however, we must keep it close to the vest for the time being.

PS—The website is still forthcoming.