Feedback Program
This playbook summarizes the feedback workflow documented in our App Store Distribution Guide. Use it to understand how we collect input, what to test, and how we turn your suggestions into product improvements.
1. Channels & Contacts
Beta Feedback
Email beta@colorsoflife.com for TestFlight builds. Include screenshots or screen recordings when possible.
Production Support
Use support@colorsoflife.store or the in-app help desk for live users. We aim to reply within 1–2 business days.
Direct In-App Reports
TestFlight testers can send annotated screenshots directly through the TestFlight feedback interface. These reports automatically include device and session diagnostics.
2. Priority Test Checklist
The beta testing email template from our distribution guide lists the must-hit scenarios:
- Sign in with Google and confirm onboarding completes.
- Upload a well-lit photo to create an avatar (allow 30–60 seconds).
- Search for items like “summer dress” or “casual t-shirt” and review results.
- Try on at least three outfits and save a look to your wardrobe and camera roll.
- Chat with Emma AI for outfit advice and note any confusing responses.
Report crashes, unexpected UI behaviour, slow performance, or missing guidance.
3. Request Template
Use this TestFlight email template when asking for structured feedback:
Subject: TestFlight Build 1.0.0 (1) - Testing Checklist Hi Beta Testers! Thank you for helping test Colors of Life! Please cover the following: [ ] Sign in with Google [ ] Upload a clear photo for avatar creation and wait for the result [ ] Search for “summer dress” or “casual t-shirt” [ ] Try on at least 3 different items [ ] Chat with Emma AI and ask for outfit advice [ ] Save items to your wardrobe and export a look to Photos Please report crashes, confusing flows, or slow performance. Use TestFlight’s screenshot + feedback feature so we get context automatically. Thank you! The Colors of Life Team
4. Turning Feedback into Action
Our distribution guide maps the most common comments to the actions we take internally:
| Feedback | Action |
|---|---|
| “Avatar creation failed” | Improve error handling, add retry logic, review fal.ai job logs. |
| “Upload crashed the app” | Patch image processing pipeline, add client-side validation. |
| “Try-on flow is confusing” | Ship onboarding tooltips and inline guidance. |
| “Search results feel off” | Tune filtering weights, review Brave/Google query logs. |
| “App feels slow” | Optimize image caching, profile startup metrics, add loading states. |
5. Sharing Your Ideas
When submitting feedback, please include:
- Build number and device model (auto-filled when using TestFlight).
- Expected vs. actual behaviour, plus steps to reproduce.
- Screenshots or screen recordings for visual context.
- Your feature ideas or quality-of-life improvements.
Prefer async? Reach us at feedback@colorsoflife.com and we will route the request to the right squad.
6. Release Readiness
- When feedback volume drops and major bugs are closed, we cut a fresh TestFlight build.
- External testers are alerted automatically; internal testers manually promote builds.
- We continue to use TestFlight post-launch for early feature access and A/B experiments.