What was tested?
| Testing area | Coverage |
|---|---|
| Devices | Samsung, Realme, Motorola, OnePlus, Samsung S9 Tablet |
| Android versions | Android 10 – Android 16 |
| Orientation | Portrait |
| UI testing | Subscription paywall, project timeline, header, status bar, home-screen actions |
| Functional testing | Subscription availability, project deletion, UI actions, project creation |
| Stability testing | Subscription selection and project-management interactions |
| Scenarios (4) | Annual Subscription, Timeline / Project Deletion, Light Theme UI, New Project Actions |
| QA findings | 4 issues + 2 enhancement suggestions |
- 1
The Developer's Problem
Google Play requires new personal developer accounts to run a closed test with at least 12 testers, continuously opted in for at least 14 days, before applying for production access. For a developer shipping their first app, that's an unfamiliar hurdle on top of the build itself: recruiting testers, keeping them engaged for two weeks, and then answering Google's production questionnaire.
- 2
Starting Situation
MyLifelens was functionally complete, with a monetised model: one free project, and a Pro subscription — offered as monthly and annual plans — for unlimited projects. That made the paywall a critical path to test alongside the core flows of creating projects, adding photos and reviewing timelines.
- 3
Testing Process
Testers used the app through the full 14-day cycle. It was tested in portrait mode on Samsung, Realme, Motorola and OnePlus phones and a Samsung S9 tablet, across Android 10 to Android 16. Functional testing covered subscription availability, project creation and deletion, and UI actions; UI testing covered the subscription paywall, project timeline, header, status bar and home-screen actions.
- 4
Issues Identified
The QA report recorded four issues, two of which it marked as the priority:
- Priority: on the Pro upgrade paywall, the Annual plan showed as "Not available" while the Monthly plan could be purchased.
- Priority: there was no visible way to delete an individual photo frame or an entire Full Story timeline.
- In the light theme, status-bar icons had low contrast and the "g" descender in the header text was clipped.
- Three separate home-screen buttons all performed the same New Project action, blurring the primary action.
- 5
Enhancement Suggestions
The report also recommended two improvements: Google Play In-App Updates, and the Google Play In-App Review API. Every finding — with its screen, description and recommendation — is summarised in the QA report section below.
- 6
Production Access Guidance
Once the 14-day cycle was complete, the developer received a production application guide covering each part of Google's questionnaire — about the closed test, about the app, and production readiness — plus the extra question Google asks if a previous application was rejected.
- 7
Outcome
MyLifelens is now publicly available on Google Play. The developer described the experience as doing "exactly what he says on his site" and plans to return for future projects.
Deliverable
Inside the QA report
MyLifelens — Comprehensive Android Application Testing & Functional Evaluation
Teekam's QA Team · September 2026 · 8 pages
6
Findings
4
Issues
2
Enhancements
Scenarios tested (4)
- Annual Subscription
- Timeline / Project Deletion
- Light Theme UI
- New Project Actions
Issues found (4)
#1PriorityFunctional / SubscriptionAnnual subscription is unavailable
Screen / flow: Pro upgrade paywall
The Annual plan was displayed as "Not available" while the Monthly plan could be purchased, so users couldn't choose the annual option.
Recommendation: Verify the annual subscription configuration in the store and make sure the plan is correctly connected to the app.
#2PriorityFunctional / Project managementNo delete option for timeline or project frames
Screen / flow: Full Story timeline / project frames
There was no visible way to delete an individual frame/photo or a complete timeline, limiting users' control over their content.
Recommendation: Add delete actions for frames and, where appropriate, whole projects — with a confirmation prompt to prevent accidents.
#3UI / Visual designLow status-bar contrast and clipped header text
Screen / flow: Light theme / app header
In the light theme, status-bar icons had low contrast against the background, and the "g" descender in the header text was clipped.
Recommendation: Adjust status-bar icon appearance for contrast, and review the header's font metrics, line height and container height.
#4UI / UsabilityThree buttons perform the same New Project action
Screen / flow: Home screen
Three separate home-screen buttons all created a new project, cluttering the screen and weakening the primary action.
Recommendation: Consolidate into one clearly placed New Project button, or give each button a distinct purpose.
Enhancement suggestions (2)
#5Usability / MaintenanceImplement In-App Updates
Screen / flow: Application updates
Users on older versions may miss fixes, security improvements and new features.
Recommendation: Integrate Google Play In-App Updates — flexible for non-critical releases, immediate for critical ones.
#6User engagement / UXAdd In-App Rating and Review
Screen / flow: Settings / App review
Letting users rate the app without leaving it makes feedback easier to give.
Recommendation: Integrate the Google Play In-App Review API and trigger it at positive moments that don't interrupt the user.
Report conclusion: The report's priorities were the unavailable annual subscription and the missing deletion controls, followed by the light-theme visual issues and the duplicate New Project actions — with in-app updates and in-app reviews recommended for maintenance and engagement.
“Tekkham was great to work with on my first app build Mylifelens, he does exactly what he says on his site, I'm looking at new apps and ideas and will defiantly reach out to him on future projects. Thanks”
Evidence
- Google Play listing for MyLifelens
- Developer testimonial on Reddit, r/testimonials
- Full QA report — 8 pages (PDF)
- Production application guide (available on request)
What this case demonstrates
For a monetised app, closed testing is a chance to check the parts that earn money, not just the parts that look good. Here, testing on real devices caught an annual subscription that couldn't be bought — a revenue issue invisible in day-to-day use — alongside a missing content-management control and light-theme polish issues, all documented with steps to reproduce before the app went public.
Important note
Google Play controls all production access decisions, and outcomes vary by app and account. This case describes one engagement; completing closed testing does not guarantee approval for any other app or on any particular timeline.