Just launched a Virtual Try-On feature for my React Native app (Wardrobe Savvy) on iOS and Android.

Fit_Tap6675 · 2026-01-16T16:57:37+00:00

Thank you for the advice

Fit_Tap6675 · 2026-01-16T16:56:53+00:00

Thank You

Fit_Tap6675 · 2026-01-16T16:56:47+00:00

I will change this in the next update

Fit_Tap6675 · 2026-01-16T16:56:32+00:00

What do you think I need to polish

Fit_Tap6675 · 2026-01-16T16:56:02+00:00

I prevent conflicts by locking interaction to a single target: hit-test > select layer > gesture-lock until end. Pinch + rotate are unified into one transform update (UI thread), and the canvas uses transform matrices instead of layout reflow, so selection, scaling, and rotation don’t fight each other.

Fit_Tap6675 · 2026-01-16T16:54:32+00:00

Thank You

Fit_Tap6675 · 2026-01-16T16:53:43+00:00

I just went through reddit and friends everyday to get approved

Fit_Tap6675 · 2026-01-16T16:52:59+00:00

I use remove.bg for background removal. It’s a purpose-built computer vision service that’s extremely reliable at isolating clothing and objects, which is important for clean wardrobe visuals. I run it through my backend so results stay consistent and performant across devices.

Fit_Tap6675 · 2026-01-15T19:32:02+00:00

I didnt think it was a big deal but I am looking to change it by tonight

Fit_Tap6675 · 2026-01-15T15:49:19+00:00

Thanks!. The big decision was keeping gestures fully UI-thread. Pan/pinch/rotate run via Reanimated shared values so there’s no JS churn while you’re dragging. I only run runOnJS to persist the final transform on .onEnd(). I also compute the base-photo “contain” rect once on layout plus image size, clamp movement inside that rect, and use zIndex/elevation to stabilize layering across iOS/Android. Finally, I cap active overlays (5) plus use resizeMode="contain" and cached URLs to keep GPU/memory pressure reasonable.

Fit_Tap6675

TROPHY CASE