> I don't know how to know that it is "good enough" Stealing some ideas from an old post of Joel Spolsky (see number 12) https://www.joelonsoftware.com/2000/08

> I don't know how to know that it is "good enough" Stealing some ideas from an old post of Joel Spolsky (see number 12) https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/ https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-s... and copying a recent comment by myself: My recommendations are: 1) Don't test it at the office. Go to a nearby coffee store with a crappy wifi and test the site there to ensure it's not too heavy. 2) Grab a friend as a tester. Don't explain the site. Just sit your friend and ask him/her to use the site. You must sit like 3 foots behind your friend so you avoid helping her/him. Cross your hands on your back so you avoid helping. Look how the site is used, thanks your friend and go to fix the problems. Repeat with another friend. (Ideally a friend that is interested in the product, but any friend is a good substitution.)