Artifact box

A tool for secure storage and controlled distribution of build artifacts for QA and engineering teams.

My Role

Solo Product Designer · End-to-end

Platform

Mobile · Internal tool

Scope

End-to-end redesign · Research · UX · UI · Ownership

Product overview

Artifact Box is an internal build-and-device management tool used by QA and engineering teams in the gaming industry during development and testing. The platform brings together build artifacts, device activation, and external sharing.

Process

Discovery. Interviews with QA leads and engineers to understand real usage scenarios, roles, and key pain points.
Analysis. An audit of the current product and a catalogue of every workaround teams had built in real work.
Validation with users. Checking key insights and early concepts with QA and engineering teams before moving into development — iteratively refining scenarios and prioritizing solutions.
Design. Designing the new product structure, from low-fidelity flows to high-fidelity interfaces built on MUI.
Validation with engineers. Aligning solutions on technical feasibility, infrastructure constraints, and integration into existing systems before handoff.

Problem

No centralized access control. The system didn't provide a unified access model for build artifacts: storage and distribution weren't tied to formal security rules.
No traceability. There was no way to track where artifacts were or how they spread after being passed between teams and devices.
Fragmented processes. Work with artifacts and devices ran through manual, scattered practices outside the main system.
Rising operational load. Teams compensated for the tool's limitations with their own processes and workarounds.

7 screens

Browsing and drill-down — Navigation moves from folders down to a specific build and its recipients. Grouping folders by type keeps the path predictable and surfaces each artifact's target device up front — without extra drilling.

Sharing a build — a one-time email link that sends the build to external collaborators for testing: the link makes it possible to clearly track the recipient and spot any further distribution. Or a QR code to pass an artifact within the team across whitelisted devices.

Folder actions — rename and lock, with locking preventing new uploads until unlocked.

Filtering and searching builds by platform, date and version, with clear empty and result states.

Device management — activate and deactivate devices to control which can receive builds.

Pairing a new device — assign an owner, activate by QR, with guards against duplicate pairing.

Searching and filtering devices by status, owner and platform.

Strategy — coming soon

Personas — coming soon

UX artifacts — coming soon

Inside the Figma file

Figma file organization — How the file is organized — a cover and project doc, then flows grouped by area (browsing, builds, devices), each with an info block, screen frames, and a dev-ready handoff marker.

Collaboration

Product Coordinator. Together we defined user problems, priorities, and constraints. I clarified the task context and validated solutions before implementation began.
Design Lead. We aligned solutions with the overall product concept, the design system, and visual principles.
Developers. I supported implementation — explaining scenarios and interactions, discussing technical constraints, and adapting solutions where needed.
QA. We checked that interfaces matched the scenarios, found UX/UI inconsistencies, and improved the quality of the final product.
Support team. The main source of user insights. Through interviews and testing, I surfaced problems, tested hypotheses, and validated solutions.

Results

The tool moved from fragmented, workaround-based use to a predictable infrastructure system that teams came to rely on in their daily work.

Stabilized storage management. Automated lifecycle tracking removed the need for manual cleanup cycles and reduced operational storage-management work.
Fewer device-activation errors. A simplified flow cut the number of steps, reduced errors, and lowered support load.
Stronger distribution security. A controlled access model replaced informal sharing, lowering data-leak risk and improving control over artifact distribution.
Reduced operational friction. Engineering teams stopped relying on workarounds and began using the tool as a stable system.
Faster work with artifacts. Unified table interfaces reduced context-switching and sped up finding and checking the status of resources.

Next project

Pulse