Archive position — measured, not model output
1 like on Devpost
506 of the 7,856 archived projects have more likes, and 1,758 share exactly 1 — so this project's #1,376 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
What the company appears to be
Livia Beikost is a self-reported German-Chinese baby-weaning assistant app built by one developer (Jan Kai) for personal use. The app provides age-based food guidance, allergy alerts, TCM food types, meal planning, diary and progress tracking. It was submitted as a project to the OpenAI 2026 hackathon.
What changed
The author states that this is their first fully usable app, built using Codex and structured data. It has been adopted by the developer’s wife in daily life, with positive feedback. The app is described as mobile-first and self-contained, using local storage for user data.
Single most important open question
Is there evidence of external adoption or traction beyond the founder's personal use?
What The Product Actually Is
The description states that Livia Beikost is a German-Chinese baby-weaning assistant. It offers:
- Age-based food guidance
- Food pairing and incompatibility information
- Allergy-status tracking
- TCM (Traditional Chinese Medicine) food classifications
- Feeding diary
- Meal planning
- Progress tracking
It was built as a mobile-first, self-contained HTML application, using Codex for implementation. The app’s content is managed through structured data, and user records are stored via local storage.
Evidence
- Author's own write-up
- Technology tags: babel, codex, css3, html5, javascript, jsx, localstorage, lovable, openai, react
Inference The app appears to be a personal tool built for a specific niche (German-Chinese caregivers of infants), not a commercial product.
Positioning & Claim Evolution
The author states that the app was inspired by the need to reduce the workload of caregivers during infant weaning. It is positioned as a practical assistant that supports healthy and safe development while managing food research, planning, and recording.
It claims to be:
- A German-Chinese baby-weaning assistant
- Designed for caregivers monitoring allergic reactions
- A tool for age-based guidance, food pairing, allergy alerts, and TCM food types
Evidence
- Inspiration section
- What it does section
Inference The positioning is narrow and personal, not a broad commercial product. The claim of being the first usable app by the author indicates a personal project rather than a scalable product.
Target Customer & ICP
The description states that the app is for caregivers of infants starting solid foods, particularly those monitoring for allergic reactions. It is tailored to German-Chinese contexts, including TCM food classifications.
Evidence
- Inspiration section
- What it does section
Inference The target customer is likely a parent or caregiver in a German-Chinese household, with specific needs around infant nutrition and allergy management.
Business Model & Pricing Evidence
There is no evidence of any business model or pricing structure. The app is described as a personal project built by one developer for use by the founder’s wife.
Evidence
- No mention of monetization
- No pricing, subscriptions, or sales channels
Inference No commercial business model is evident from the description.
Technical & Delivery Signals
The app was built using:
- Codex
- HTML5, CSS3, JavaScript, JSX
- React
- Local storage for data persistence
- Structured data management
It is described as a mobile-first, self-contained HTML application. The developer notes challenges in building a logical architecture and translating complex knowledge into user-friendly interactions.
Evidence
- How it was built section
- Technology tags
Inference The app is a lightweight, personal tool with no external dependencies or cloud infrastructure. It’s not scalable or production-ready.
Traction & Maturity Signals
The description states that:
- The app is fully usable
- The developer’s wife is using it in daily life
- Feedback has been positive
- It was submitted to a hackathon (OpenAI 2026)
There is no evidence of external users, revenue, or adoption beyond the founder.
Evidence
- Accomplishments section
- Context: hackathon submission
Inference The app shows early-stage maturity and personal adoption but lacks any signs of commercial traction or user base.
Competitive Context
No competitive landscape is described. The app appears to be a personal solution for a specific niche (German-Chinese caregivers), with no mention of competitors or market positioning.
Evidence
- No mention of competitors
- No market analysis or differentiation
Inference The product may not have a defined competitive space, as it is a personal tool rather than a commercial offering.
Key Risks & Red Flags
- No commercial traction or revenue: The app is described as personal use only.
- Single-person development: No team or external support.
- No scalability or infrastructure: Built as a self-contained HTML app with local storage.
- No professional medical input: The next steps include obtaining such input, suggesting the current version may lack clinical validation.
- Unverified claims: All descriptions are self-reported and unverified.
Evidence
- No mention of users beyond the founder’s wife
- No revenue or monetization
- No team or external support
Inference This is a personal project with no signs of commercial viability or scalability.
Diligence Questions To Ask The Founders
- What specific feedback has been received from the user (the developer's wife), and how has it shaped the app?
- Are there any plans to expand beyond the current scope, such as adding more languages or medical professionals?
- Has the founder considered integrating with existing baby care platforms or apps?
- Is there any intention to monetize this product, and if so, what model is being considered?
- What are the technical limitations of the current architecture that might prevent scaling?
Investment/Partnership Verdict
Not evidenced — There is no evidence of a commercial product, revenue, or traction beyond personal use.
Inference This is a personal project, not a scalable business opportunity. It does not meet criteria for investment or partnership at this stage. The app may evolve into a product with further development and external adoption, but as described, it is not a commercial entity.
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.