ritmovida

The company appears to be a personal project by one founder (Ikaro Laborda) that builds a health and fitness tracker integrating Xiaomi body composition data with AI-powered insights. The product is described as a full-stack Laravel application with Bluetooth integration, domain-driven architecture, and an embedded AI coach. It imports data from a Xiaomi Mi Body Composition Scale 2 via Bluetooth or Python sidecar, processes it server-side, and provides personalized coaching using Prism PHP and Tavily search.

The author states the project began as a personal solution to manage insulin resistance, aiming for user ownership of health data and actionable guidance. The system tracks trends over time, correlates them with habits, and offers AI-powered insights without locking users into proprietary ecosystems.

Analysis basis

This report is based entirely on the self-reported, unverified description provided by the author. No third-party verification or historical data exists for this project.

The description states that RitmoVida is:

• A personal health & fitness tracker built with AI
• It imports Xiaomi body composition data over Bluetooth
• It tracks trends and provides AI-powered health insights and coaching

It uses:

• Laravel 13 (PHP 8.5)
• Bluetooth communication via Web Bluetooth or Python sidecar using bleak
• Server-side decoding of raw Bluetooth frames to derive body composition metrics
• An embedded AI coach, powered by Prism PHP and Tavily search
• A domain-first architecture with Livewire 3 + Volt, Tailwind CSS v4 + Flux UI, PostgreSQL 17, Redis 7, Docker

Inference The product appears to be a full-stack application designed for personal use, integrating hardware (Xiaomi scale) and software (AI coaching), but no evidence of commercial deployment or user base is provided.

The author states:

• RitmoVida was inspired by the need to understand how one’s body changes over time, correlate those changes with habits, and make better decisions about nutrition, exercise, and recovery.
• Most existing health apps either lock data into proprietary ecosystems or provide isolated metrics without meaningful context.
• The goal is to offer a single place where users can own their data, understand it, and receive actionable guidance.

The author also mentions:

• Building RitmoVida taught them that engineering must be balanced with empathy
• Numbers alone are rarely motivating; presenting trends, explaining them, and helping build sustainable habits is more valuable than displaying measurements

Inference The positioning has evolved from a personal solution to a broader vision of empowering users through data ownership and AI-driven insights. However, there is no evidence that this positioning has been tested or validated in the market.

The description states:

• The product was initially built for the founder’s own use case — managing insulin resistance
• It aims to help people understand their health through their own data, not just collect it
• It tracks trends over time and correlates them with habits like meals, workouts, sleep, hydration, mood, and steps

Inference The initial ICP seems to be individuals with chronic conditions or lifestyle management needs (e.g., insulin resistance), but no evidence of a defined customer segment beyond the founder’s personal experience.

The description does not contain any information about:

• Revenue streams
• Pricing models
• Monetization strategy
• Customer acquisition costs
• Sales process or go-to-market approach

Not evidenced

The author states:

• Built using Laravel 13, Livewire 3 + Volt, Tailwind CSS v4 + Flux UI
• Uses PostgreSQL 17, Redis 7, Docker, Prism PHP, Python (bleak) for Bluetooth support
• Implements a domain-first architecture to isolate business logic from infrastructure
• Communicates directly with Xiaomi Mi Body Composition Scale 2 via Web Bluetooth or Python sidecar
• Raw Bluetooth frames are decoded server-side, ensuring deterministic results across measurement methods

Inference The technical stack suggests a modern, scalable approach. However, there is no evidence of production deployment, performance metrics, or scalability testing.

The description states:

• The project started as a personal project
• It was submitted to the OpenAI 2026 hackathon
• Future work includes richer trend analysis, wearable integrations, advanced nutritional insights, predictive health indicators, and additional AI capabilities

Not evidenced No evidence of user adoption, revenue, customer growth, or product-market fit beyond the founder’s personal use.

The author claims:

• Most existing health apps either lock data into proprietary ecosystems or provide isolated metrics without meaningful context
• RitmoVida aims to be a single place where users can own their data, understand it, and receive actionable guidance

Inference The competitive landscape includes traditional health apps that may lock data or offer limited insights. However, no specific competitors are named, nor is there evidence of market analysis or differentiation strategy.

• Single-founder project: Only one team member (Ikaro Laborda) is listed
• No commercial traction: No evidence of revenue, customers, or product-market fit
• Limited external validation: The project was submitted to a hackathon and has no independent verification
• Technical complexity without deployment evidence: While the architecture is described in detail, there is no indication that it’s been deployed at scale or tested in real-world conditions
• AI coach design risk: The AI coach is described as reasoning over user data first, but no evidence of its effectiveness or user feedback exists

Not evidenced No data on market size, competitive dynamics, or financial viability.

1. What specific problem are you solving for users beyond your own?
2. Have you validated your solution with potential users outside of yourself?
3. How do you plan to monetize this product?
4. Are there any existing health apps or platforms that you see as direct competitors?
5. What is the timeline for launching a public version, and what features will be prioritized?
6. Do you have plans to integrate with other wearable devices or platforms?
7. What are your long-term goals for RitmoVida — is it intended to be a standalone app or part of a larger ecosystem?