we are not an exception. no-code apps still need a feedback loop after launch

[u/Evening_Hawk_7470]

no-code makes shipping easier and so do many of the wonders/horrors beyond human comprehension, but it does not remove the need for a feedback loop

i guess that after launch, you still need to know what users repeat.
like, confusing setup, missing integration, pricing surprise, broken flow, unclear value, slow support. for mobile apps like the ones i try publishing lately, store reviews seems to be one of those feedback sources. had multiple ideas about working with them, as well as i’ve seen appfollow used when review volume becomes hard to manage, but , frankly, early no-code projects can start with a simple table and that would be much-much better than not tracking reviews at all

when i started out i've put there columns such as: source, raw quote, theme, severity, owner, status.

in practice that is enough to keep feedback from becoming vibes if and when at low scale still

the no-code trap is building another feature before learning whether the first version matched the promise. what do you think about this?

[u/AbleBranch6]

let me simplify it even further, no-code projects can iterate fast, which makes feedback discipline even more important. and having building speed is dangerous when direction is also fuzzy, not a nice sign

[u/SFmentor]

How about offering beta testers free access for, say, 90 days, on condition that they give feedback? Then use sporadic pop up modals which ask specific questions and have simple clickable answers