Show HN: WWYD – "What Would You Do?" A Daily Scenario App
I built WWYD - What Would You Do, a community-driven app where users respond to daily hypothetical and real-world scenarios, then see how their choices compare to others. Each scenario presents four possible options, and after selecting one, users can leave a short (140-character) comment explaining their reasoning. Once submitted, users can see community-wide voting percentages and read anonymized comment threads grouped by choice.

Why I Built This: There aren't many places like HN that focus on cultivating a community-driven exchange of ideas rather than the usual social media noise. WWYD strips away the distractions (e.g., no following, replying, or user search), offers a space to see what people think, and, if they decide to share, why they think that way. The scenarios serve as daily prompts to guide discussions and offer a way for users to compare their perspectives with others. While comments are limited to 140 characters, the hope is that these brief insights will spark deeper real-life conversations, using WWYD as a thought-provoking starting point.

How It Works

• One new scenario daily – Keeps things fresh and avoids overwhelming moderation.

• Limited response window – Scenarios lock after a certain period to prevent stale debates.

• Anonymity-focused – No public profiles, no identifying user info, and no replies to individual users.

• Spam-resistant – Requires sign-up (I know, friction, but necessary). No excessive data collection.

• Uniqueness Score – Tracks how often your choices align with (or deviate from) the crowd.

Current Limitations

• US-only for now – Managing moderation and keeping backend resource usage low (free-tier constraints!).

• Database constraints – Built-in safeguards notify users if daily request limits (e.g., reads/writes/deletes/sign-ups) are close to hitting.

Incorporated “Vibe Coding” (with Claude Code): This is my third app and by far my most ambitious. For reference, both my previous apps were written in Dart (Flutter), whereas this is pure Swift. I started this app from scratch on Xcode last Sunday, and it took a fraction of the time my previous (simpler) apps required. Here are some of my learnings from this “vibe coding” experience:

• Great for writing clean, structured code when given precise instructions.

• Lacks strong system design intuition, and makes heavy unspoken assumptions. For instance, it initially assumed I had configured the backend in a particular way (which I hadn't), it assumed certain structures just magically existed (which they didn't), and it did require a fair bit of debugging to pinpoint those assumptions. But after a while, you do get better at debugging with it and just like irl when the nature of the bugs are similar to those you've encountered, the marginal effort to debug reduces substantially.

• Best suited for narrow, well-scoped tasks, but not quite ready for architecting large, complex systems.

I’d appreciate your thoughts (btw, you can provide feedback inside the app), especially on:

• Improving the onboarding/sign-up experience while keeping spam control (keeping in mind, this is not a funded venture or anything).

• Potential feature additions (e.g., more granular voting insights?).

Check it out (US-only for now) and let me know what you think. Thanks for reading!