What are people using to host their websites these days, I feel like @Webflow, @Wix, @Framer, etc have gotten so expensive that I'm questioning if those are still the best for basic sites?
I'm building a site where the focus is SEO, lead gen, and good UI/UX
Before I hand off a feature, I’m trying to ask:
could someone build this without needing a 30-minute explanation from me?
If the answer is no, it’s not a dev problem yet. It’s still a clarity problem.
Things I built or broke this month: PRD tool, habit tracker, fitness app logic, several flows I thought were simple, and my confidence in understanding errors quickly.
Good month, weirdly.
Having said that, the deep research tool seemed quite strong, and I can definitely see the value in the analytics and scenario planning side. That’s the part I’d be most intrigued to test further, especially to see how deep it can actually go when analysing data.
Joined an AWS workshop today to learn more about Amazon Quick and I’m still forming my thoughts on where it sits.
Some of the tools felt a bit behind, especially the PowerPoint and image generation. The deck didn’t really stick to one theme and the design changed across pages
Does anyone have recs for this?
I built a workout app for myself on iOS and only want to use it personally. Is there a way to keep it on my phone without having to publish it to the App Store?
Me and Claude have had about 5 conversations trying to fix two alignment issues on my app; timeline dots and chevrons.
I think the answer might just be to go in and fix the code myself. Has anyone with no coding background actually done this successfully?
Sometimes the AI output is bad because the tool is bad.
Sometimes the AI output is bad because my prompt is basically “please solve this vague thing I have not thought through yet.”
Unfortunately, it is often the second one.
PRDstudio should not feel like filling in a template.
It should feel like a slightly annoying product partner asking: have you actually defined the user, what are you assuming here, why is this in scope, and how will you know this worked?
Creators are not “hard to work with” just because they ask how their content will be used. That’s not difficult. That’s someone understanding the value of their work.
QA asks: does it work?
UAT asks: does it make sense?
Very different questions. I think product teams sometimes hide behind the first one because the second one is more uncomfortable.
There's a specific feeling when you've been building something for weeks and it works, nothing is broken, and then a user tells you politely that they'd just been doing it a different way anyway and suddenly all that time looks different.
Before I'd spend a chunk of the day writing acceptance criteria from scratch, catching edge cases halfway through a build, UAT planning eating time I didn't have. Now the first draft is done in minutes and I'm refining rather than starting from zero.
Most features stall in development have the same issue underneath: nobody agreed on what done actually looked like.
That's not a build problem. It's a definition problem. And it should have been solved before anyone opened a design file.
What usually kills your momentum?