Eyenbros

Eyenbros is a community-based project management marketplace for Tribes(groups) willing to carry out small and medium-sized projects collectively. The users within the platform can create their tribes or be a part of it. The leader of the tribe can create tribe projects and collect funds from their members. 

They are able to open their projects for bids from the professionals and carry out the project within the platform. The platform also has an active connect area where users are able to create their own posts. 

As for the professionals, and other users they have a dashboard to track down their engagement in a very intuitive manner.

Product Approach

We started with the project at a very early stage.  The founder, Brahim Benaissa, a research scholar turned entrepreneur was developing the project on his own from an open-source project at that time. 

We introduced our MVP Program and Brahim was quick to identify the benefits of it. Once we started the program, we identified key features to test the market and got feedback from the users. 

Ever since we are able to iterate 3 times with the help of the customer feedback and continue to further the progress. 

• In the first release, the key features including minimal group activities were released to gather feedback from the users. 
• In the second release, we attached a non-business side to the platform driving user engagement using content. 
• Once we finalized the feature set using this MVP Approach, we revamped the design with the final release of the revamped structure collected via user feedback. 

Technical Approach

1. The initial skeleton project had the stack of:

• Python 2.7
• PostgreSQL 
• BackboneJS with Django template rendering in most places. 

During the development of the first release, we continued with the stack, before upgrading and parting ways with the same in the second release. 

We upgraded to Python 3.x  and build the new features with Django Rest API & VueJS. 

We still rendered the initial pages to help the SEO of the product. 

2. In the second release, 

• We tested the semantic UI to test the response of the users with a slightly better UI/UX and it turned out to be exceeding our expectations. 
• By the end of the second release, the need for a much better UI/UX was evident.

3. And…thus started our third phase where,

• Our dedicated designer got involved to bring out the aesthetics with UI/UX keeping th conventions in mind for ease of access & usage.

Development Approach

The approach that we followed -  was to get the designs prepared in one sprint that gets developed in the next sprint and the cycle continues. 

• Firstly, the designs were reviewed and finalized. 
• Secondly, the pages and features were added in the development sprint. 
• Following that, the bugs were fixed within the next development sprint.

Current State

The client had a good release and moved from MVP to the next phase as well but with prevailing Covid-19 during 20 - 21 they had to shut down operations. 

Their product is still live but the operations were dismantled after Covid. The client is looking to re-initiate the project and we are on hold to develop further sprints.