Project at a Glance
Client
Cylindo
Industry
3D Product Visualization & E-commerce Tech.
The Challenge
A high volume of critical daily bugs in the core 360 Viewer was damaging UX and causing customer churn. The small internal team lacked the resources to stabilize the current product and refactor for the future.
Key Technologies
Pure JavaScript/Web Component Development. Focused on native web performance, cross-browser compatibility, and test automation frameworks (for 1,000+ tests).
The Solution
Phase I provided rapid stabilization through high-impact bug fixing (v2.3). Phase II involved a complete re-architecture to a Zero-Dependency design, integrated with over 1,000 automated test cases.
THE KEY RESULT
Achieved 100% resolution of critical issues, reduced support ticket time to under 48 hours, and delivered a future-proof, high-performance product with 4K Zoom capability.
The Challenge: Bug Firefighting was Limiting Growth.
The client, Cylindo, is a leader in 3D product visualization for the furniture e-commerce industry, supporting retailers worldwide.
Their 360 Viewer component is mission-critical, embedded directly into their customers' retail sites, meaning any failure has a direct impact on revenue and customer experience.
After years of rapid scaling, their platform was suffering from two critical bottlenecks:
-
Massive Daily Bug Volume and Reputational Risk: The legacy v2 code base was generating a large, daily influx of critical, cross-browser bugs. These issues directly affected end-user experience (UX) on high-traffic e-commerce sites, leading to negative customer feedback and threatening churn among enterprise clients. The situation required constant, immediate firefighting by the internal team.
-
The Innovation Bottleneck: Cylindo's internal development team was resource-constrained and perpetually focused on emergency maintenance for the v2 viewer. This exhaustive focus on stabilizing the current product meant they had virtually no bandwidth left to address the mounting technical debt or invest in the crucial next generation of their platform (v3). Cylindo urgently needed an elite engineering partner to rapidly stabilize the existing crisis and architect a robust, scalable future.
Our Two-Phase Approach: First Stabilize, Then Re-Architect.
We deployed a proven strategy to first halt the customer dissatisfaction and then engineer a long-term solution.
Phase 1:
Rapid Stabilization (The Immediate Fix)
The critical goal was mitigating risk and restoring user confidence. We opted for an iterative, high-impact bug fixing strategy:
-
Priority: Focused solely on fixing customer-reported bugs in the v2 360 Viewer that had the highest negative impact on live e-commerce websites.
-
Methodology: Gradual, periodic deployments of v2.x fixes over three months, minimizing deployment risk while providing customers with fast, visible relief.
-
Outcome: The viewer reached a stable v2.3, providing the foundation and time needed for Phase II.
Phase 2:
Future-Proof Refactoring (The Scalable Architecture)
Once stability was achieved, we focused on eliminating the root cause of the previous instability and designing for 5+ years of growth.
-
Zero-Dependency Architecture: We completely re-architected the 360 Viewer, removing all external library dependencies. Impact: This decision significantly reduced payload size, maximized rendering performance, eliminated third-party security risks, and guaranteed superior long-term maintainability.
-
Performance Engineering: Focused optimization delivered faster load times and smoother user interactions across all devices.
-
Next-Gen Features: Developed and integrated high-resolution 4K zoom capabilities, providing a superior retail experience for the end-user.
From Manual Checks to Automated Certainty.
To ensure the web component worked flawlessly across Cylindo’s entire client ecosystem (different browsers, platforms, and e-commerce integrations), we built an impenetrable quality barrier.
-
The Action: We designed and implemented over 1,000 automated test cases for the 360 Viewer.
-
The Value: This comprehensive regression suite runs continuously, guaranteeing that every commit and new feature is cross-compatible and prevents future regressions. This QA rigor is the secret to achieving and maintaining Zero Bugs in Production.
The Metrics That Matter
Seamless Integration, Trusted Ownership.
The success of the technical fixes earned us deep trust with the Cylindo CTO and stakeholders, extending our role beyond simple development. We became embedded in their customer support workflow, ensuring that the developers diagnosing a problem were the same ones writing the fix. This level of holistic ownership defines our partnership model.
In high-stakes e-commerce, software stability is not a feature—it is the platform. Hristov Development ensures your core product is not only bug-free today but architected for future scalability, turning technical debt into a competitive advantage.
FAQ:
Addressing Your Technical & Partnership Concerns.
Q: Why was a two-phase approach (Stabilize then Refactor) necessary?
A: A full refactor would have taken too long to stop the immediate customer dissatisfaction caused by the v2 bugs. Phase I provided rapid relief and stabilized the product in ~3 months, allowing the client to regain customer trust while we strategically planned and executed the Phase II re-architecture for long-term scalability.
Q: What does "Zero-Dependency Architecture" mean for performance?
A: It means the new v3 viewer does not rely on any third-party JavaScript libraries (like jQuery or React). This significantly reduces the total file size (payload), drastically improves loading speed, minimizes potential security vulnerabilities, and removes the risk of external library updates breaking the core component.
Q: How did you manage to integrate the 1,000+ automated tests?
A: We implemented a comprehensive regression test suite that runs continuously after every code commit. This suite covered all known browser, platform, and e-commerce integration points, ensuring that the new v3 architecture remained cross-compatible and prevented future regressions, which is the key to maintaining zero bugs in production.
Q: Why did your role extend to Customer and Tech Support?
A: Our deep understanding of the v2 bug sources and the v3 architecture made us the most effective team to handle tech support tickets. This seamless integration ensured immediate diagnosis and fast resolution (100% closed under 48 hours), turning support into a proactive feedback loop for development.