SignalArc

SignalArc is a self-reported personalized wellness-learning app built by a physician-founder with no prior software background. The product uses AI to structure user inputs around outcomes, interventions, observations, and signals, aiming to help users learn from their wellness routines over time. It supports both guided and detailed modes, with initial focus on cannabinoid and cannabis-adjacent wellness but broader applicability across supplements, botanicals, and lifestyle interventions.

The app is described as a working mobile beta built with React Native, Expo, and TypeScript, connecting to a Vercel backend and Supabase infrastructure. AI is used for structured product scanning and extraction from labels or QR codes, with results presented as drafts for user review. The system includes fallback behavior when AI services are unavailable.

Key claims include:

• Not a generic chatbot or static tracker
• Designed around the learning process between recommendations and isolated events
• Uses AI to organize messy information while keeping users in control
• Supports both Guided and Detailed modes
• Built with AI tools (Codex, GPT-5.6) during OpenAI Build Week

The single most important open question is whether SignalArc has achieved meaningful user adoption or traction beyond the founder's own use case, as no evidence of customers, revenue, or usage metrics is provided.

The description states that SignalArc is a "personalized wellness-learning app for everyday life." It is described as an app that helps users:

• Choose desired outcomes
• Build pathways
• Add products or routines
• Record what happened
• Review patterns over time

The core workflow is defined as: Outcome → Pathway → Interventions → Observations → Signals → Arc → Better Decisions.

SignalArc is built as a cross-platform mobile application using React Native, Expo, and TypeScript. It connects to a Vercel backend and Supabase infrastructure. The app supports:

• iOS TestFlight beta access
• Guided and Detailed modes
• Product scanning via camera or QR codes
• Structured product intelligence extraction from AI
• Signal and Arc views for pattern recognition
• Export tools

The system is described as having a "learning loop" where one observation is not treated as proof, but repeated comparable observations may become signals that accumulate into an arc.

The description states that SignalArc is positioned as:

• Not a generic wellness chatbot
• Not a static tracker
• Not a one-time recommendation engine
• A tool built around the learning process between recommendations and isolated events

It claims to be different from other tools because it treats:

• A Pathway as a structured starting point, not a prescription
• One Observation as not proof
• Repeated comparable Observations as potential Signals
• Signals accumulating into an Arc that helps users understand what appears to work

The positioning evolved from a narrower product pathway (originally named CARTA) to a broader system called SignalArc. The author notes that the app started as a "narrower product pathway" before expanding into the broader SignalArc system.

The description states that SignalArc is initially designed for people managing:

• Multiple supplements
• Botanical products
• Cannabinoid wellness products
• Routines
• Lifestyle interventions

It specifically mentions that one of its first use cases is cannabinoid and cannabis-adjacent wellness, where product variability, dose, timing, format, setting, and individual response all matter.

The target customer appears to be:

• Individuals who want a clearer record of what helps with their wellness routines
• People managing multiple wellness products or interventions
• Users interested in personalization through experience rather than recommendations

The description mentions "eight Outcome Domains" but does not specify what these domains are. It also notes that the app supports both Guided Mode (approachable for first use) and Detailed Mode (for deeper review).

Not evidenced.

The description provides no information about:

• Revenue model
• Pricing structure
• Monetization strategy
• Customer acquisition costs
• Unit economics
• Any commercial arrangements or business development activities

All claims in the description are self-reported and unverified, with no evidence of actual business operations or financial metrics.

The app is described as built with:

• React Native
• Expo
• TypeScript
• Node.js
• Vercel backend
• Supabase infrastructure
• OpenAI API integration (specifically OpenAI's Responses API)
• Codex and GPT-5.6 for development assistance during Build Week

Key technical elements mentioned include:

• Mobile beta with iOS TestFlight access
• Structured product intelligence extraction from labels or QR codes
• Confidence and quality indicators in AI results
• Fallback behavior when AI or network services are unavailable
• Backend health checks
• Cross-platform behavior maintenance
• OpenAI credentials kept off device
• Product-label images sent to server-side endpoint

The description notes that the app uses "OpenAI's Responses API through a secure Vercel server-side runtime" and that model selection is configurable through environment variables.

Not evidenced.

The description states that SignalArc:

• Existed as an early mobile beta before Build Week
• Has a working mobile beta with TestFlight access for judges
• Has a private source repository documenting Build Week work
• Is described as "a real working beta, not just a concept"

However, there is no evidence of:

• Customer base or user adoption
• Revenue or monetization
• Usage metrics or engagement data
• Product-market fit validation
• Any traction beyond the founder's own use case

The description explicitly states that this is a self-reported account with no independent verification.

Not evidenced.

The description does not mention:

• Direct competitors
• Market size or opportunity
• Competitive advantages or disadvantages
• Market positioning relative to existing wellness apps
• Any competitive landscape analysis

The author states that SignalArc is "not a generic wellness chatbot, static tracker, or one-time recommendation engine" but provides no comparison to actual products in the market.

Inferences based on self-reported information:

1. Founder background risk: The description states the founder has no coding or app-development background, which may indicate potential technical execution risks or lack of deep product understanding.

1. AI dependency risk: The system heavily relies on AI for product scanning and extraction, with fallback behavior described as "clearly labeled local review." This suggests potential reliability issues if AI services are unavailable.

1. Medical boundary risk: The description states the app is designed to avoid medical claims or diagnostic tools, but there's no evidence of how this boundary will be maintained in practice or enforced.

1. Product-market fit uncertainty: The app appears to be a self-reported beta with no evidence of customer adoption or market traction beyond the founder's own use case.

1. Scalability concerns: The description mentions "private source repository" and "TestFlight access for judges," suggesting limited public availability and potential scalability issues.

1. AI tool dependency: The product was built using Codex and GPT-5.6 during Build Week, but the production system uses gpt-4.1-mini as default, indicating a potential gap between development and production capabilities.

1. What is your specific customer acquisition strategy and how do you plan to scale beyond the founder's own use case?

1. How do you plan to maintain the boundary between wellness guidance and medical advice without risking regulatory issues?

1. What are the actual technical limitations of the current beta that would prevent it from being production-ready?

1. How do you intend to monetize this product, and what is your revenue model?

1. What specific metrics or data points indicate successful user engagement or learning outcomes?

1. How do you plan to handle privacy and data security concerns given the personal nature of wellness information?

1. What are the actual limitations of the AI-powered product scanning that users might encounter?

1. How do you plan to validate that the "learning loop" actually produces better decisions rather than just more data entry?

1. What is your timeline for moving beyond beta status and achieving market readiness?

1. How do you plan to compete with existing wellness tracking tools in the marketplace?