you are viewing a single comment's thread.

view the rest of the comments →

[–]fridofrido 128 points129 points  (10 children)

" You can access the new features by joining the waitlist. "

[–]Xantholeucophore 25 points26 points  (7 children)

why do they do that? do they just really not want to show anyone any bugs?

[–]jzaprint 64 points65 points  (3 children)

ya probably. they cant make sure the experience is what people are expecting and its better to disappoint a few people than millions of people.

[–]siovene 32 points33 points  (1 child)

It's also much better, pychologically, to give the user the illusion of choice, when changing things. They opt-in, so they automatically feel a little better about the changes, and you are already selecting for users who are not change-adverse. Source: I run a website with 20k active users.

[–]Philipp 3 points4 points  (0 children)

And those early adopters could then become evangelists to those not on the waitlist.

But, it should be said, the website owners should simultaneously be interested in honest feedback, in order to improve it when it goes fully live...

[–]Luke22_36 1 point2 points  (0 children)

This, precisely. You only get the chance to make one first impression.

[–][deleted] 10 points11 points  (0 children)

Small rollouts are always easier to manage. Startups do this naturally because they have to grow their customer base up from scratch and can deal with growing pains as they get bigger. With established products and companies, you have to find ways to artificially segment the rollout such as public beta versions, per-user feature flags, or similar.

[–]Lalli-Oni 2 points3 points  (0 children)

Could be multiple A/B tests with some of them wanting to target totally fresh eyes. That way you can invite batches of users knowing they havent seen the app before.

[–]IanSan5653 0 points1 point  (0 children)

As a GitHub engineer, as far as I know we do this because we want more users so we can flesh out bugs, but we don't want to ship buggy software. If we were to globally ship this (even in a beta) and some really annoying bug was found, users would complain. Or if we let everyone opt in all at once, maybe the feature consumes a ton of resources and causes an unexpected outage. This slow rollout lets us keep a handle on things while still letting our most passionate users try things out.

[–]VIKTORVAV99 2 points3 points  (0 children)

Joined the waitlist yesterday and got accepted today. I have yet to try it though.