Carbonly

• The description states that Carbonly is a PWA (Progressive Web App) built with vanilla JavaScript, HTML, and CSS.
• It is described as framework-free, with no backend dependencies.
• The app allows users to snap or upload a photo of a meal, journey, or energy use.
• Users can confirm what the item is, then receive an instant sourced CO₂e estimate.
• It includes a private, on-device dashboard that aggregates logged choices over time.
• The app uses a single items object where each entry stores its emissions factor with its source unit intact — e.g., kg CO₂e per kg, km, kWh.
• Data sources include:
  • Food factors from Poore & Nemecek’s global life-cycle dataset via Our World in Data
  • Travel and electricity factors from the UK Government's greenhouse gas conversion factors

Note

The description does not state whether this is a working prototype or a completed product, nor does it include any evidence of live usage or user feedback.

• The author states that Carbonly was built to address a frustration with existing carbon footprint tools — namely, that they ask too much upfront and provide estimates without transparency.
• The core design constraint is: every number must trace back to a clickable link.
• The app is positioned as a tool for personal carbon tracking, not a business or enterprise solution.
• It emphasizes honesty in data presentation, avoiding normalization of units that obscures assumptions.
• The author describes the tool as not just a calculator, but a way to make patterns visible over time through a dashboard.

Inference The positioning suggests a focus on individual behavior change, not enterprise or institutional use. It is not clear if this was intended as a long-term product or a proof-of-concept.

• The description does not name specific customer segments.
• The app is described as for individual users who want to track their carbon footprint in daily life.
• It targets people interested in personal sustainability, especially those who are frustrated with opaque carbon calculators.
• The tool is built for non-experts, aiming to make carbon footprinting accessible and transparent.

Note

No evidence of customer personas, user research, or target market segmentation is provided.

• The description does not state a business model or pricing structure.
• It is described as a static PWA with no backend, suggesting no monetization via subscriptions or transactions.
• There is no mention of advertising, freemium tiers, or any revenue-generating mechanism.

Inference If the app remains static and non-commercial, it likely has no business model at this stage. The author does not claim any monetization strategy.

• Carbonly is built as a PWA with:
  • A manifest
  • A service worker
  • Offline caching
• It uses vanilla JavaScript, HTML, and CSS, with no frameworks.
• The app stores data in a single items object that includes source units and links.
• The author states they divided food factors by ten to align with 100g portions, documenting this transformation in the README.
• Challenges include:
  • No photo recognition without an external API (which is avoided intentionally).
  • Managing comparisons across different measurement bases (e.g., per vehicle-km vs. per passenger-km).

Inference The technical approach is minimal and self-contained, but the app may not yet be fully functional in all aspects (e.g., offline support, installability).

• The project was submitted to the OpenAI 2026 hackathon, indicating a recent development phase.
• It is described as a self-reported prototype with no evidence of live users or adoption.
• There is no mention of revenue, customers, or usage metrics.
• The author notes that the app is not yet fully installable due to issues with service worker registration.

Note

No traction data or user engagement signals are provided. The project appears to be in a pre-product-market-fit phase.

• The description does not mention competitors.
• It positions itself as an alternative to carbon footprint calculators that ask long forms or provide vague estimates.
• The app is described as being built with a sourcing-first approach, which may differentiate it from tools that obscure data sources.

Inference While the author identifies a gap in current tools, no competitive analysis or market positioning is evident. The project does not appear to be part of an existing ecosystem.

• The app is described as static and framework-free, which may limit scalability or feature expansion.
• It avoids backend services (e.g., for photo recognition), which could restrict functionality in real-world use.
• There is no evidence of user testing, feedback, or adoption.
• The app is not yet fully installable due to issues with service worker registration.
• The project is not monetized, and no business model is described.

Inference The lack of traction, revenue, or product-market fit makes it a high-risk investment or partnership opportunity. It may be a prototype or proof-of-concept rather than a viable product.

1. What is the current status of the app? Is it fully functional, or still in development?
2. How many users have interacted with the app, if any?
3. Has the team validated the need for this tool through user interviews or surveys?
4. Are there plans to monetize or scale the product beyond its current prototype form?
5. What are the technical limitations of the PWA approach that might prevent future feature development?
6. How is the data being maintained and updated over time?