OpenAI 2026 hackathon

Perch

Perch is a personal pixel-art focus companion that gently notices when you get distracted, reacts through your own custom mascot, and helps you return to the work you meant to do.

Solo project by Alex Yan · 0 likes · 0 comments

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 #5,889 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

Perch is described as a personal pixel-art focus companion that notices when users get distracted and gently reacts through a custom mascot to help them return to their intended work. The product is self-reported as a tool for improving focus, built using technologies including React, TypeScript, Electron, and GPT-based components.

The author states this is a hackathon project submitted to the OpenAI 2026 hackathon, with no evidence of revenue, customers, or traction beyond its submission. The description does not indicate any commercialization or market adoption.

Single most important open question

Is there any evidence that Perch has moved beyond the prototype stage or demonstrated user engagement?

Back to contents

What The Product Actually Is

The description states: “Perch is a personal pixel-art focus companion that gently notices when you get distracted, reacts through your own custom mascot, and helps you return to the work you meant to do.”

  • Inferred: The product appears to be an application designed to improve user focus by monitoring behavior and prompting re-engagement with tasks.
  • Not evidenced: No details on how distraction is detected, what constitutes a "custom mascot", or whether the mascot is interactive or static.

The author declares that Perch was built using technologies including Electron, React, TypeScript, GPT, SQL, and others. It is described as a desktop application (via Electron) with a pixel-art aesthetic.

  • Inferred: The product likely runs on desktop platforms.
  • Not evidenced: No information about the actual UI/UX or functionality of the mascot or distraction detection mechanism.

Back to contents

Positioning & Claim Evolution

The description states: “Perch is a personal pixel-art focus companion that gently notices when you get distracted, reacts through your own custom mascot, and helps you return to the work you meant to do.”

  • Claim: Perch positions itself as a gentle, non-intrusive focus tool.
  • Not evidenced: No indication of how this differs from other focus tools or whether it has evolved from an earlier version.

The project is submitted to the OpenAI 2026 hackathon. This implies that the positioning may be early-stage and experimental.

  • Inferred: The product is likely in a pre-commercial, exploratory phase.
  • Not evidenced: No evidence of prior versions or claims about market fit or user feedback.

Back to contents

Target Customer & ICP

The description states: “Perch is a personal pixel-art focus companion that gently notices when you get distracted, reacts through your own custom mascot, and helps you return to the work you meant to do.”

  • Inferred: The target customer appears to be individuals who struggle with focus or need help staying on task.
  • Not evidenced: No specific user persona, segment, or demographic is described.

The author is a single individual (Alex Yan), suggesting that the product may be aimed at solo developers or self-employed professionals.

  • Inferred: The ICP may be self-directed workers or developers needing focus aids.
  • Not evidenced: No evidence of customer interviews, personas, or user research.

Back to contents

Business Model & Pricing Evidence

The description does not state anything about pricing, monetization, or a business model.

  • Not evidenced: No information on how Perch would generate revenue or whether it is intended to be free, paid, or ad-supported.

Back to contents

Technical & Delivery Signals

The author declares that the project was built with technologies including:

  • Chrome
  • Codex
  • CSS
  • Electron
  • Electron-Vite
  • GPT
  • HTML
  • Nano-Banana-Pro
  • React
  • SQL
  • SQLite
  • Tailwind
  • TypeScript
  • WebSocket
  • Inferred: The product is a desktop application built with modern web and AI technologies.
  • Not evidenced: No information on architecture, scalability, or delivery mechanism beyond the tech stack.

The project was submitted to a hackathon. This suggests it may be in an early prototype phase.

  • Inferred: Likely not production-ready.
  • Not evidenced: No evidence of deployment, testing, or performance metrics.

Back to contents

Traction & Maturity Signals

The description states that Perch is a submission to the OpenAI 2026 hackathon. It was built by one person (Alex Yan).

  • Inferred: The product is likely in an early-stage prototype.
  • Not evidenced: No evidence of user adoption, retention, or usage data.

No mention of any customers, revenue, or growth indicators.

  • Not evidenced: No signs of traction or market validation.

Back to contents

Competitive Context

The description does not provide any information on competitors or the competitive landscape.

  • Not evidenced: No indication of existing tools in the focus or productivity space that Perch might compete with or complement.

Back to contents

Key Risks & Red Flags

  • Risk: The project is described as a hackathon submission by a single individual, suggesting limited development resources and no clear path to commercialization.
  • Red Flag: No evidence of product-market fit, user feedback, or traction. The lack of any business model or pricing information raises questions about viability.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the core problem Perch solves, and how does it differ from existing focus tools?
  2. How does Perch detect distraction? Is this based on behavior tracking, keyboard/mouse activity, or something else?
  3. Has there been any user testing or feedback on the mascot interaction?
  4. What are the plans for monetization or commercialization beyond the hackathon?
  5. Are there any existing users or early adopters?

Back to contents

Investment/Partnership Verdict

The description states that Perch is a hackathon submission by one individual, with no evidence of traction, revenue, or customer engagement.

  • Inferred: The project is likely in an exploratory phase and not yet ready for investment or partnership.
  • Not evidenced: No indication of commercial viability, scalability, or strategic fit.

Verdict: Not ready for due diligence. The product lacks any demonstrated traction or market validation.

Back to contents

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.