- 3 min read
We had some hot debates about our beta program. We were seriously considering limiting access to the program and discussed various ways of implementing it, but the final show of hands pointed towards making the program public. The driving force behind this decision was the argument that Wrike's power is in its collaborative abilities.
The web 2.0 world is use to public betas. A company builds a product, makes it live, starts promoting it and polishes things on the way (on the way to where). Its a good approach, but sometimes it might be painful for users. You can allow this to happen if you have a strong
The web 2.0 world is use to public betas. A company builds a product, makes it live, starts promoting it and polishes things on the way (on the way to where). Its a good approach, but sometimes it might be painful for users. You can allow this to happen if you have a strong