2 weeks ago I posted on twitter asking if people wanted feedback on their MVP, and an idea on how makers could help each other with it:
It got some good responses so I set up a landing page to gather interested people together and further fine tune the idea:
https://feedbackswap.softr.app/
Benefits being:
Hi Marty,
You idea would be very useful to me if there is a way to control the nature of the swap. What I usually try for is a usage swap. Not a review swap which typically just includes pointers on the UI. So if Feedback Swap had a way for me to mark the level of commitment - say use for a week - then it would save me a lot of time.
thanks for the reply . I think then that your idea requires more of a match with a specific target audience, whereas my idea is more closely aligned with QA / or basic login and onboarding testing. certainly room for both kinds of apps, but I'll try and keep the scope confined at this stage.
That's the point - just what does your service offer? If I sign up then I'm just supposed to check my partner's on-boarding? If you don't setup any levels of expectations then people can get pretty miffed right away when there partner doesn't match their implicit ideas. Better to make everything explicit and then its just one app but people know what they are getting.
yep I think we agree that clarity is really important. I propose in the landing page that this will be made clearer by the use of fill in forms, which have certain requirements regarding the categories of questions, and minimum content length.
Probably worth adding support for different forms too, which the owner of a site then selects from a list of templates, in that way the site owner can constrain the reviewer to answering certain questions.
For most of us no - the form feedback is not the point. Most modern apps have some equivalent of LogRocket in them that allows you to monitor usage. So when someone hits bad UX or a bug we already know without them saying anything. We just need usage exchange where they actually use the product.
And its okay if they use the product and just pretend to be target market - that's fine. But usage - not opinions formed without using. So its the usage that has to be clarified. If they are just going to do onboarding then that won't be enough, I can get people to try that without a service helping me.