You don’t need to be a developer to help improve Daty. You just need to try the early version, pay attention to your experience, and tell us what happened.

As members begin exploring the initial User Acceptance Testing (UAT) version, every clear observation can help us understand what works well and what needs attention.

Here’s how to make your testing useful.

Start with something you actually want to do

Rather than tapping through every screen, begin with a simple task available in your test version.

You might try to complete your profile, find a setting, or read an explanation and decide whether you understand it.

Use the product at your own pace. Notice where the next step feels obvious and where you have to stop and think.

You don’t need to find a major bug to contribute. A confusing label, a missing confirmation, or an explanation that leaves you unsure can all be worth reporting.

Notice what feels easy, too

Feedback helps us understand what to preserve as well as what to improve.

If a step is straightforward, tell us why. If an explanation helps you understand something, point to the part that made the difference.

For example:

“The short introduction before this step helped me understand what information I needed. I could continue without going back.”

That is more useful than simply saying, “Looks good.” It tells the team what supported your experience.

Tell us what you tried, expected, and saw

When something doesn’t work as expected, three details make your feedback easier to act on:

  • What you were trying to do.

  • What you expected to happen.

  • What actually happened.

Here are a few illustrative examples—not reports of known Daty issues.

Instead of: “My profile doesn’t work.”

Try: “I edited my profile and tapped Save. I expected the changes to remain, but when I reopened the page, the previous information was still there.”

Instead of: “This screen is confusing.”

Try: “After completing this step, I couldn’t tell whether it had saved. I looked for a confirmation message or a button showing what to do next.”

Instead of: “The explanation isn’t helpful.”

Try: “I understood the first paragraph, but I wasn’t sure what the phrase in the second paragraph meant. A plain-language definition or example would help.”

You don’t need to diagnose the cause or suggest a technical fix. A clear description gives the team a place to start.

Include a little context

For a technical issue, mention whether you were using an Apple/iOS or Android device. If available, include your device model, operating system version, and the Daty test version.

It also helps to say whether the issue happened once or each time you repeated the same steps.

If you include a screenshot, check it before sharing. Hide private messages, personal details, and information about other people. Never include passwords or verification codes.

Share your perspective

Daty is being developed to support reflection and relationship understanding. During testing, consider whether its explanations are understandable, appropriately worded, and useful to you.

If an insight doesn’t resonate, explain which part and why. Your perspective is valuable feedback. You don’t need to accept an explanation simply because the product generated it.

Send your feedback directly in the app

Use the in-app feedback option to share your experience with the Daty team.

Whenever possible, submit your feedback while the details are still fresh. Describe the step you were on, what happened, and anything that would help the team understand or reproduce the issue.

Use the same channel for suggestions and positive feedback, too. Knowing what feels clear and useful helps us make better decisions as development continues.

Help us make the next version better

You don’t have to test everything. One carefully described experience can be more useful than a long list of general impressions.

Try something that matters to you. Notice what happens. Tell us through the app.

That’s how your first look at Daty can help shape what comes next.