closetise

Company: closetise

Self-reported basis: The description is entirely self-reported by the author, unverified, and submitted as part of an OpenAI Build Week hackathon project. No external corroboration exists.

What it appears to be: A personal wardrobe tracker built as a Progressive Web App (PWA), using AI coding assistance for JavaScript logic while manually writing HTML/CSS. It tracks clothing items, enforces wear limits, and flags items as "dirty" once max wear is reached.

What changed: The project evolved from a personal problem — tracking clean/dirty clothes — into a functional prototype with AI-assisted development.

Single most important open question: Is there any evidence of user adoption or traction beyond the author's own use, and what are the implications for scalability or monetization?

The description states that closetise is a wardrobe tracker built as a Progressive Web App (PWA). It allows users to:

• Add clothing items with a photo, category, and description.
• Set a maximum wear count per item.
• Automatically lock an item as "dirty" once the wear limit is hit.
• Track laundry state (e.g., "cleaning", "clean").
• Filter, sort, and search by name or category.
• Display last-worn dates.

It was built using HTML5, CSS, JavaScript, with no frameworks. Data is stored in localStorage. The app is installable on mobile devices like a native app.

Inference: The product is a lightweight, personal tool for managing clothing inventory and hygiene habits. It is not a marketplace or SaaS platform.

The author states that closetise was inspired by a personal need to avoid reusing dirty clothes or washing clean ones. It aims to enforce a habit through automation — flagging items as dirty once worn too many times, rather than relying on guesswork.

It is positioned as a personal productivity tool, not a commercial product or service. The author explicitly mentions that the project was built during a hackathon and is not intended for mass adoption or monetization.

Inference: The positioning is minimal and self-contained — it does not claim to be part of a larger ecosystem, nor does it suggest any commercial intent beyond personal use.

The description states that the author is a Software Engineering student, and the app was built for personal use. There is no evidence of a defined customer persona or target segment beyond the individual user who has a closet and wants to track clothing hygiene.

No mention of:

• Demographics
• Customer segments
• Use cases beyond personal tracking
• Target markets or verticals

Inference: The ICP is not defined, and there is no evidence of a broader market or customer base.

There is no evidence in the description of any business model or pricing structure. The app is described as a personal tool built during a hackathon, with no indication of monetization plans, subscriptions, or paid features.

Inference: No business model or pricing data is evidenced.

The project was built using:

• HTML5, CSS, JavaScript
• No frameworks
• No backend
• Data stored in localStorage
• Built with Codex, an AI coding agent, for JavaScript logic and state management
• Manual review of all AI-generated code before acceptance
• Git commits used as checkpoints

The app is installable as a PWA, and the author mentions:

• Handling image size and quota errors from localStorage
• PWA requirements like manifests, service workers, and icon sizing

Inference: The technical stack is minimal and self-contained. The use of AI for JavaScript logic suggests an experimental or learning-oriented approach rather than a scalable development process.

The description states that this was a hackathon project, built in a short timeframe, and submitted to the OpenAI 2026 Build Week hackathon. There is no evidence of:

• Users
• Revenue
• Customer adoption
• Product usage metrics
• Iteration beyond initial prototype

Inference: No traction or maturity signals are evidenced.

There is no mention in the description of competitors or similar products. The author does not reference any existing wardrobe or clothing tracking tools, nor does the project describe how it differentiates from them.

Inference: No competitive context is provided.

• No traction or adoption beyond the author’s personal use.
• localStorage-based storage limits scalability and persistence.
• Single-person team, no evidence of a product-market fit or team structure.
• Hackathon project, not a commercial endeavor — likely not intended for growth or monetization.
• AI-assisted development may indicate lack of deep technical rigor or process maturity.

Inference: The project is experimental, personal, and not scalable. It lacks any evidence of commercial viability or traction.

1. What is the actual user base beyond the author?
2. Are there plans to move off localStorage to a backend for scalability?
3. Has the app been tested by others outside the author’s immediate circle?
4. What are the long-term goals for the product — is it intended to evolve into a commercial offering?
5. How does the author plan to handle data persistence and backup in a real-world scenario?