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 #6,615 place in the like-ranked listing is a tie-break inside that group, not a ranking.
Projects (log scale)
Likes on Devpost. ▲ marks this project's group.
Show the figures
| Likes | Projects | Share of archive |
|---|---|---|
| 0 | 5,592 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 285 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
Executive Summary
SelfCare is a self-reported personal and family health tracker built as a mobile-first application with a web interface, using FastAPI and SQLite. The author states it supports daily logging of health data including fluids, medicines, vitals, food, symptoms, and clinical events, with features like trend charts, reminders, and Excel exports. It is positioned to help families manage everyday care and prepare for medical reviews.
The project has no evidenced traction, revenue, or customer base. The author describes a single-person team (Kanika Garg) and does not provide evidence of product-market fit, adoption, or monetization. The description is self-reported and unverified; it contains claims but no facts.
The single most important open question: Is there any evidence that the target users—families managing chronic or complex health conditions—have a real need for this tool, or that they would pay for it?
What The Product Actually Is
The description states that SelfCare is a personal and family health tracker, built as a mobile-first FastAPI application with SQLite storage. It supports:
- Daily health logging
- Linked family profiles
- Reminders
- Clinical records
- Trend charts
- Doctor-friendly history
- Excel exports
It was built using JavaScript, FastAPI, codex, and gpt5.6, and is described as a responsive web interface with profile-based access and configurable tracking measures.
Inference: The product appears to be a lightweight, offline-capable tool for personal or family health data management, likely intended for caregivers or patients managing chronic conditions.
Positioning & Claim Evolution
The author states that SelfCare was inspired by the difficulty of tracking their paraplegic father’s health, and aims to help families turn daily care into a clear, private health record. The tagline is: “SelfCare helps families turn daily care into a clear, private health record—tracking fluids, medicines, vitals, food, and symptoms so trends are ready for every medical review even without internet.”
The author also states that the tool supports “fluid balance, BP, diabetes, thyroid, food nutrition, medicines, stool, menstrual cycles, symptoms, vaccinations, eyesight, catheterization, and more.”
Inference: The positioning is to serve as a private, offline-capable health log, with an emphasis on family care and medical review preparation. It claims to simplify complex health data entry and visualization for caregivers or patients.
Target Customer & ICP
The author states that SelfCare helps families turn daily care into a clear, private health record. It is described as useful for tracking fluids, medicines, vitals, food, symptoms, bowel patterns, and clinical events, especially for those managing chronic or complex conditions like paraplegia.
The product is intended for caregivers and patients, particularly in situations where health data must be tracked over time and shared with clinicians.
Inference: The ICP appears to be families or individuals managing chronic or complex health conditions, with a focus on offline use, privacy, and clinical readiness. No evidence of segmentation or user personas is provided.
Business Model & Pricing Evidence
The description does not state any business model, pricing, monetization strategy, or revenue streams. The author mentions future plans such as secure cloud storage, caregiver sharing permissions, clinician-ready reports, and integrations with wearables, but no current commercial structure is described.
Inference: No business model or pricing evidence is available. The project appears to be a prototype or proof-of-concept, not yet monetized or scaled.
Technical & Delivery Signals
The author states that the product was built using:
- FastAPI
- SQLite storage
- JavaScript
- codex
- gpt5.6
It is described as a mobile-first application with a responsive web interface, supporting profile-based access and configurable tracking measures.
The team size is stated to be 1 person (Kanika Garg).
Inference: The technical stack suggests a lightweight, self-contained solution, likely intended for personal or family use, with an emphasis on offline functionality. The use of AI tools like codex and gpt5.6 indicates a developer-focused prototype rather than a commercial-grade product.
Traction & Maturity Signals
The description does not provide any evidence of traction, including:
- Number of users
- Customer adoption
- Revenue or monetization
- Product usage metrics
- Market validation
The author states that the project was submitted to the OpenAI 2026 hackathon, and that it is a single-person effort.
Inference: No traction or maturity signals are evident. The product appears to be in an early development stage, likely a prototype or MVP.
Competitive Context
The description does not mention any competitors or existing solutions in the health tracking space. It does not reference similar tools or platforms that may already exist for personal or family health logging.
Inference: No competitive context is provided. The author does not state whether there are existing tools addressing this use case, nor how SelfCare would differentiate from them.
Key Risks & Red Flags
- No evidence of traction or adoption — the project appears to be a prototype with no user base.
- Single-person team — limits scalability and development capacity.
- No commercial model — no indication of monetization, pricing, or revenue.
- Unverified claims — all features and functionality are self-reported without independent validation.
- Offline-first design — while a strength for some use cases, it may limit integration with modern health systems or data sharing.
- Lack of clinical validation — no mention of medical or regulatory compliance or input from healthcare professionals.
Diligence Questions To Ask The Founders
- What is the actual need in the market for this tool? Have you spoken to families or caregivers who would use it?
- How do you plan to validate that users will pay for this product, and what pricing model are you considering?
- What clinical or regulatory considerations have you taken into account, especially around data privacy and health record accuracy?
- Are there any existing tools in the market that already solve this problem? How does SelfCare differ?
- What is your roadmap for scaling beyond a single-person development effort?
Investment/Partnership Verdict
Not evidenced.
The description provides no evidence of traction, revenue, or customer validation. The project appears to be a self-reported prototype, likely built as part of a hackathon, with no indication of commercial viability or market readiness.
There is no basis for investment or partnership consideration at this stage. Any future value would depend on whether the team can demonstrate real user need, build a scalable product, and establish a viable business model.
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.