Call for Action: More Frequent Alpha Testing

RemNote
#1

This post attempts to suggest one way to solve the tension between meeting users’ expectations of transparent communication (i.e., disclosure, timeline, etc) and publishing a relatively polished update.

The RemNote team should utilize and rely more on alpha testing, enlisting life-learners to help with bug detection and function polishing. That way, the testing process might be pushed forward, and, equally important if not more, other users would know what is going on and have an idea of what will happen eventually.

It might be my personal opinion, however, being kept in dark is one element detrimental to fostering a viable community. People would be more patient if they could have some references for what is likely to happen.

The lack of alpha testing (or short transition from alpha to beta and to the main server) might be a waste of opportunity that could have been used to stir a healthy amount of conversations within the RemNote community.

8 Likes
#2

i completely agree. hopefully someone from the team sees this. the more testing remnote gets, the more polished it becomes

2 Likes
#3

Yep! And with more frequent Alpha and Beta testing, the release of standard update is likely to be more polished, rather than facing a huge backlash from the community.

1 Like
#4

With the iOS beta app releasing there could be an impetus to keep a beta app indefinitely for the testing of new released before pushing it to the non-beta iOS app version. This is conjecture on my part

1 Like