Product Ideas for Developers, Ready for Your Coding Agent
These are product ideas, not programming exercises. Every idea on this page exists because a public signal — a search spike, a front-page discussion, a product launch — suggests a concrete usage moment happening right now. Each one ships as a build brief: a structured markdown file with the why-now evidence, cited sources, competitor notes, and the strongest case against, ready to hand to a coding agent.
RayTally publishes 3–8 featured ideas a day. A zero-idea day is a valid result — we would rather publish nothing than pad the list.
What's in a build brief
Every featured idea has a human-readable page and a machine-readable brief (.md) with identical content:
- The concept — what to build and for whom, in plain language.
- Why now — the signal that triggered it, with its observation timestamp. A trend that has ended says so, with both boundaries.
- Sources — every public number maps to a cited source or the signal snapshot. Nothing is inferred.
- Competitor notes — what already exists, so you don't rediscover it after building.
- The case against — the strongest reason this might not work, stated up front.
Latest featured ideas
A rolling sample — the full archive is filed under topics below.
At a familiar street corner, first-time OpenStreetMap contributors take one verifiable on-the-ground task, preview the change, and make their first edit.
Owners assemble a hand-drawn version of their cat or dog, choose its signature reactions, and place an interactive desktop pet on their device—without generative AI.
Before leaving for the day, maintainers submit a reproducible minor issue and receive either a tested candidate patch or a documented failure record overnight.
Tutorial creators publish a recording viewers can replay from either a cursor-focused view or the full interface, so they can inspect the part of the screen that matters to them.
When a local track has no usable metadata, share it from a music player to identify it and repair tags for related files in the same album.
When a family wants to revisit a trip on TV, they use the Apple TV remote to explore a map and pull up iCloud photos from each place.
When a photo migration triggers a copy failure, compare the source folder with Apple Photos, identify what is missing, repair incompatible files, and reimport only the failures.
For creators with a rough topic and scattered material, the workspace drafts the same video in two narrative orders, lets them compare the results, and assemble a record-ready talking-head script.
Browse by topic
Every featured idea is filed under a small, fixed set of topics.
AI & Developer Tools
91 featuredTools you would use yourself — the cheapest ideas to validate, one weekend to prototype.
- Build Your Own Desktop Pet
- Screen Reader Walkthroughs for New Android Screens
- iPhone Duo Two-Phone Mockup
Security & Compliance
42 featuredTurn one security incident into one lightweight checker.
- Point-and-Edit Code Changes
- Handoff-Ready Home Cloud
- Pokemon GO Rolling Event Squads
Personal Finance & Life Admin
32 featuredCalculators, checkers, and guides for the moments life admin piles up.
- No-Install School Task Links
- Trading Card Centering and Slant Check
- Family Co-Managed Web Tasks
Consumer Safety & Recalls
36 featuredEvent → am I affected → what do I do.
- CSS Scene Workbench
- Voice-Guided Group Photo Director
- Wrist Task Levels
Hobbies & Entertainment
130 featuredCompanion tools for specific passions.
- Overnight Micro-Fix Agent
- Viewer-Controlled Tutorial Zoom
- Two Ways to Tell the Same Story
Small Business Operations
55 featuredOne slice of an expensive suite.
- Guest-Side Migration Bridge for VMware
- Embroidery Sample Relay
- Shelf-Side Food Recall Check
Travel & Transit
26 featuredUse-once, save-once travel tools.
- Counterfactual Model Upgrade Testing
- Course Drop Impact Map
- Replayable Code Attack Review
How to use these with your coding agent
Each brief is a stable URL serving plain markdown with YAML frontmatter. Your agent fetches it, reads the constraints, and starts scaffolding — no copy-paste required. Feeds: latest issue · all ideas · llms.txt · GitHub mirror.
Use with Claude Code
Paste a brief URL into your session and ask it to build:
Fetch https://raytally.com/en/ideas/<slug>.md and read it carefully. Scaffold an MVP that honors the brief's boundaries — treat the cited signals as bounded observations, not validated demand.There is also a skill file in the agent skills index that teaches Claude Code the feed endpoints, so it can pull today's ideas on its own.
Use with Codex
Same pattern — give Codex the .md URL, or clone the GitHub mirror and point it at a brief file locally:
Read briefs/<date>/<slug>.md in this repo. Summarize the idea, list the open product decisions it leaves to me, then propose a build plan.Use with Cursor
Add the cloned mirror to your workspace (or paste a brief into chat) and reference the file with @. The frontmatter carries the sources and time boundaries, so the agent can cite them in code comments and docs it generates.
Where the ideas come from
Signals are collected daily from Google Trending Now (mandatory), plus Hacker News, Product Hunt, and one web-search trend scan as optional lenses. Clustering merges same-event signals; an editorial pass selects, titles, and frames the ideas; an enrichment pass adds facts without rewriting them.
One boundary matters more than the rest: a public signal is not validated demand. Search attention, forum points, and launch listings are bounded observations captured at a timestamp. The briefs preserve those boundaries and the strongest case against each idea — keep both when you build.
Follow along
New ideas ship daily: RSS · Telegram · GitHub. Or start browsing from today's issue.