myNeeds

Introduction

myNeeds was a social network that connected the needs of users with the offers of brands. As opposed to the traditional relationship between brand and customer, here the user was the one who said what they needed, and other users and brands helped them with recommendations, offers, comments and suggestions.

It was a complete social network, with everything a social network had at that time (wall, profiles, friends, chat), a Pinterest-like grid of posts and a "concierge" that assisted the user. It started out as Needbook and was later renamed myNeeds.

What we did

We built the product end to end: discovery, UX, design, development and deployment. We built the responsive web app, the admin console, the brands console, the API and the Android app.

I led the project technically: I defined the architecture, led the team and coded the hardest parts with them.

The web app and the API were built in PHP with Symfony 2 and Doctrine on PostgreSQL, with functional tests of the API and continuous integration with Jenkins. The Android app was native, in Java.

The first release went out in 4 months. After that we did 24 incremental releases.