CalDo

CalDo is a self-reported personal lifestyle app built by one developer (Zoran Perokovic) for tracking fitness, meals, workouts, and daily organization. The author states it was developed as a hackathon submission to the OpenAI 2026 hackathon, using AI tools like Codex, ChatGPT 5.6, and the Uno platform. It is described as an attempt to consolidate multiple apps into one, with features including calorie tracking (manual or photo-based), workout logging (manual or video-based with form analysis), and calendar/todo functionality.

The app's positioning is that of a personal productivity and health management tool, aiming to reduce reliance on multiple platforms while leveraging AI for workout analysis. The author claims the app can analyze bodyweight squats from video input and count reps automatically.

Key commercial due-diligence questions include: What is the actual product-market fit? How does it differ from existing solutions? Is there a viable path to monetization or user adoption beyond a single developer's prototype?

The description states CalDo is:

• A lifestyle app integrating fitness tracking (calories, workouts), workout form analysis via video input, and calendar/todo functionality.
• Built using Azure, C#, SQL, and Uno platform.
• Initially prototyped in Replit but rearchitected using .NET 10, Flutter, and eventually Uno after experimentation with AI tools like ChatGPT 5.6.

Inferred from the description:

• The app is designed to be a single interface for personal health and productivity management.
• It includes AI-powered features such as rep counting and form feedback for bodyweight squats.

Not evidenced:

• Whether the app is functional beyond a prototype or demo.
• Whether the AI features work reliably outside of limited testing (e.g., bodyweight squats).
• The actual user interface or experience design.
• Any technical architecture details beyond platform choices.

The author states:

• CalDo was built to solve personal needs: tiredness of multiple apps, privacy issues, and cost of coaching.
• It aims to be a "one lifestyle app to rule them all."
• The app is positioned as an AI-powered alternative to paying for personal coaching sessions.

Inferred from the description:

• The app is intended to replace several existing tools (e.g., calorie trackers, workout apps, calendars).
• It leverages AI to provide personalized feedback and reduce manual input.

Not evidenced:

• How CalDo differentiates from existing solutions.
• Whether the author has validated demand or user interest beyond personal use.
• Any marketing claims or positioning in the market.
• The app’s intended audience beyond the developer's own needs.

The description states:

• The app was built for the developer’s own use, addressing personal pain points around fitness tracking and privacy.
• It is described as a "personal lifestyle app."

Inferred from the description:

• The target customer may be individuals seeking integrated health and productivity tools.
• The app could appeal to fitness enthusiasts or people managing their daily routines.

Not evidenced:

• Specific customer segments or personas.
• Market size or user base.
• Any customer acquisition strategy or user feedback.
• Whether the developer has identified a broader market need beyond personal use.

The description states:

• No explicit pricing model is mentioned.
• The app was built as a personal project, not a commercial product.
• It is described as a prototype or hackathon submission.

Inferred from the description:

• There is no evidence of monetization plans or pricing structure.
• The app may be intended for personal use only, with no commercial intent.

Not evidenced:

• Revenue model (e.g., freemium, subscription, one-time purchase).
• Pricing strategy or any commercial viability.
• Any partnerships or distribution channels.
• Whether the developer has considered scaling or monetizing the product.

The description states:

• Built with Azure, C#, SQL, and Uno platform.
• Initially prototyped in Replit, then rearchitected using .NET 10, Flutter, and eventually Uno.
• AI tools like Codex and ChatGPT 5.6 were used for development.

Inferred from the description:

• The developer has experience with modern development frameworks and AI-assisted coding.
• The app is built with a focus on cross-platform compatibility (Uno platform).

Not evidenced:

• Technical performance or scalability.
• App stability or reliability.
• Any production deployment or infrastructure details.
• Whether the app is available for public use.

The description states:

• This was a hackathon submission to the OpenAI 2026 hackathon.
• The developer has not yet validated the product beyond personal use.
• UI issues remain, and performance problems were encountered during development.

Inferred from the description:

• There is no evidence of user adoption or engagement.
• The app is in early development or prototype stage.
• No metrics on usage, retention, or growth are provided.

Not evidenced:

• Any user base or customer data.
• Product maturity or roadmap beyond the hackathon.
• Any traction indicators such as downloads, signups, or feedback.
• Whether the developer plans to continue building or launching the product.

The description states:

• The app was built to address issues with existing apps (e.g., privacy, cost, fragmentation).
• It aims to consolidate multiple tools into one.

Inferred from the description:

• CalDo competes with various fitness and productivity apps.
• It is positioned as an AI-enhanced alternative to traditional workout tracking or coaching tools.

Not evidenced:

• Specific competitors or market analysis.
• Competitive advantages or differentiators.
• Market share or competitive positioning.
• Any market research or user preference data.

The description reveals:

• The app is a single-developer project, likely in early prototype stage.
• Performance and UI issues were encountered during development.
• AI features are limited to bodyweight squats and have not been tested on other exercises.
• No evidence of monetization or commercial viability.

Inferred from the description:

• Risk of technical failure or lack of scalability.
• Risk of low user adoption due to limited functionality or UI issues.
• Risk of no viable business model or path to market.

Not evidenced:

• Any risk mitigation strategies.
• Financial or operational risks beyond the developer's personal capacity.
• Any external validation or support.

1. What is your plan for validating demand and user interest beyond personal use?
2. How do you intend to monetize the app, if at all?
3. What are the technical limitations of the AI features (e.g., workout types supported)?
4. Are there any plans to scale or improve the UI/UX beyond current prototype?
5. Have you considered partnerships or integrations with existing fitness or productivity platforms?
6. How do you plan to acquire users if this is intended for a broader audience?