OpenAI 2026 hackathon

Pirate Pearls

Ever only have your Apple Watch on you, and have the need to game a bit? Play this classic reimagined match-three colored ball shooter and see how far you can go. With simple controls and fun in mind!

Solo project by Jonathan Klopper · 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,954 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

Company: Pirate Pearls

Self-reported basis: The description provided by the author is the only evidence. No third-party verification, revenue, customer data, or traction metrics are available.

What it appears to be: A mobile game for Apple Watch, rebuilt from a 20-year-old Java ME match-three puzzle game using AI tools like Codex and Swift.

What changed: The original game was reimagined with modern visuals, controls, and gameplay mechanics, but not simply ported.

Single most important open question: Is there any evidence of monetization or user engagement beyond the author's own playtesting?

Back to contents

What The Product Actually Is

The description states that Pirate Pearls is a fast, pick-up-and-play underwater match-three pearl shooter for Apple Watch. It involves:

  • Aiming with the Digital Crown or ship’s wheel
  • Firing pearls to make matches
  • Unlocking power-ups
  • Stopping the sea from filling up

The game is described as:

  • Colorful
  • Relaxing
  • Chaotic
  • Suitable for short play sessions

It was rebuilt using Swift and SwiftUI, with input from Codex. The original source code came from a Java ME project built nearly 20 years ago.

Inference: The product is a mobile game, not a SaaS or B2B tool. It’s a consumer-facing entertainment app.

Back to contents

Positioning & Claim Evolution

The author claims:

  • The game is a "classic reimagined match-three colored ball shooter"
  • It was built with "simple controls and fun in mind"
  • It's designed to be played during short breaks, especially when the user has their Apple Watch on
  • It’s a "rebirth" of an old game, not just a port

The positioning is:

  • Nostalgic
  • Casual
  • Mobile-first (Apple Watch)
  • Focused on accessibility and ease-of-use

Claim vs. Fact: The author states the game is “fun” and “perfect for a few spare minutes,” but no evidence of user feedback or engagement exists.

Back to contents

Target Customer & ICP

The description does not state:

  • Who the target customer is
  • What segment or persona this product is aimed at
  • Whether there are any specific demographics or use cases

Not evidenced: No explicit customer profile, ICP, or target market defined.

Back to contents

Business Model & Pricing Evidence

The description does not mention:

  • How the game will be monetized (e.g., paid download, in-app purchases, ads)
  • Any pricing strategy
  • Whether it’s free-to-play or premium

Not evidenced: No business model or pricing information is provided.

Back to contents

Technical & Delivery Signals

The project was built using:

  • Swift and SwiftUI
  • Codex (AI coding assistant)
  • Xcode
  • J2ME (as reference source)

The author notes:

  • The original Java ME code was used as a reference
  • The game was rebuilt from scratch, not ported
  • AI tools were used to help translate and refine the mechanics
  • Testing was difficult due to Apple Watch quirks

Inference: The development process involved modern iOS tooling and AI-assisted coding. However, no evidence of scalability, performance metrics, or production deployment is given.

Back to contents

Traction & Maturity Signals

The description states:

  • The game is nearly complete
  • It’s expected to be released on the App Store soon
  • The author is proud of how it “feels” like a native Apple Watch app
  • It was submitted to a hackathon (OpenAI 2026)

Not evidenced: No data on downloads, user engagement, retention, or post-launch performance.

Back to contents

Competitive Context

The description does not mention:

  • Competitors in the match-three genre for Apple Watch
  • Similar games or platforms
  • Market size or competitive positioning

Not evidenced: No competitive analysis or market context is provided.

Back to contents

Key Risks & Red Flags

  • No monetization strategy is evident, which raises questions about viability.
  • The product is a single-person project with no team or external support.
  • It’s unclear whether it will be released as a paid app or free-to-play.
  • The author has not provided any user feedback or data on gameplay.
  • The game is described as “fun” but lacks evidence of broader appeal or traction.

Inference: The lack of revenue, customer data, and business model makes this a high-risk investment or partnership opportunity.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the monetization strategy for Pirate Pearls?
  2. How many users have played the game so far, and what feedback have you received?
  3. Are there plans to expand beyond Apple Watch (e.g., iOS, Android)?
  4. What are your long-term goals for the game—will it be a standalone product or part of a larger ecosystem?
  5. Have you considered partnerships with Apple or other platforms?

Back to contents

Investment/Partnership Verdict

The description is self-reported and unverified, and contains no evidence of:

  • Revenue
  • Customers
  • Traction
  • Business model
  • Market data

Verdict: Based on the provided information, there is no commercial due-diligence basis to support an investment or partnership decision. The project appears to be a personal hobby or hackathon effort with no demonstrated commercial viability or market traction.

Confidence level: Low. The evidence is minimal and entirely self-reported.

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.