SnapCal

SnapCal is an Android app that automates calendar event creation from screenshots using local OCR and a deterministic ambiguity rejection system. The author states it was built for personal use to solve the problem of forgetting to add events seen in screenshots, particularly from LINE or social media. It runs entirely on-device with no network permissions, and uses Japanese OCR via ML Kit. The app is described as privacy-focused, rejecting ambiguous inputs rather than guessing.

The most important open question is: What is the actual adoption rate or usage volume of this tool, if any? The description provides no evidence of customers, revenue, or product-market fit beyond the author's own use case and a single-person development effort.

This analysis is based entirely on self-reported information from the project description. No third-party verification or historical data exists for this project.

The description states that SnapCal is an Android app with two entry points:

• Sharing a single screenshot from Gallery, LINE, or another app.
• Starting screenshot monitoring with a persistent edge bubble visible on screen.

It uses Japanese OCR via ML Kit, runs entirely on-device, and integrates with Android's standard Calendar Provider. It stores only small operational identifiers for duplicate prevention and Undo functionality.

The app is built in Kotlin with Jetpack Compose, using libraries such as Room, WorkManager, and MediaStore observation. The author used Codex and GPT-5.6 to assist development, including architecture design, end-to-end flow implementation, ambiguity rule design, adversarial testing, and privacy review.

The app is described as having a “deterministic ambiguity rejection” system, where it does nothing when input is unclear (e.g., multiple events, past dates, missing fields). It adds only one event per screenshot if the OCR output is unambiguous.

Not evidenced: No evidence of actual users, usage metrics, or product-market fit beyond the author’s personal use case.

The author states that SnapCal was built to solve a personal problem: forgetting to add events seen in screenshots. The app’s positioning is framed around automation, privacy, and safety—specifically, it avoids guessing or over-automating by rejecting unclear inputs.

It is described as a “privacy-by-construction” tool, with no network permissions, and no data leaving the device. It also claims to be safe in that it does not persist sensitive information like full OCR text or images.

The evolution of the product’s claim appears to have shifted from a simple “OCR + calendar” idea to a more nuanced approach: rejecting uncertainty as a feature, rather than an error.

Not evidenced: No evidence of how this positioning has evolved over time, nor whether it was tested with others. No marketing or branding claims beyond the author’s own description.

The author states that SnapCal is for people who take screenshots of events in LINE, social media, or ticket pages, and then forget to add them to their calendar.

It is described as targeting users who are frustrated by manual calendar entry and want a “one-click” solution. The app is built specifically for Android users, with support for Japanese OCR.

The ICP (Ideal Customer Profile) appears to be:

• Android users
• Regularly screenshotting event details
• Interested in privacy and automation
• Likely to be self-employed or tech-savvy individuals

Not evidenced: No evidence of actual customer segments, personas, or feedback from users beyond the author’s own experience.

The description states that SnapCal is free to use, with no pricing model or monetization strategy described. It is built as a personal tool and not presented as a commercial product.

There are no mentions of subscriptions, in-app purchases, or paid features. The app is open-source (GitHub repository included), and the author provides setup and testing instructions.

Not evidenced: No evidence of revenue streams, pricing tiers, or monetization plans.

The app is built with Kotlin, Jetpack Compose, and uses ML Kit for Japanese OCR, Room for local data storage, WorkManager for background tasks, and MediaStore observation. It also uses a foreground service to maintain the edge bubble.

It was developed using Codex and GPT-5.6, which helped in architecture, flow implementation, ambiguity rule design, adversarial testing, and privacy review.

The app is described as having a release gate that enforces no network dependencies, runs unit tests, and inspects APK permissions. It was built to be privacy-first, with no data persisted beyond operational identifiers.

Not evidenced: No evidence of scalability, performance metrics, or production deployment details beyond the author’s own development setup.

The project is described as a single-person effort by Hiroyasu Tazawa. It was submitted to the OpenAI 2026 hackathon, and includes a public GitHub repository with setup instructions, signed APKs, and evaluator bundles.

There is no evidence of:

• User adoption or usage metrics
• Customer feedback or testimonials
• Product iterations beyond this version
• Revenue or monetization

The app is described as “safe” and “private”, but there is no evidence of market traction or product-market fit.

Not evidenced: No evidence of users, customers, or adoption beyond the author’s own use case.

The description does not mention any direct competitors. It is implied that SnapCal fills a gap in automation for calendar entry from screenshots, particularly with a privacy-first approach.

It is not clear whether similar tools exist in the market, nor how it would compare to existing Android apps or services that offer OCR + calendar integration.

Not evidenced: No evidence of competitive landscape, existing solutions, or differentiation strategy.

• Single-person development: The app was built by one developer and lacks a team or business structure.
• No traction or adoption: There is no evidence of users, customers, or product-market fit.
• Limited scope: It only supports Japanese OCR and Android, with no indication of expansion plans.
• Privacy as a feature vs. market demand: While privacy is emphasized, it’s unclear if this is a strong enough value proposition for widespread adoption.
• No monetization strategy: The app is free and open-source, with no clear path to revenue.

Not evidenced: No evidence of risks being mitigated or addressed in any way beyond the author’s own development choices.

1. What is your actual usage frequency of SnapCal? Is it a tool you use daily?
2. Have you received feedback from others who tried the app?
3. What are your plans for expanding beyond Japanese OCR or Android?
4. How do you plan to monetize or grow this product if at all?
5. Are there any technical limitations or scalability concerns with the current architecture?
6. Do you have a roadmap for future features or improvements?