Yes — I can commit to using Spotted for at least three weeks and sharing structured feedback on my experience, including usability, features, issues encountered, and suggestions for improvement.

Pretty often — whenever I’m out with friends or at social events, I like capturing moments and group photos. It helps me keep memories and share them later.

One example of giving feedback that led to product improvement happened during a virtual learning project where I was helping review an early version of a digital math practice module for primary-grade students. After piloting it with a small group, I noticed that while the content accuracy was strong, students were frequently dropping off midway through activities. Instead of just reporting “low engagement,” I gathered specific observations and simple metrics — completion rates per activity, average time spent per screen, and common points where students asked for help. I also collected short student comments about what confused or bored them.I shared feedback with the development team in a structured way: first highlighting what worked well (clear instructions and strong visuals), then pointing out friction points. I explained that multi-step instructions on a single screen were overwhelming for younger learners and that the lack of immediate feedback after each answer reduced motivation. I suggested splitting tasks into smaller steps, adding instant correctness indicators, and including a progress bar so students could see how close they were to finishing.The team implemented these changes in the next iteration. After the update, completion rates increased significantly, students required fewer clarification prompts, and session time became more consistent rather than dropping sharply halfway through. The key factor was that the feedback was specific, evidence-based, and paired with practical suggestions rather than just criticism, which made it easier for the product team to act on it quickly.