Snappy

What the company appears to be: Snappy is a menu bar app for macOS that uses audio fingerprinting to recognize single or double finger snaps as input to trigger actions such as opening apps, websites, or deleting browser tabs.

What changed: The project evolved from a personal hackathon idea (submitted to OpenAI 2026 hackathon) into a potential consumer product with a one-time purchase model. It was built using Swift and leveraged AI tools like Codex for development.

The single most important open question: Is there sufficient commercial traction or user demand to justify further investment or partnership, given that the project is self-reported, has no revenue data, and lacks evidence of customer adoption?

• The description states Snappy is a menu bar app for macOS.
• It uses the macbook’s microphone to detect finger snaps.
• It employs audio fingerprinting to match detected snaps against stored recordings.
• It supports single or double snap gestures to trigger actions like:
  • Opening apps
  • Opening websites
  • Managing browser tabs (e.g., deleting all open tabs)
• The app is built using Swift, and the author used AI tools such as Codex for development.

Note: No evidence of actual product functionality beyond self-reported claims, no screenshots, no demo video, or user feedback data.

• The author describes Snappy as a personal solution to ADHD-related fidgeting, and an experiment in using the MacBook’s chassis as an input source.
• It is positioned as a novel interaction method for macOS users — replacing traditional keyboard or mouse inputs with audio gestures.
• The app was initially built during a hackathon, but has evolved into a potential consumer product.
• The author states they are planning to launch it as a paid one-time purchase with a lifetime license model.

Inference: The positioning appears to be niche and experimental, targeting users who value novel interaction methods or have specific accessibility needs. No evidence of broader market positioning or branding strategy.

• The author identifies themselves as a person with ADHD and a naturally fidgety individual.
• The app is designed for macOS users, particularly those looking for alternative input methods.
• There is no evidence of:
  • Specific personas
  • Market segmentation
  • Target demographics beyond the founder’s personal experience

Note: No evidence of customer research, target segments, or user interviews. The ICP is inferred from the author's own description.

• The author states they plan to sell Snappy as a one-time fee for a lifetime license.
• There is no mention of:
  • Pricing tiers
  • Freemium models
  • Subscription plans
  • Revenue projections or monetization strategy beyond the single purchase model

Note: This is a self-reported business model, not validated by any market data or sales.

• Built using Swift.
• Uses audio fingerprinting to detect finger snaps.
• Leverages AI tools like Codex for development.
• The app supports both single and double snap gestures.
• The author mentions false positives were a challenge, and that they used machine learning techniques (e.g., Apple ML) to filter out:
  • Keyboard typing
  • Trackpad clicking
  • Speaker noise
  • External interference

Inference: The technical approach is experimental and likely not production-ready. No evidence of scalability or robustness in real-world usage.

• The project was submitted to the OpenAI 2026 hackathon.
• The author mentions:
  • Early demos shared online
  • Feedback from friends and potential users
  • A comment from a user requesting single-snap support
• The app reportedly achieves 85–90% accuracy
• There is no evidence of:
  • Actual sales
  • User base or adoption metrics
  • Customer reviews or testimonials
  • Product in the App Store or other distribution channels

Note: Traction is entirely self-reported and lacks independent verification.

• The description mentions a similar project for Windows OS: [https://github.com/Yutarop/two_claps_open](https://github.com/Yutarop/two_claps_open)
• No evidence of:
  • Direct competitors in the macOS space
  • Market analysis or competitive positioning
  • Pricing or feature comparisons

Inference: The app is likely a niche product with limited competition, but no market data supports this.

• No revenue or sales data — the project is unproven in the marketplace.
• Single-person team — no evidence of scaling capability or support structure.
• Unverified claims: Accuracy rates, user feedback, and product functionality are self-reported.
• Experimental nature: The app is described as a hackathon project that has evolved into a consumer product without clear validation.
• No distribution strategy — no mention of App Store listing, marketing plan, or launch strategy.

Inference: The risk of failure is high due to lack of traction, no business model validation, and limited team capacity.

1. What is your actual user base (if any) and how are you measuring adoption?
2. How do you plan to validate the accuracy and usability of the app in real-world settings?
3. Have you tested the app with users outside of your immediate circle?
4. What is your go-to-market strategy for reaching consumers?
5. Are there any technical or legal risks (e.g., microphone permissions, privacy concerns) that could affect adoption?
6. How do you plan to scale beyond a single-person development team?