LiBlul — a 360° virtual tour platform

Context

360° virtual tours remain costly to produce and publish. LiBlul aims to make creating them accessible: import panoramas, compose a tour, share it.

Problem

Building such a platform means holding three topics at once: a visual editor simple enough for non-technical users, performant delivery of heavy panoramas, and infrastructure that absorbs peaks without costing a fortune.

Constraints

• Non-technical end users: the editor must be understood without documentation.
• Heavy panoramas: load time directly conditions conversion.
• User data to protect (accounts, private content).

My role

Founder: product, UX, full-stack development, infrastructure and monitoring.

Approach

Iterate on the editor with real usage, keep the technical foundation simple while performance holds, and measure what matters: tours created, tours viewed, load time.

Architecture

• Full-stack application: Angular client, server-side API.
• Panorama optimisation pipeline (adapted to screens and networks).
• Self-managed hosting, monitoring and automated backups.

Key decisions

• Optimise at import, not at view time: the cost is paid once by the creator, smoothness is guaranteed for visitors.
• Deliberate but bounded nodal editor: composing a tour stays visual, without exposing technical complexity.
• Owned infrastructure: the same cost/control trade-off as the other projects, with product-level monitoring.

Challenges

The image-quality versus file-weight compromise: a tour that loads poorly does not convert. The second challenge is the product itself: defining what makes an editor “simple” (fewer options? better defaults? better flows?).

Outcome

An online platform that lets anyone create and publish virtual tours without technical skills.

What this project demonstrates

Designing a complete SaaS product — editor, delivery, accounts, infrastructure — and driving it from concept to operations.