Harmony – Cycle & Partner Care

Harmony – Cycle & Partner Care is a self-reported mobile application designed to track menstrual cycles, fertility windows, pregnancy progress, and related health symptoms. The app claims to support multiple languages (English, Turkish, German, Spanish, French, Italian, Portuguese, Russian), offer an Android-first experience, and provide secure cloud backup with optional partner sharing.

The author states that the product was built during a hackathon using React, TypeScript, Supabase, Capacitor, and GPT-5.6 for code auditing and redesign. It includes features such as biometric protection, device integrations, privacy-safe notifications, and local-first data storage with optional cloud sync.

Key commercial due-diligence questions include:

• Is there any evidence of user adoption or retention?
• What is the actual product-market fit in this niche?
• How does the team plan to scale beyond a single developer?

The most important open question: What traction, revenue, or customer feedback exists for Harmony?

The description states that Harmony is a mobile app for tracking:

• Periods
• Symptoms
• Fertility windows
• Pregnancy progress
• Water intake
• Weight
• Private notes

It supports multiple languages (English, Turkish, German, Spanish, French, Italian, Portuguese, Russian) and offers an Android-first experience.

The author claims the app works "local-first" with optional Google sign-in and secure cloud backup and restore. It allows partners to connect via invite code and share only insights the user permits.

It sends reminders and privacy-safe partner update notifications.

The description states it uses React, TypeScript, Vite, Tailwind CSS, Capacitor, Supabase, Firebase Cloud Messaging, and GPT-5.6 for development.

Inference: The app appears to be a health-tracking tool focused on reproductive health, with an emphasis on privacy and multilingual support.

The author positions Harmony as:

• A private, multilingual cycle and pregnancy tracking tool
• Designed for people everywhere—not limited by country or language
• Focused on calm, accessible, low-friction user experience
• Supporting both individual use and optional partner sharing

It is described as a product built with the goal of reducing burden rather than adding it, especially for users managing chronic health conditions.

The author also claims that Harmony was developed during an OpenAI Build Week using GPT-5.6 to improve onboarding, authentication, and notification systems.

Inference: The positioning emphasizes accessibility, privacy, and global reach—though no evidence of actual market traction or user feedback is provided.

The description states that Harmony aims to serve:

• People tracking their menstrual cycles
• Individuals in pregnancy care
• Users managing chronic health conditions
• Anyone seeking a calm, private, multilingual experience for reproductive health data

It is designed to be accessible and supportive, particularly for those who may feel overwhelmed by existing tools.

The app supports multiple languages (English, Turkish, German, Spanish, French, Italian, Portuguese, Russian), suggesting an international audience.

Inference: The ICP likely includes individuals in developed markets who value privacy and multilingual support, especially those managing reproductive health or chronic conditions. However, no evidence of actual users or personas is provided.

The description does not provide any information about:

• Revenue model
• Pricing structure
• Monetization strategy
• Subscription plans or in-app purchases

It only mentions that the app works with optional Google sign-in and secure cloud backup, which may imply a freemium or paid cloud feature.

Inference: No clear business model is evident from the self-reported description. The lack of pricing or monetization details makes it difficult to assess commercial viability.

The author reports that Harmony was built using:

• Frontend: React, TypeScript, Vite, Tailwind CSS
• Mobile Framework: Capacitor
• Backend Services: Supabase (Google OAuth, PostgreSQL, Row Level Security, Edge Functions)
• Notifications: Firebase Cloud Messaging
• AI Tools: GPT-5.6 via Codex for code auditing and redesign

The app is described as:

• Android-first
• Supporting biometric protection
• Integrating with device features like notifications and file operations
• Using secure storage methods including JWT-protected functions and RLS policies

It also includes a working APK, indicating that the product has reached a functional prototype stage.

Inference: The technical stack suggests a modern, scalable architecture with attention to security and mobile integration. However, no evidence of production deployment or performance metrics is available.

The description states:

• Harmony was built during an OpenAI 2026 hackathon
• It includes a working Android APK
• The team consists of one member (AHMET HAZAR)
• No mention of user adoption, retention, or usage data

There is no evidence of:

• Active users
• Revenue
• Customer feedback
• Product-market fit validation

Inference: The product appears to be in early development or prototype stage. There is no indication of traction or maturity beyond a single developer’s effort.

The description does not include any information about:

• Competitors
• Market size
• Competitive differentiation
• Industry trends

It does not reference other apps in the reproductive health space, nor does it explain how Harmony differs from them.

Inference: No competitive context is provided. The app’s positioning and features are described without comparison to existing solutions.

Key risks and red flags based on the self-reported description:

• Single-person team (AHMET HAZAR) — raises concerns about scalability, maintenance, and long-term support
• No revenue or customer data — makes it hard to assess viability or traction
• Product is described as a hackathon project — likely not yet mature for commercial use
• Use of GPT-5.6 for development may indicate reliance on AI tools rather than deep technical expertise
• Lack of clarity around monetization, pricing, and business model

Inference: The lack of team structure, traction, or revenue data suggests a high-risk, early-stage product with unclear commercial potential.

1. What is the actual user base or adoption rate for Harmony?
2. How do you plan to monetize the app beyond optional cloud features?
3. What are your plans for scaling beyond one developer?
4. Are there any existing partnerships or distribution channels?
5. How do you intend to ensure long-term privacy compliance and data security?
6. What is the roadmap for iOS support, and how does that affect your go-to-market strategy?
7. Have you conducted any user research or usability testing?