OpenAI 2026 hackathon

if I were dead

I created If I Were Dead to give people a safe and private space to record the words they may not have had the chance to say, the things they still want to do, and important personal arrangements.

Solo project by bdfj lfj · 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 #4,601 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

What the company appears to be

The project “if I were dead” is described as an iOS app that allows users to write private letters, wishes, and important personal arrangements in advance, with a focus on privacy, emotional comfort, and end-to-end encryption.

What changed

This is a self-reported submission for the OpenAI 2026 hackathon. No evidence of prior development, traction, or commercial activity exists beyond the author's own description.

The single most important open question

Is there any evidence of user adoption, revenue, or product-market fit beyond the initial concept and prototype?

Back to contents

What The Product Actually Is

The description states that “if I were dead” is an iOS app built with Swift and SwiftUI. It supports:

  • Writing private letters
  • Saving wishes
  • Adding guardians
  • Receiving messages
  • Recording important plans
  • Account synchronization
  • Friend connections
  • Notifications (via Apple Push Notification service)
  • End-to-end encryption for sensitive content

The backend is powered by PocketBase, which handles authentication, data synchronization, friendships, guardians, notifications, and membership services. Subscriptions are managed via Apple StoreKit.

Evidence

  • The author states the app is built with Swift, SwiftUI, and PocketBase.
  • It uses Apple Push Notification service for delivery.
  • End-to-end encryption is mentioned as a feature.

Inference The app appears to be a personal digital legacy or planning tool, designed around emotional and privacy concerns.

Back to contents

Positioning & Claim Evolution

The project is positioned as a safe and private space for people to record things they may not have had the chance to say, or important personal arrangements. The tagline says: “I created If I Were Dead to give people a safe and private space to record the words they may not have had the chance to say, the things they still want to do, and important personal arrangements.”

The inspiration behind the app is rooted in the idea that accidents and separation are unpredictable, and people should be able to express their feelings or intentions in advance.

Evidence

  • The tagline and write-up describe the product as a safe space for private expression.
  • It is framed as a way to value the present and the people around us.
  • The app is not meant to create fear but to remind users of the importance of relationships.

Inference The positioning is emotionally driven, aiming at individuals who may be concerned about mortality or legacy planning. It does not appear to target a commercial market beyond personal use.

Back to contents

Target Customer & ICP

The description does not specify a clear customer segment or ideal customer profile (ICP). The app is described as being for people who want to express themselves in advance, but no demographic, behavioral, or psychographic details are provided.

Evidence

  • The app is described as useful for people who may not have had the chance to say things.
  • It is framed as a tool for emotional comfort and legacy planning.

Inference The target audience likely includes individuals concerned with mortality, personal legacy, or those in emotionally vulnerable situations. However, no explicit ICP is stated.

Back to contents

Business Model & Pricing Evidence

There is no evidence of a business model or pricing structure in the description. The app uses Apple StoreKit for subscriptions, but no details are given about subscription tiers, pricing, or monetization strategy.

Evidence

  • Subscriptions are handled via Apple StoreKit.
  • No mention of revenue streams, pricing plans, or paid features.

Inference The app may be subscription-based, but the business model is not defined beyond the use of Apple’s payment system.

Back to contents

Technical & Delivery Signals

The app is built for iOS using Swift and SwiftUI. It uses PocketBase as a backend, supports account synchronization, notifications, and end-to-end encryption. The app also integrates with Apple Push Notification service and SQLite for local data storage.

Evidence

  • Built with Swift, SwiftUI, and PocketBase.
  • Uses Apple Push Notification service.
  • End-to-end encryption is implemented.
  • Data is stored locally using SQLite.

Inference The technical stack suggests a modern iOS app with backend support and privacy features. However, no evidence of scalability or production deployment is provided.

Back to contents

Traction & Maturity Signals

There is no evidence of user traction, adoption, or product-market fit beyond the initial prototype. The project was submitted to a hackathon, indicating it is in an early stage of development.

Evidence

  • Submitted to the OpenAI 2026 hackathon.
  • No mention of users, customers, or revenue.
  • No data on usage, retention, or product maturity.

Inference The app is likely in a prototype or early-stage development phase. No evidence of real-world use or commercial viability exists.

Back to contents

Competitive Context

No competitive analysis is provided in the description. The project does not reference existing products or services in this space.

Evidence

  • No mention of competitors.
  • No indication of market positioning relative to other tools for legacy planning or emotional expression.

Inference It is unclear whether similar products exist, and how this app would differentiate itself if it were to enter a broader market.

Back to contents

Key Risks & Red Flags

Key risks include:

  • Lack of user traction or commercial viability.
  • Emotional product positioning may limit mainstream appeal.
  • No evidence of monetization strategy or business model.
  • Prototype-level development with no production deployment.

Evidence

  • Submitted to a hackathon.
  • No revenue, customers, or adoption data.
  • No mention of monetization or scalability.

Inference The app is not yet proven in the market and may face challenges in scaling or gaining user trust due to its emotionally sensitive nature.

Back to contents

Diligence Questions To Ask The Founders

  1. What is the intended user base, and how are you planning to reach them?
  2. How do you plan to monetize this product beyond subscriptions?
  3. Have you conducted any user research or testing with potential users?
  4. What are your plans for expanding beyond iOS or adding new features?
  5. How do you intend to handle the emotional sensitivity of the content users will store?

Back to contents

Investment/Partnership Verdict

Not evidenced.

The project is described as a hackathon submission with no evidence of revenue, customers, traction, or commercial viability. The description does not indicate any business model beyond Apple StoreKit subscriptions, and there is no data to support product-market fit or scalability.

Confidence Low. This is a self-reported prototype with no external validation or evidence of real-world use.

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.