ErsatzGuide

The company appears to be a solo developer project named ErsatzGuide, an Android TV guide application that integrates with ErsatzTV feeds. The author describes it as a "private, local-first" tool designed for users who self-host media servers but want a native-like experience when browsing schedules from their phone.

The product combines M3U playlists and XMLTV schedules into a searchable, offline-capable Android app with reminder functionality. It is built using Kotlin and Jetpack Compose, and emphasizes resilience against data inconsistencies in feed formats.

Key commercial due-diligence read: The description does not contain any evidence of revenue, customers or adoption — only self-reported claims about product features and architecture. There is no indication that this project has moved beyond the prototype or hackathon stage.

Most important open question: Is there any evidence of user testing, feedback loops, or actual usage beyond the author’s own development?

The description states that ErsatzGuide:

• Combines an ErsatzTV M3U playlist and XMLTV schedule into a local Android guide.
• Provides a timeline, Now & Next, channel schedules, offline search, programme details, and reminders.
• Imports are transactional so failed network refreshes do not erase usable data.
• Has no accounts, ads, analytics, or cloud backend.
• Is written in Kotlin with Jetpack Compose and Material 3.

Inference: The app appears to be a lightweight, privacy-focused Android application aimed at users who self-host media content but desire a more intuitive interface for browsing and managing their guide.

The author positions ErsatzGuide as:

• A "private, local-first" solution.
• An alternative to traditional TV guides that preserves control and privacy of self-hosted setups.
• Designed for users who find existing home media server interfaces clunky or non-native.

Claim: The app makes browsing schedules from a phone feel like a native TV guide while maintaining the benefits of self-hosting.

Inference: This is a niche product targeting early adopters or power users within the self-hosted media ecosystem. It does not appear to be positioned for mass-market appeal or commercial scalability.

The description implies:

• Users who operate home media servers (e.g., using ErsatzTV).
• Individuals seeking a better interface for browsing and managing their TV schedules.
• People who value privacy and local-first solutions over cloud-based alternatives.

Not evidenced: No specific customer segments, personas, or market size are mentioned. The ICP is inferred from the product’s architecture and stated use case.

The description states:

• There are no accounts, ads, analytics, or cloud backend.
• No pricing model is described.
• The app is open-source or at least publicly available via Devpost.

Inference: If the project remains free and non-commercial, it likely does not have a monetization strategy beyond potential donations or future optional features.

The author reports:

• Built with Kotlin, Jetpack Compose, Material 3.
• Uses Hilt for dependency injection, Room for data storage, DataStore for settings, OkHttp for streaming, WorkManager for refreshes, AlarmManager for reminders.
• Defensive parsing of XMLTV data including handling malformed records and time offsets.
• Transactional imports to prevent loss of usable data during failed refreshes.
• Unit and instrumentation tests covering various aspects of functionality.

Inference: The technical stack suggests a well-structured, modern Android app with attention to robustness and testability. However, this is a solo-developer project; no team or infrastructure beyond one person is evident.

The description states:

• Submitted to the OpenAI 2026 hackathon.
• No mention of downloads, users, or engagement metrics.
• No evidence of revenue, customer acquisition, or retention.

Not evidenced: There is no indication of traction, adoption, or user feedback beyond the author’s own account. The project appears to be in an early-stage prototype or proof-of-concept phase.

The description does not reference competitors directly. However:

• ErsatzTV is mentioned as a source for feeds.
• Other similar tools may exist in the self-hosted media space, but none are named.

Inference: The competitive landscape likely includes other local-first or self-hosted media server interfaces, though no direct comparison or differentiation is made.

Key risks identified from the description:

• Solo developer project with no team or external support.
• No evidence of real-world usage, feedback, or iteration beyond a hackathon submission.
• Product may not have evolved past initial concept or prototype stage.
• Lack of monetization strategy or clear path to commercial viability.

Inference: The risk of the project remaining a one-off hack is high. Without traction or user validation, it is unclear whether this will develop into a viable product or service.

1. What was the actual outcome of the hackathon submission? Was there any follow-up or community interest?
2. Have you tested the app with real users beyond yourself?
3. Are there plans to expand beyond the current feature set, and how would that affect the architecture?
4. Is there any intention to monetize the product, and if so, what form might that take?
5. How do you plan to handle ongoing maintenance and updates given only one developer?