2 ms·
I can kind of see the point. Website users are infamous for hating change. So it can be easier to make big changes / redesign, and then fix little things, rat
by smackfu 17y ago
I can kind of see the point. Website users are infamous for hating change. So it can be easier to make big changes / redesign, and then fix little things, rather than to make small changes that are constantly getting pushback.
- _delirium 17y agoHmm, I can see that reasoning, but I think it might overall be worse. If you change a ton of things all at once, you do get the user gripes over with all at once, but you also have less continuity than if you introduce a few changes here and there. I'm not sure that a website wants to give users the retro feeling they experience when they were used to Windows XP, installed Vista, and now feel like everything's weird and different. Admittedly that's wishy-washy, and I'm not against bundling up some amount of changes into groups to roll out, especially since presumably some kinds of changes depend on each other anyway. It just seems wrong if it's becoming a huge thing equivalent to traditional product-release cycles.
- ssclafani 17y agoYou can release a new version all at once and avoid user gripes by launching the new version on a subdomain so users can get used to it. Digg did this with their last version and probably will with V4. Facebook and Zappos did as well.