1. Purpose of the Closed Testing

The purpose of this 14-day closed testing phase is to validate the app’s functionality, stability, and user experience in real-world conditions before applying for production release on Google Play.

We aim to:

  • Collect real user feedback on usability and reliability.

  • Identify and fix potential bugs or performance issues.

  • Verify that key features (location, opening hours, “Nearest Toilet” navigation, notifications) work seamlessly across multiple Android devices and versions.

2. Testers and Test Group Setup

  • Target group: 20–30 real testers, including locals, tourists, and people with specific needs (e.g., accessibility users).

  • Recruitment: Testers are invited via Google Play closed testing links, email, and direct outreach (friends, family, and volunteer users).

  • Diversity: Testing includes different devices (Samsung, Pixel, Xiaomi, etc.) and Android versions (12–14).

3. Testing Schedule and Activities

Week Focus Area Key Actions
Week 1 (Days 1–7) Functional & Stability Testing Test location detection, nearest toilet feature, AdMob banner display, and map marker behavior. Report any crashes, lags, or incorrect locations.
Week 2 (Days 8–14) User Experience & Improvement Collect feedback on design, text clarity, loading speed, and ease of navigation. Verify push notifications, updated session handling, and offline behavior.
Throughout Continuous Fixes & Updates Deploy at least one update (v1.x.x) based on tester feedback. Track performance metrics and log errors via Expo/React Native monitoring tools.

4. Feedback Collection

Feedback is gathered through:

  • Direct messages and short interviews with testers.

  • Google Form / email collection for written responses.

  • In-app behavior observation (how long users stay active, which features they use most).

Key feedback points:

  • App simplicity and clarity of design.

  • Accuracy of restroom locations and opening hours.

  • Stability of map loading and GPS tracking.

  • Usefulness of push notifications.

5. Improvements Planned During Testing

Based on feedback, the following actions are scheduled:

  • Optimize map loading and caching of restroom data.

  • Improve session persistence and login stability.

  • Adjust banner display for different screen orientations.

  • Refine translations and accessibility text.

  • Prepare a short “What’s New” section for the next release.

6. Expected Outcomes

At the end of the 14-day test period, we expect:

  • Verified stability with no major crashes.

  • Positive tester feedback (≥80% rate app as “simple” or “very useful”).

  • One or more app updates based on feedback.

  • Documented improvements ready for the production release application.

7. Summary

The closed testing phase will ensure that Krapp meets Google Play’s production readiness standards, backed by real user engagement and documented improvements. The goal is a stable, well-tested, and helpful app that genuinely serves locals and visitors in Iceland.