Add AI virtual try-on to a fashion shopping app
A mobile app should not contain a TryRobe Business license key. The app uploads approved images to a merchant-controlled backend, which authenticates the user, enforces limits, calls TryRobe, and returns job status and a protected result.
Mobile security boundary
App binaries can be inspected, so no embedded secret should be treated as confidential. Use short-lived customer sessions with your own backend and keep the TryRobe key exclusively on that server.
Resilient app experience
Persist the merchant job reference so generation can continue if the app is backgrounded or closed.
- Show upload progress separately from generation progress
- Resume status checks after app relaunch
- Use push notifications only from the merchant's trusted backend
- Handle result expiry
- Offer a clear retry path without double charging
Image and privacy guidance
Explain why a photograph is needed, request only required permissions, avoid automatic gallery uploads, and never place photos or signed URLs in analytics events or crash-report breadcrumbs.
Frequently asked questions
Can the mobile app call TryRobe directly?
No. A production Business license key must remain on a trusted backend.
What if the user closes the app during generation?
The merchant should persist the job ID and resume status retrieval later; TryRobe's backend job and credit flow does not depend on the client remaining open.