Deep Dive into the RUXAILAB Codebase: Understanding Architecture for A/B Testing Integration

When I started exploring RUXAILAB, my goal was not just to understand how the platform works, but to figure out how a new system—A/B testing—could be integrated without disrupting its existing workflow. Instead of approaching the repository as a collection of files, I treated it as a system. I focused on understanding how data flows through the platform, how different layers communicate, and where extensibility points exist. Understanding the Core Workflow The first step was to map the lifecycle of a study inside RUXAILAB. From my analysis, the workflow can be summarized as: A researcher creates a study Participants interact with the study interface Responses are stored in Firestore Analytics are generated based on collected data This flow is already well-structured and modular. What stood out to me was that RUXAILAB is not just a frontend-heavy application—it is a coordinated system involving Vue modules, Firebase services, and backend logic working together. Understanding this flow w