3 ms·
Yup, that is it, it makes it seem easier. Furthermore, it exploits the sunken cost fallacy ('Oh I have already filled so much can't give up now'). Seems a bit
by ovi256 17y ago
Yup, that is it, it makes it seem easier. Furthermore, it exploits the sunken cost fallacy ('Oh I have already filled so much can't give up now').
Seems a bit sleazy to me. But I would really like to see some A/B testing between this and a classic form, to know if it really has an influence.
- warfangle 17y agoCompare this with a form that simply requires email address and password to sign up, and .. well, you're going to get a lot better result, in terms of conversion rate, on the latter. The less, and less intrusive, you ask on signup - the better your conversion rate will be.
- hailpixel 17y agoSunken cost is an interesting argument (though "fallacy" is an apt description), but I believe it does not address the design mistake made here. Given the composition of the first UI object (user / pass / submit / register) an user would click "register" thinking that the process is complete, only to gaze in horror as more fields are revealed. If those fields are required from the start (which they really shouldn't be) they should be visible. The 'verbage' is all wrong.