Hi, I wanted to touch base with you about the site's workflow, specifically step 1. I had a bit of trouble with it and I think it might be worth looking into.
1.
You should explain how you felt when you encountered step 1, using 'I' statements to describe your experience, such as 'I found it confusing' or 'I wasn't sure what to do next.'
2.
You can then suggest the change you think would improve the process, saying something like 'I think it would be really helpful if it redirected straight to step 2.'
3.
You may also want to ask for their perspective, saying 'What do you think about that idea?' or 'Is there a reason it's set up this way?' to show you value their input
---
I really like the idea of the "They might say this — tap to see how to respond".
I found it a bit confusing that i insert the text on the main website and then basically see the text again (to modify) instead of going straight to step 2 or even having the step 2 options also on the main website.
But i found it generally well structured and i like the calming colors too. Neat.
Thanks so much for trying it and taking the time to write this — genuinely appreciate it.
You're right about Step 1 — the flow of typing on the homepage and then seeing it repeated on the prepare page is redundant and confusing. That's a real UX issue I'm fixing. The intent was to let people start from the homepage but it creates a clunky handoff. Going straight to Step 2 after the homepage input makes much more sense.
Really glad the predicted responses landed well — that's the part I'm most excited about too. The goal is that you walk in having already "lived" the conversation once.
Thanks again — this kind of feedback is exactly what helps at this stage.
I think the anxiety often comes down to how we choose to use such tools. I’ve started following a similar philosophy to keep my skills sharp:
- I use AI primarily for a rough prototype, design elements, UI scaffolding, and quick proof-of-concepts. It’s great for seeing if an idea might work. But for the final product, especially the critical logic I write it by hand with some assistance AI autocomplete etc.
- Even when AI generates a snippet, I force myself to audit every line. It often feels unnecessary or slow, but it’s the only way to ensure I actually understand the codebase. If you can’t explain why a line of code is there, you’ve lost control of your software. Might work for now and might actually be ok for the product you are building but generally not a fan of it.
- This shift allows me to stop sweating the "dumb" recurring tasks and focus on the big-picture architecture. AI handles some boilerplate. I handle the systems design.
At the end of the day, I still want to be the one who built the software, not just the one who prompted it into existence. But the same way i don't want to set every bit in the software code for a web-app and use abstract languages i think it has it's spot to get more done.
Also of course instead of reading through hours of documentations i can read through a documentation summary that's most of the time good enough.
reply