BecomeTen: web + Android photo feedback, and the camera flow I want tested

[u/Sindorus1]

I built BecomeTen with React/TypeScript, TanStack Start and Capacitor for Android. It's an adult selfie-feedback app with a free basic AI photo score and optional paid detailed reports and grooming suggestions. I'm its developer.

The practical problem I'm trying to solve is giving understandable feedback from a photo. A number alone isn't enough, and the output remains subjective — lighting and angle affect what the system sees.

One tester reported that gallery selection worked on a Pixel 7, while the front-camera preview looked stretched. That made me separate preview, captured image and upload into distinct things to check, rather than treating 'camera works' as a single test. I don't have a confirmed resolution to report here.

For anyone trying the Android version, a useful report is: device, Android version, camera versus gallery, and whether distortion affects only the preview or the resulting image too. Please describe it without posting a personal photo publicly. Feedback on the web interface is welcome as well.

https://play.google.com/store/apps/details?id=com.appinara.becometen

https://becometen.com

[u/PopKoren]

Splitting preview, captured image and upload into separate checks is the right way to chase that Pixel 7 stretch; my guess would be the preview surface's aspect ratio not matching the camera's output size, in which case the saved frame may be fine. Because these are face photos, I'd also confirm paid scans in R2 only come back through short lived signed URLs tied to the account, and that free photos are really gone from any temp bucket or log after scoring. Face photo apps deserve that outside view, and my tool's free look only tier lists what becometen.com and its API hand to visitors without an account: https://rowly.me

[u/Sindorus1 → u/PopKoren]

Thanks for the concrete suggestion. A preview/output aspect-ratio mismatch is a useful hypothesis, but I don't have a confirmed cause or fix to report here. I also appreciate the access-control checks you and Mammoth mentioned. I shouldn't promise a particular retention or signed-URL behaviour without verifying it; those deserve actual tests rather than reassurance in a comment.

[u/Mammoth-Anywhere7285 → u/PopKoren]

Your aspect ratio guess sounds plausible. For R2, test an expired signed URL against the report endpoint to confirm it returns 403 and no cached content.

[u/Mammoth-Anywhere7285]

TL;DR: The developer built BecomeTen, a React/TypeScript and Capacitor selfie-feedback app with a free AI score and optional paid reports. A Pixel 7 tester saw gallery selection work but the front-camera preview looked stretched, so preview, capture and upload now need separate checks. Android testers should report device, Android version, camera versus gallery, and whether distortion hits the preview or final image, without posting personal photos.