Help test AYOHI apps before public release
This page provides testing information for AYOHI apps across supported release channels. Tester access may depend on product readiness, platform review, supported devices, region, account eligibility, and available test capacity.
Testing helps improve app quality before a wider release. Testers may help identify crashes, usability problems, unclear screens, device compatibility issues, broken flows, confusing wording, missing translations, performance problems, or privacy and support questions that should be clarified before production.
Current testing programs
The table below lists current and planned AYOHI app testing programs. Links will be updated when each test track becomes available.
| App | Supported platforms | Current phase | Tester link |
|---|---|---|---|
Stowlet
|
To be announced | Build / early testing preparation | Tester access |
Build and testing phases
AYOHI apps may move through several phases before public release. Not every app will use every phase, and the order may vary depending on the product, supported platform, distribution-channel requirements, review status, and development progress.
| Phase | Purpose | Typical access |
|---|---|---|
| Build phase | Core features are being built, reviewed, adjusted, and prepared for installable testing. | Internal development only. |
| Internal testing | Early app builds are checked for installation, basic flows, crashes, account behavior, permissions, and obvious issues. | Small internal tester group. |
| Closed testing | A controlled group of testers can install and use the app before wider availability. | Approved testers by email list, group, invitation, or official test link. |
| Wider testing | A broader group may access the app before production if the product is ready for additional feedback. | Public or semi-public test link where available. |
| Release candidate | The app is close to production and is reviewed for stability, release readiness, privacy information, and support details. | Selected testers and release review. |
| Production | The app is available publicly through official release channels. | General users, depending on supported platforms, region, distribution channel, and device compatibility. |
How to join a test
When an AYOHI app test is available, testers may need to follow an official link, use an approved account or email address, join a tester list, accept a testing invitation, or install the app through the relevant distribution channel.
Testers should use the same account or email address that was approved for the test. If a test link is opened with a different account, access may not work or the app may appear unavailable.
Tester request template
Users who want to join a test can contact AYOHI using the format below.
Subject: AYOHI App Testing Request
App name:
Testing account email:
Device model:
Operating system and version:
Country:
Testing experience, if any:
Why you want to test the app:What testers should check
Helpful testing feedback is specific and practical. Testers should report what happened, what they expected to happen, and how the issue can be reproduced.
| Testing area | What to check |
|---|---|
| Installation | Whether the app installs, opens, updates, and launches correctly on the device. |
| Core flows | Whether the main screens, buttons, navigation, saving, editing, deleting, and app flows work as expected. |
| Crashes and freezes | Whether the app crashes, freezes, slows down, reloads unexpectedly, or loses information. |
| Design and readability | Whether the interface is clear, readable, responsive, and understandable on different screen sizes. |
| Permissions | Whether permissions are understandable and connected to features that need them. |
| Privacy and data | Whether account behavior, data saving, deletion options, privacy information, and support links are clear. |
| Release readiness | Whether the app description, screenshots, title, icon, feature wording, and support information feel accurate. |
How to report feedback
Testers should send feedback through the official contact link or through the testing channel where available. A useful bug report includes the app name, app version, device model, operating system version, steps to reproduce, screenshots, and a short explanation of what happened.
Subject: AYOHI App Testing Feedback
App name:
App version:
Device model:
Operating system version:
Issue type:
Steps to reproduce:
Expected result:
Actual result:
Screenshot or screen recording:
Additional notes:Important testing notes
Test builds may contain unfinished features, temporary screens, test data, bugs, missing polish, incomplete translations, placeholder graphics, or changes that will not appear in the final public version.
Testers should not rely on test builds for critical personal data, important records, business workflows, financial information, medical information, emergency information, or any information that cannot be safely lost.
Privacy and tester data
Testing may involve support messages, tester email addresses, device information, diagnostic information, crash reports, screenshots, feedback messages, and app usage information where applicable.
General privacy information is available in the Privacy Policy. Deletion request information is available on the Data Deletion page. Data and security information is available on the Data & Security page.
Testing availability
Testing access may be limited. Not every tester request can be accepted, and test links may expire, change, become unavailable, or be limited by distribution-channel rules, region, device compatibility, account status, review status, or test capacity.
When an app is ready for wider release, the relevant product page and this testing page will be updated with the most accurate availability information.
Contact for testing
Use the official contact link below to request testing access, send feedback, report a test issue, or ask a question about an AYOHI app testing program.