RingApp
A multi-platform notification layer designed for immediate communication among close contacts—built through validated learning, fast iteration and real-world feedback.
In collaboration with my business partner, Carlos Carrascosa, we set out to create a fully functional product to improve communication quality among users. We followed a Lean Startup approach—testing hypotheses quickly, iterating with small releases, and learning from feedback. The goal was not immediate monetization, but building a product capable of mass adoption.
What we were trying to solve
The core idea was simple: make sure important alerts from trusted people are never missed. With information overload and silent/vibrate modes, critical messages can be overlooked—especially for close relations like parents, children, or elderly family members. RingApp was designed as a bridge: an immediate notifier that triggers attention, while leaving the follow-up communication to the user’s preferred channel (call, WhatsApp, etc.).
“We wanted something that could cut through the noise—simple, immediate, and reserved for the people who really matter.”
Once installed, the app created what we called the “RingApp context”: users could see which contacts also had the app, request authorization, and build a small secure circle. Inside that circle, contacts could send different levels of notifications—quick, standard, or urgent—depending on the situation.
Technical notes and learnings
The product included an Android app, an iOS app, and a central server built with ASP.NET. At the time, Android and iOS allowed more permissive access to device states than today, which enabled features such as contextual awareness (e.g., silent/vibrate status). Privacy requirements have evolved significantly since then, and a modern version would require a careful redesign to balance functionality with stronger user protection.
I personally coded every layer of the system, which pushed me into true multi-platform development: Java (Android), Objective-C (iOS), and C# for ASP.NET on a Windows server. Beyond code, the project taught me a lot about security, data protection, permissions design, and the real complexity of building trustworthy communication tools.
After two years, we ended the project. Even with a fully functional product and a company established in Spain, we couldn’t break through the investment environment needed to scale. The experience was humbling, but it left us with a strong foundation of practical knowledge we carry into every project after it.