Hello, everyone. Here you’ll find general updates on the rollout of test access to Anytwo. If you have signed up to be a tester, then please follow this thread.
This is not a thread for feedback on Anytwo, we will create a separate thread that the general community can follow. This is primarily for the logistics of testing Anytwo.
What to expect
Feedback:
We will collect user feedback, share changelogs, and shape the roadmap of Anytwo together on a separate platform—not this forum. We will use Quackback and connect it with our Linear for product development, which means that testers will have direct sync with what is being worked on, vote on features they want, see what issues have been completed, and have discussions with everybody. This will create a deeper, faster, and more dynamic relationship between testers and our team.
Releases:
We will have multiple pipelines for releases. Nightly build is the latest stage of our development and can be unstable, which typically gets released daily to our internal team. Alpha build is more stable, and gets packaged to testers when it is ready to test. Changelogs for both will be available. Eventually, we anticipate that alpha builds will be released on a near daily cadence as well.
Access:
We will rollout testing access across multiple cohorts, starting small and growing larger with each cohort. This is to ensure that we can properly absorb feedback. The goal isn’t just to get users on the product, it’s to make something people truly love to use. At this early product stage, opening up access to everybody on the waitlist would create an excess of input that we would not be able to process, which defeats the purpose entirely.
Communication:
We will have multiple channels to communicate, however the primary means will be two. One, the Anytwo Feedback Board (on Quackback) and the Anytwo Testers Space (on Anytwo). We may use other avenues as fallbacks if necessary, such as a space in Anytype.
Data Integrity:
We do not recommend for testers to use Anytwo with data that is precious to them and without backups. While it’s unlikely that absolute data loss would occur, we cannot make guarantees. At this stage, development speed is our priority. This means that breaking changes that render past vaults obsolete and forces new vault creation may happen.
Testing Cohorts
While testers are able to fully use the application however they wish, we aim to guide testers to focus their attention during each phase. Why? Having many testers provide feedback in undeveloped areas of the app isn’t productive.
Below is a rough outline of what that may look like at a high level, but is likely to change.
First Cohort: Setup
Timeline: starting this week, depending on success rate we will release more and more.
- Can you install Anytwo on your device?
- Can you receive updates to Anytwo?
- Can you provide feedback to our team?
- Can you receive updates from our team’s progress?
Second Cohort: Editor
Timeline: immediately after all of the first cohort are successfully in.
- Does the editor behave as you expect?
- Is there any missing key functionality?
- Are there shortcuts or workflows you feel are needed?
- Etc.
Third Cohort: Collections
Timeline: immediately after feedback loop integrations are smooth.
- Are Collections able to solve your needs?
- Is there any missing key functionality?
- How would you improve the onboarding?
- Etc.
Additional Cohorts
As the situation progresses, we will make more updates on future cohorts.
Timeline
As mentioned, our goal is to reach a public release of Anytwo by the end of the year. This means that we want to prioritise thorough testing of core functionality to get Anytwo to a state where our community loves to use it.
Our goal is to roll out to as many testers as we can, as soon as we can. We will prioritise testers who marked themselves as active testers, paid members, nightly testers of Anytype, and other key contributors. If you are really want early access to Anytwo, please message me and I will see what we can do.
The roadmap will be publicly available after it has been crafted with the community of testers.
Join testers of Anytwo
If you have not already signed up, you can do so here: Any: Early Tester Waitlist