WhenToWater?

What the company appears to be: WhenToWater? is a self-reported iOS application designed to provide plant-specific outdoor watering advice for California homeowners using an ordinary garden hose. The app uses scientific data (e.g., CIMIS ETo zones, UC crop coefficients) and user inputs (e.g., hose flow measurement, recent rain) to recommend when and how long to water plants.

What changed: The project was built during a single hackathon event (Build Week), with the author stating that prior to this effort, they had only gathered research and planning documents but no functional product or recommendation engine. This submission represents an initial implementation of their concept.

Single most important open question: Is there any evidence of traction, revenue, or user adoption beyond the single developer's own testing and demonstration?

Note: All claims are self-reported by the author and unverified. No third-party data, customer feedback, or financial metrics are provided in the description.

The description states that WhenToWater? is an iOS app that provides plant-specific outdoor watering advice based on:

• Seasonal evapotranspiration (CIMIS ETo)
• Plant demand (UC crop coefficients)
• Watered area
• Hose flow rate
• Recent conditions (rain, previous watering)

It uses these inputs to calculate a recommendation for how long and how often to water plants using an ordinary garden hose.

The app is described as:

• Built with Swift and SwiftUI
• Using GitHub and Codex for development workflow
• Running locally on iOS without requiring backend or network connectivity
• Designed for use by homeowners holding a hose in one hand and a phone in the other

Claim: The product is an iOS application that provides personalized watering guidance.

Evidence: Author's own write-up.

Inference: The app likely performs deterministic calculations based on input data.

Evidence: Author states "deterministic, provider-neutral engine" and describes calculation chain from ZIP code to hose duration.

The author positions WhenToWater? as:

• A tool that brings irrigation intelligence to the person holding an ordinary hose
• An alternative to professional irrigation systems or controllers
• A way to avoid overwatering or under-watering without needing irrigation expertise

It is described as:

• Intended for "the ordinary hose in your hand and the human doing the watering"
• Not requiring accounts, APIs, or complex setup
• Focused on simplicity: “homeowners should not have to read six formulas”

The claim evolution appears to be:

1. Initial idea: Bring scientific irrigation logic to homeowners using a simple hose.
2. Development focus: Build a deterministic, local-first recommendation engine with traceable provenance.
3. Current state: A working prototype demonstrating one path (tomato plant, hose delivery).

Claim: The product aims to simplify irrigation decision-making for everyday users.

Evidence: Author's own write-up.

Inference: The positioning reflects a shift from academic or technical tooling toward consumer usability.

Evidence: Emphasis on "simple answer", "trustworthy action", and avoiding complexity.

The description states that the target customer is:

• Homeowners in California
• Who do not have irrigation controllers or professional training
• Who use a garden hose to water plants outdoors
• Who are often in sun glare, trying to decide how much water a plant needs

The ICP (Ideal Customer Profile) seems to be:

• A homeowner with a vegetable garden or landscape
• Using an ordinary garden hose for watering
• Seeking reliable, science-backed guidance without technical knowledge

Claim: The target customer is California homeowners using a garden hose.

Evidence: Author's own write-up.

Inference: The app targets people who are not experts but want accurate irrigation advice.

Evidence: Mention of lack of irrigation training and desire to avoid overwatering.

There is no evidence in the description of:

• Revenue model
• Pricing structure
• Monetization strategy
• Subscription or one-time purchase plans

The app is described as:

• Not requiring an account
• Having no backend or API keys
• Being local-first and offline-capable

Claim: No business model or pricing information is provided.

Evidence: Author's own write-up.

Key technical elements mentioned:

• Built with Swift, SwiftUI, iOS Simulator
• Uses GitHub for version control and Codex for development workflow
• GPT-5.6 (via Codex) assisted in implementation
• Local-first architecture with no network dependency
• Deterministic recommendation engine
• Persistence of measurements across navigation and relaunch
• 29 deterministic tests covering accuracy, source integrity, etc.
• ZIP-to-CIMIS zone lookup, historical ETo data, UC crop coefficients

Claim: The app is technically implemented using local-first principles with AI-assisted development.

Evidence: Author's own write-up.

Inference: The architecture supports offline use and scientific traceability.

Evidence: Description of local data handling, deterministic engine, provenance tracking.

There is no evidence of:

• Revenue
• Customers or user base
• Product adoption or usage metrics
• Market traction beyond the author’s own testing

The project is described as:

• A single developer's hackathon submission
• Demonstrating one path (tomato plant, hose delivery)
• Not yet expanded to other plants or delivery methods
• In early alpha stage with planned future features

Claim: No traction or maturity data is available.

Evidence: Author's own write-up.

The description does not mention:

• Direct competitors
• Market landscape
• Existing solutions in the irrigation space

It implies that current alternatives include:

• Professional irrigation controllers
• Irrigation certification or training programs
• General gardening apps (not specified)

Claim: No competitive context is provided.

Evidence: Author's own write-up.

Potential risks and red flags based on the description:

1. Single developer team – Limited capacity for scaling or feature development
2. No revenue or traction – No evidence of market validation or monetization
3. Limited scope – Only one plant type (tomato) and delivery method (hose)
4. Unverified scientific accuracy – App uses static data and deterministic logic, but no independent verification of its recommendations
5. AI-assisted development dependency – Reliance on GPT-5.6 may not be scalable or reproducible outside the original developer's environment

Claim: Several operational and strategic risks are present due to lack of validation and limited scope.

Evidence: Author's own write-up.

1. What is the source of the scientific data used (e.g., CIMIS, UC coefficients)? Is it publicly available or proprietary?
2. How does the app handle missing or uncertain inputs? Are there fallbacks or warnings?
3. Has the app been tested in real-world conditions beyond the author’s own testing?
4. What are the plans for expanding to other plants, delivery methods, and regions beyond California?
5. Is there any plan for monetization or commercial viability beyond personal use?
6. How is the recommendation engine validated? Are there peer-reviewed sources or expert reviews?
7. What is the long-term vision for the app’s architecture and data updates?

Note: These questions are based on the author's self-reported information and aim to probe deeper into unverified claims.