ruminate.io

Building Ruminate.io: Real-time Feedback

Building Ruminate.io: Real-time Feedback

Ever since the Alpha release, I’ve been focusing on making it easier for users to get started. Matrices can now be shared, cloned and user can also browse the template directory for pre-made matrices.

However, there is still one obvious barrier that I’ve been ignoring from the very beginning. In order to build and edit a decision matrix, you must sign up for an account first. If I wanted anyone to be able to quickly get started, the app will need to support the ability for guest to create and edit a matrix.

Building Ruminate.io: First Contact

Building Ruminate.io: First Contact

As the saying goes, no plan survives contact with the enemy. In this case, no product assumption survives the first contact with real users.

I’ve been building Ruminate.io with the assumption users understand what a decision matrix is and how to use it. This may be true for some but it’s definitely important to provide some guidance for the rest.

Building Ruminate.io: Towards Alpha

Building Ruminate.io: Towards Alpha

After building the main user journey for Ruminate.io, I focused on getting it ready for its Alpha release. The objective of this release is to gather feedback from others using it so I can decide where to take it next.

As you can see on the screenshots below, I marked the non working parts of the app as coming soon so I can get the app out the door quicker.

Building Ruminate.io: Core Concept

Building Ruminate.io: Core Concept

It has been years since I’ve worked on a side project. So when I found some spare time and an idea that seems interesting along with the arrival of Phoenix LiveView, I started working on Ruminate.io.

This is the first of a series of articles to recount the entire journey of building this app. For my learnings of Phoenix LiveView while working on Ruminate.io, check out this article.