Vibe coding Cues helped me experience how creating interactive prototypes have changed now with vibe coding and Al tools. And this experience has taught me the importance of prompting and being able to describe what I want. There were several times when I prompted Claude to implement a feature, but Claude misinterpreted what I wanted. I had to tell it to reverse the changes made and find different ways to communicate to Claude by giving it references and more context.

For Cues, we're always surrounded by too many choices, even for low-stakes decisions. And often times, it is these small things that occur the most frequent and annoying, despite being low-stakes. When faced with decision fatigue, we can default to our safe choice and end up not trying something new or missing out on new opportunities. I intended for Cues to help shift making these decisions from 'which is objectively best?' to 'which do I commit to?' If I rebuild this, l'd add weighted randomness (let users bias probabilities, like 'I feel more strongly about certain options in the list') and collaborative mode (friends vote on eliminations). Another feature I would like to enhance is how the elimination happens so that the app feels more playful and less stressful. For example, maybe implemenet these mini-games like roll a dice or pick a random card so that the eliminating options become more interactive and engaging.