Wardrobe

Company: Wardrobe

Self-reported basis: The description is entirely self-reported and unverified, based on a Devpost submission for the OpenAI 2026 hackathon. No third-party corroboration, revenue, customer data or traction evidence is available.

What it appears to be: A personal closet management tool that uses generative AI to analyze daily outfit photos and build a temporal knowledge graph of user style preferences. It allows users to track what they wear, understand their style, and receive personalized recommendations.

What changed: The project was submitted as a hackathon entry, indicating an early-stage prototype or proof-of-concept with no commercial traction or product-market fit validated.

Single most important open question: Is there sufficient evidence of user demand or engagement to justify further development beyond the hackathon stage?

The description states that Wardrobe is a closet management app that uses AI to analyze daily outfit photos. It processes these images using Google AI Studio and stores data via Convex, with a temporal knowledge graph built by Zep. Users can track what they wear and receive personalized recommendations based on their style.

Evidence:

• “The user takes photos and google Gemini describes them.”
• “These are processed as episodes by Zep, which manages a temporal knowledge graph for each user.”
• “Users create a record of what they wear and can even see how well new items fit their style objectives when shopping.”

Inference: The app appears to be an AI-powered personal styling assistant that builds a user’s fashion profile over time.

The author states the app is designed to avoid “paternalistic” advice, aiming instead to help both fashion-conscious and clueless users. It leverages generative AI to model the full distribution of fashion and allows users to build their own personal recommendation system.

Evidence:

• “I wanted a closet management app that doesn't tell you how to dress in a paternalistic way.”
• “By taking a subject that is inherently opinionated, it's a great way to take advantage of how generative AI models the full distribution of fashion.”

Inference: The positioning is centered on personalization and user autonomy, using generative AI as a core differentiator.

The description states Wardrobe targets “the fashion conscious and clueless alike,” suggesting a broad audience. It also implies users who want to track outfits and understand their style preferences.

Evidence:

• “I wanted a closet management app that doesn't tell you how to dress in a paternalistic way, and could help the fashion conscious and clueless alike.”
• “Users create a record of what they wear and can even see how well new items fit their style objectives when shopping.”

Inference: The ICP is likely early adopters or users interested in personal style tracking, but no specific persona or segmentation is described.

No business model or pricing information is provided. The description does not mention monetization, subscriptions, or any revenue streams.

Evidence:

• Not evidenced.

Inference: The app appears to be a prototype with no commercial model defined.

The project was built using a monorepo architecture with technologies like GCP, Convex, Clerk, Expo, and Vercel. It uses image embeddings from Google AI Studio and Zep for temporal knowledge graphing.

Evidence:

• “GCP / Google AI Studio for image embeddings, Vercel for Web. Convex for object, vector storage, and application data.”
• “Expo for the mobile ports.”
• “Built with (author-declared): arcjet, axiom, clerk, convex, expo.io, gcp, posthog, typescript, vercel”

Inference: The stack suggests a modern, cloud-native approach to building a mobile and web app with AI integration.

No traction or maturity data is provided. The project was submitted as a hackathon entry, indicating an early-stage prototype.

Evidence:

• “This project was submitted to the OpenAI 2026 hackathon on Devpost.”
• “The routing of full outfits versus individual items...”
• “The self-updating user bio.”

Inference: The app has no verified users, revenue or product-market fit. It is a prototype.

No competitive analysis or market positioning is provided in the description. The author does not reference existing players in the fashion or closet management space.

Evidence:

• Not evidenced.

Inference: No information available to assess competitive landscape or differentiation.

• Unproven demand: The app is a hackathon project with no evidence of user adoption or engagement.
• No monetization strategy: No business model or pricing structure is described.
• Limited team: Only one team member (David Schmitt) is listed, suggesting limited development capacity.
• Unclear scalability: The prototype lacks data on performance, user retention, or system robustness.

Evidence:

• “Team size: 1”
• “This project was submitted to the OpenAI 2026 hackathon.”
• “No revenue, customer or traction data is available beyond what they state.”

1. What specific user problems are you solving, and how do you know users have these problems?
2. How did you validate the idea with real users before building this prototype?
3. What is your plan for monetization or revenue generation?
4. Are there any existing competitors in this space, and how does Wardrobe differentiate itself?
5. What are the key metrics you would track to assess product-market fit?