4 signals from X — Jun 3–4, 2026 (below threshold, 7th consecutive)
0 of 4 X demand signals cleared the ≥10 combined engagement threshold — the 7th consecutive below-threshold run (35 signals total, 0 qualifying). The window's only above-threshold post (20 engagement — "Shazam for smells" by @maddydoggo) is unbuildable hardware. One actionable below-threshold signal: a multi-channel sports chat broadcaster from @AlexMyers3 (Golf Digest, 15,698 followers), buildability 4/5, PARTIALLY_SOLVED gap. Two disqualified: Things app API/CLI request (feature request) and Perplexity social-exclusion filter (feature request). 100% validation coverage this window.
Coverage window: June 3, 2026 13:29 UTC → June 4, 2026 18:00 UTC (28.5 hours). 4 signals found. 0 cleared the ≥10 combined engagement threshold. 1 signal — a "Shazam for smells" concept — crossed the threshold at 20 engagement but is unbuildable in its stated form. 1 actionable at below-threshold tier. 2 disqualified.
This is the 7th consecutive below-threshold run (35 total signals across 7 windows, 0 above threshold and buildable). Active queries: "I wish there was an app" and "wish there was a tool." 100% validation coverage this window — all 4 signals received poster verification, reply checking, and competitive landscape searches.
Nearest miss: high engagement, not buildable
Shazam for smells → custom candle
The window's highest-engagement post came from @maddydoggo, a musician with 519 followers: 20 total interactions (15 likes, 5 replies) on a request for an app that identifies a real-world smell the way Shazam identifies music, then produces a candle replicating that exact scent. 1
콘텐츠 카드를 불러오는 중…
The 5 replies were all jokes or expressions of delight — "@SincereSinsHere: Someone give this girl 1 million dollars in funding," "@Scrubz01: Smellzam produce French linen smelling candle for me" — not reports of an existing solution. 1
Why it doesn't qualify: the ask requires two unsolved hardware problems. Consumer-grade digital olfaction (capture + identification of a real-world scent) remains in research and lab settings — electronic nose sensors exist in industrial contexts but no consumer device can sample an arbitrary scent and return a replicable formula. Scent reproduction from sensor readings to candle formulation adds a second unsolved layer. This is a hardware science problem, not an app opportunity. Buildability: 1/5.
Existing products: ScentMax.ai offers AI-based fragrance recommendations from stated preferences (not scent capture). Ininum, demoed at CES, switches between pre-loaded scents — not capture-and-replicate. No consumer product solves the capture side.
Actionable signal (1)
Multi-channel sports chat broadcaster
Tier: BELOW THRESHOLD — 2 total engagement; genuine consumer confirmed; competitive gap partially validated; technically feasible on existing APIs.
콘텐츠 카드를 불러오는 중…
- Poster: @AlexMyers3, 15,698 followers, senior writer at Golf Digest (independently verified). Unverified blue badge. 2
- Engagement: 2 likes · 0 retweets · 0 replies · (views not reported)
- Posted: June 3, 2026 23:35 UTC
The ask: "I wish there was an app that I could type messages that send to all my various Knicks text/email/slack chains instead of having to send to each one. These games are a freaking grind." 2
A single compose window that broadcasts to multiple independent group chats across SMS, email, and Slack simultaneously — no copy-pasting between platforms.
What already exists — and what's missing: Kannect (kannect.co) handles multi-channel group messaging but targets enterprise organizational use, not consumer group chats. Zapier and IFTTT can bridge platforms but require setting up multi-step workflows per destination — there is no "compose once, send everywhere" consumer product. WhatsApp Broadcast is single-platform only. No dedicated consumer app for cross-platform group chat broadcast was found.
Category: PARTIALLY_SOLVED — building blocks exist (Slack API, email SMTP, SMS gateways), but the consumer-facing product does not.
Tech feasibility: Slack API, email SMTP, and SMS gateway APIs (Twilio, Vonage) are all accessible. The engineering challenge is authentication — an app needs the user to authorize their Slack workspace, email account, and phone-number-based SMS identity separately, and consumer OAuth scopes for SMS group chats are complicated (iMessage has no API; Android SMS access works via RCS or direct device integration). An MVP scoped to Slack + email broadcast sidesteps the SMS problem entirely and is buildable without platform-restricted APIs.
Competitive position: The poster's use case (game commentary to multiple fan groups) is a niche but probably recurring scenario for sports fans who maintain parallel community groups on different platforms. No cold-start advantage is obvious — the app requires the user to have accounts on all target platforms, making day-one utility low for new users. Buildability: 4/5. The primary constraint is UX for multi-platform identity management, not technical APIs.
Credibility note: @AlexMyers3 has 15,698 followers and a verifiable byline history at Golf Digest. The engagement is 2 likes, but the poster has a strong track record in sports media — The engagement number (2) and the poster's reach (15,698 followers, verified Golf Digest byline) point in different directions — low raw signal, high-credibility source. Disclose that asymmetry when evaluating.
Not actionable (2)
The two signals below were reviewed and disqualified.
Things app (by Cultured Code) — official API/CLI request
콘텐츠 카드를 불러오는 중…
- Poster: @JBagley (Jason Bagley), 2,800 followers, founder of Growth Experts (self-reported; unverified via independent search). Builder-adjacent. 3
- Engagement: 0 total
- Posted: June 3, 2026 18:26 UTC
The ask: "I love Things from @culturedcode. Everything about it brings me joy. But man I wish there was an API/CLI or just some app updates." 3 The stated use case: integrate Things with Cursor IDE, add tasks while coding, read task lists from the terminal.
Reason for disqualification: this is a feature request aimed at Cultured Code, not an independent product opportunity. The community has already shipped unofficial workarounds — a Go SDK for the Things 3 Cloud API exists on GitHub, and
things-mcpb (mbmccormick/things-mcpb) is a Claude Desktop Extension that bridges Things 3 via the MCP protocol. The primary constraint is Cultured Code's willingness to support an official API; building on top of the unofficial SDK carries breakage risk at any Things update. Poster is builder-adjacent. Buildability: 3/5, but dependent on a third-party vendor decision.Perplexity — exclude Reddit/social from research results
- Poster: @KenLaCorte, 68,988 followers, former Fox News executive and journalist (independently verified). 4
- Engagement: 0 total
- Posted: June 3, 2026 19:27 UTC
The ask: "I frequently am deep in a serious thread before I notice that some of its results have come from Reddit or some similarly stupid social media post. I really wish there was a way to exclude 'random online comment' from them. It's messed me up numerous times." 4 Use context: YouTube channel production research requiring verifiable sources.
Reason for disqualification: Perplexity currently provides source-type filters (Academic, Video, Social) that surface social media results but offer no inverse exclusion toggle. A Reddit r/perplexity_ai feature request from 2025 raised the same issue — Perplexity's social filter was noted as "stuck on Reddit only." This is a feature request for an existing product, not a standalone app gap. As a standalone product, it would require building a full Perplexity competitor with better source filtering. A browser extension filtering Perplexity results by domain is technically feasible but niche. Buildability: 2/5 as a standalone product.
Credibility note: @KenLaCorte has 68,988 followers and a verifiable media background. Zero engagement on a 28.5-hour-old post from a 69K-follower account is low but not rare for non-viral posts. The pain point is real; the opportunity is not independent.
Summary table — all 4 signals
| # | Signal | Poster (followers) | Engagement | Threshold | Gap status | Buildability |
|---|---|---|---|---|---|---|
| 1 | Shazam for smells → candle | @maddydoggo (519, unverified) | 20 | ABOVE — but unbuildable hardware | UNBUILDABLE — no consumer digital olfaction exists | 1/5 |
| 2 | Multi-channel sports chat broadcaster | @AlexMyers3 (15,698, unverified) | 2 | BELOW | Partial — no consumer cross-platform broadcast product found | 4/5 |
| 3 | Things app official API/CLI | @JBagley (2,800, unverified) | 0 | BELOW | Partial — community SDKs exist; requires Cultured Code action | 3/5 |
| 4 | Perplexity: exclude social/Reddit sources | @KenLaCorte (68,988, unverified) | 0 | BELOW | Feature request — not an independent product gap | 2/5 |
Total engagement = likes + retweets + replies; views excluded. 0 of 4 signals met the ≥10 threshold with a buildable opportunity. Coverage: June 3, 2026 13:29 UTC → June 4, 2026 18:00 UTC (28.5h window). 7th consecutive below-threshold run; 35 total signals across 7 windows, 0 qualifying.
Streak context: 7 consecutive runs, 35 signals, 0 above-threshold and buildable. The only post to exceed 10 engagement this window requires a hardware science breakthrough. The structural pattern — genuine consumer demand posts drawing low engagement in the first 24–48 hours — has held across all 7 windows. The research team has flagged the threshold calibration as needing review; options include reducing the engagement floor, switching to a multi-signal clustering model, or treating low-engagement posts from high-credibility posters as qualifying on a credibility-adjusted basis.
Cover: AI-generated illustration
이 콘텐츠를 둘러싼 관점이나 맥락을 계속 보강해 보세요.