The founder reached us a few months after the Minimum Viable Product went live. The platform was buggy and user adoption was below expectations. The original tech team was not up to the challenge. We prepared and executed the handover of the project and designed a roadmap to fix the existing issues and revisit the workflows by applying our Product Design Process. After delivering the improvements, user growth and adoption was back on track.
The platform was initially built in Ruby on Rails, and because the goal was to add to the existing project, we decided to keep the original codebase. But code coverage was low and one of the reasons why so many bugs were hitting production. We raised coverage to the ideal value of 80% and replaced deprecated libraries with new ones.
The founder reached us a few months after the Minimum Viable Product went live. The platform was buggy and user adoption was below expectations. The original tech team was not up to the challenge. We prepared and executed the handover of the project and designed a roadmap to fix the existing issues and revisit the workflows by applying our Product Design Process. After delivering the improvements, user growth and adoption was back on track.
The platform was initially built in Ruby on Rails, and because the goal was to add to the existing project, we decided to keep the original codebase. But code coverage was low and one of the reasons why so many bugs were hitting production. We raised coverage to the ideal value of 80% and replaced deprecated libraries with new ones.
It's often harder to build a simple and clean product than it is to build complex experiences. The main challenge with Invisible Homes was to cut everything that is often presented in real estate websites and stick to the very essential, without losing anything important in the process. We found that sweet spot in which users are able to reach their goals, without making the experience too complex for them to stick around for long.