iStaging ONE — Capture Once, Create Everywhere
One mobile app unifying panorama capture, 3D object scanning, and content management across three product ecosystems — users capture once and choose their output after.
Two capture paradigms with opposite instincts — one camera UI.
Business
- Consolidate three separate tools into one app
- Widen 3D adoption beyond technical experts
User
- Capture without understanding computer vision
- Quick results for sellers, real depth for professionals
Technical
- Precision alignment vs. spatial coverage in one flow
- Reflective and repetitive surfaces defeat photogrammetry
Conflicting capture models
Panoramas need center-point precision; 3D scanning needs full spatial coverage.
Invisible branching
One photo set feeds three reconstruction pipelines the user never has to name.
Failure modes in the lens
Glass and chrome defeat the algorithms — the UI must prevent, not explain.
Three ecosystems' expectations
VR, AR, and META users arrive with different mental models.
I owned the capture experience end to end — from hardware guidance to information architecture.
Owned
- Cross-Product UX Strategy
- Capture Workflow Design
- Information Architecture
- Interaction Design
Collaborated with
- Product Manager
- Platform Director
- App & Back-End Engineering
One capture, many outputs.
The asset library as the convergence layer
Four capture methods and three platforms threatened four parallel workflows.
Every input — Rotator, THETA, ScanKit, upload — deposits into one asset library; projects pull from it.
Users think in content — my panoramas, my scans — not in platform names.
New capture methods plug in without restructuring the app.
Capture once, choose format after
3D formats — ScanKit, 3DGS, photogrammetry — are meaningless before users see results.
One three-angle ScanKit capture generates all three outputs on demand.
The technical decision moves to after users hold tangible results to compare.
Users start scanning without learning reconstruction technology first.
Accessible default, optional depth
Most sellers need a spinnable product view, not true 3D — professionals need both.
ScanKit drag-to-view is the default; 3DGS and photogrammetry are upgrades from the same data.
Serve the majority instantly without forcing either group through the other's workflow.
The steepest barrier to 3D adoption — understanding it — was removed.
Guided capture coaching
Real-time alignment and three-angle guidance turn photogrammetry rules into camera UI.
Multi-format pipeline
One photo set feeds ScanKit, 3DGS, and photogrammetry outputs.
Assets-then-projects model
Capture first, create later — three taps from camera to published project.
The trade-off — I centered the app on assets instead of product platforms. It broke internal naming conventions, but users think in their content — not in which platform hosts it.
What I'd improve — capture-failure feedback. The UI prevents most photogrammetry failures, but explaining why a reflective object failed still falls to documentation.
Next time — when outputs branch invisibly, preview earlier — showing format comparisons before the first capture would have shortened the learning curve further.
