6 ms·

Andrew, First off, it was very cool to chat the other night at the night owls. Very much appreciated your thoughts on connecting to different APIs. I do agree

Andrew, First off, it was very cool to chat the other night at the night owls. Very much appreciated your thoughts on connecting to different APIs. I do agree with the other reviewers that the purpose and uses for this product need to become more obvious. I would suggest including some brief illustrative use cases on the front page for people to start salivating over what cool things they can now do that they couldn't before. Having to read the FAQ via "What's Quirk" should not be the primary way visitors learn about your product. Also, for the dramatic effect of getting your Quirk, why not actually generate it right on the front page with a subtext of "make this Quirk do...." with options for people to chose from? I think that would also help communicate the use of the product better. Also, why can't I just paste a link (any link to anywhere) that I want my quirk to go to? You could make it a pass-through your site and probably find business models for that as well (I am making the assumption that the Quirk embeds the link back to your site specifically but could go anywhere). "Link your social network accounts" makes me believe I will get a Quirk that takes people to my actual Facebook profile rather than a Quirk profile. Smaller Things: Once logged in, when I click you logo, it doesn't take me back to your front page as I would typically expect. When I chose to log in via Facebook and then subsequently denied your oauth request, i just get an error page on your site.

andrewacove 16y ago
Thanks for the comments, cool meeting you too. It's definitely apparent that pointing users at the FAQ was a lazy and ineffective move. I'm working on making the front page a much better introduction to Quirk. We're not generating Quirks pre-signup (e.g., on the front page as you've suggested) because we think it's better for the encoded URLs to have each user's vanity URL, rather than a random key. This'd be a cool thing to add via Facebook's Instant Personalization, though. I agree that a good utility for encoding URLs in QR codes is a viable product. Sites and libraries exist for doing so, though none have any real mindshare. If the QR code flood is coming, a bit.ly for QRs is probably going to be a very useful tool. That said, it's not the product I want to build right now. Thanks for pointing out that error. I'll fix that ASAP; the home page too (right now logged in users are automatically redirected to their account views from the home page).

andrewacove 16y ago

Thanks for the comments, cool meeting you too. It's definitely apparent that pointing users at the FAQ was a lazy and ineffective move. I'm working on making the front page a much better introduction to Quirk. We're not generating Quirks pre-signup (e.g., on the front page as you've suggested) because we think it's better for the encoded URLs to have each user's vanity URL, rather than a random key. This'd be a cool thing to add via Facebook's Instant Personalization, though. I agree that a good utility for encoding URLs in QR codes is a viable product. Sites and libraries exist for doing so, though none have any real mindshare. If the QR code flood is coming, a bit.ly for QRs is probably going to be a very useful tool. That said, it's not the product I want to build right now. Thanks for pointing out that error. I'll fix that ASAP; the home page too (right now logged in users are automatically redirected to their account views from the home page).