OpenAI 2026 hackathon

CalT: a frictionless calorie tracker for Android

CalT: AI-powered meal logging that turns a food photo into practical calorie and macro tracking in seconds, built on top of OpenNutriTracker.

Solo project by ishi vj · 0 likes · 0 comments

Archive position — measured, not model output

0 likes on Devpost

2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #3,096 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

What the company appears to be

CalT is an Android calorie-tracking app built as a self-contained application on top of OpenNutriTracker. The author states it uses AI (via Codex and GPT-5.6) to estimate calories, macros, and portions from food photos, with optional integration of user-provided AI providers through BYOK (Bring Your Own Key). It includes features like a “CalT Coach” for personalized feedback and an “Ask CalT” function for follow-up questions.

What changed

The project was submitted to the OpenAI 2026 hackathon. The author describes iterative development using Codex, with focus on reducing friction in meal logging, especially through AI photo recognition and local data storage.

Single most important open question

Is there any evidence of user adoption or engagement beyond the developer’s own testing? The description states no revenue, customers, or traction data are available.

Back to contents

What The Product Actually Is

The description states that CalT is a frictionless calorie tracker for Android, built on top of OpenNutriTracker. It allows users to log meals via search, barcode scanning, custom entries, or photo uploads. AI features estimate food items, portions, calories, protein, carbs, and fat from photos, which users can review and edit before saving.

It includes:

  • A “CalT Coach” that reviews today’s meals based on user profile, goals, and diary.
  • An “Ask CalT” feature for follow-up questions.
  • Optional AI integration via BYOK (Bring Your Own Key).
  • Local storage of diary data.
  • Encrypted API key storage.

The app was built as a Flutter application with its own Android package ID, name, branding, and APK.

Evidence

  • The author states: “CalT is a frictionless calorie tracker for Android, built on top of OpenNutriTracker.”
  • “Users can log meals by searching for food, scanning barcodes, adding custom meals, or uploading a meal photo.”
  • “AI photo feature estimates foods, portions, calories, protein, carbohydrates, and fat.”
  • “CalT Coach gives a short review of today’s meals based on the user’s profile, goals, and diary.”
  • “Ask CalT lets users ask follow-up questions about their meals.”
  • “AI is optional. Users can connect their own provider, such as OpenAI, Gemini, Anthropic, or an OpenAI-compatible service, through BYOK.”

Inference The app appears to be a standalone Android application with AI-enhanced features, but not a full-fledged SaaS product.

Back to contents

Positioning & Claim Evolution

The author positions CalT as a frictionless calorie tracker, aiming to reduce the time and effort required for meal logging. The core claim is that it improves upon existing tools like OpenNutriTracker by automating parts of the process using AI, particularly through photo-based estimation.

Evidence

  • “I used OpenNutriTracker to track calories, but I found the process slow.”
  • “CalT was created to bring meal estimates, diary tracking, and personal AI feedback into one Android app.”
  • “We are proud that CalT solves a real personal problem: reducing the time and effort needed to track meals.”

Inference The positioning evolved from solving a personal pain point (slow tracking) to offering an integrated solution with AI. However, no evidence of market validation or user feedback beyond the developer is provided.

Back to contents

Target Customer & ICP

The description does not explicitly define a target customer or ideal customer profile (ICP). It implies that CalT is for individuals who track calories and want a streamlined experience, particularly those interested in AI-assisted nutrition logging.

Evidence

  • “CalT Coach gives a short review of today’s meals based on the user’s profile, goals, and diary.”
  • “Ask CalT lets users ask follow-up questions about their meals.”

Inference The target is likely health-conscious individuals or those using calorie tracking apps for weight management or dietary goals. No segmentation or persona details are provided.

Back to contents

Business Model & Pricing Evidence

There is no evidence of a business model or pricing structure in the description. The app appears to be a personal project submitted to a hackathon, with no indication of monetization plans, subscriptions, or paid features.

Evidence

  • “AI is optional. Users can connect their own provider, such as OpenAI, Gemini, Anthropic, or an OpenAI-compatible service, through BYOK.”
  • “The app keeps diary data locally. API keys are stored in encrypted platform storage.”

Inference If monetized, it would likely rely on user-provided AI subscriptions (BYOK), but no pricing or revenue model is stated.

Back to contents

Technical & Delivery Signals

CalT was built as a Flutter application, with a separate Android identity from OpenNutriTracker. It includes:

  • Local data storage.
  • Encrypted API key handling.
  • BYOK for AI provider integration.
  • A seven-day sample diary for testing.
  • APK packaging.

Evidence

  • “We built CalT as a Flutter application and prepared it as a separate Android app with its own package ID, name, branding, and APK.”
  • “The app keeps diary data locally. API keys are stored in encrypted platform storage.”
  • “We used Codex with GPT-5.6 to develop and improve the project iteratively.”

Inference The technical stack is standard for mobile development (Flutter), and the use of Codex suggests rapid prototyping. No evidence of scalability, backend infrastructure, or API integrations beyond local storage.

Back to contents

Traction & Maturity Signals

There is no evidence of traction, user adoption, or product maturity beyond the developer’s own testing. The project was submitted to a hackathon and includes only a sample diary for judges to test.

Evidence

  • “We added a seven-day test diary so judges can test the dashboard, diary, calendar, and coach quickly.”
  • “This project was submitted to the OpenAI 2026 hackathon on Devpost.”

Inference The app is in early development or prototype stage. No data on downloads, retention, or user engagement is provided.

Back to contents

Competitive Context

The description does not mention any competitors or market positioning relative to existing calorie-tracking apps. It only references OpenNutriTracker as a prior tool the author used.

Evidence

  • “I used OpenNutriTracker to track calories, but I found the process slow.”
  • No mention of other apps or platforms in the market.

Inference CalT likely competes with general calorie-tracking apps and possibly AI-enhanced nutrition tools. However, no competitive analysis is evident.

Back to contents

Key Risks & Red Flags

  1. No traction or user data: The app is a hackathon submission with no evidence of real-world usage.
  2. AI dependency without monetization: AI features are optional but not monetized; unclear how the team plans to sustain them.
  3. BYOK model may limit adoption: Users must provide their own API keys, which could reduce usability or engagement.
  4. No scalability or infrastructure: The app is built for local storage and lacks backend or cloud integration.
  5. Unverified claims: All statements are self-reported; no third-party validation.

Evidence

  • “Everything above is the authors' own account. It is not independently verified, and no revenue, customer or traction data is available beyond what they state.”
  • “We added a seven-day test diary so judges can test the dashboard, diary, calendar, and coach quickly.”

Back to contents

Diligence Questions To Ask The Founders

  1. What is your plan for monetization or user acquisition?
  2. Have you tested the AI photo feature with real users beyond the sample data?
  3. How do you intend to handle API key errors or provider compatibility issues?
  4. Is there a roadmap for expanding beyond Android or integrating with other platforms?
  5. What are the limitations of the current AI model in terms of accuracy and user feedback?

Back to contents

Investment/Partnership Verdict

Not evidenced.

The description does not provide sufficient evidence to assess whether this project is ready for investment or partnership. It is a hackathon submission with no traction, revenue, or customer data. The author’s own account indicates the app is in early development and has not been validated in the market.

Confidence Low. The entire analysis is based on self-reported claims from one developer, with no external validation or evidence of product-market fit.

Back to contents

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.

The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.