None?
also none
From Concept to Prototype
The earliest versions of OSCIL-8R were intentionally simple.
My primary goal was not visual polish but proving that the underlying concept was technically achievable.
The project went through several iterations as I explored different approaches.
Iteration 1: Browser Prototype
The first version was built as a simple React application running in the browser.
Audio data was captured through a user's microphone and translated into visual output.
While functional, this approach presented limitations around usability, performance, and integration with music sources.
Iteration 2: Electron
To move towards a desktop experience, I experimented with Electron.
Although it solved some architectural challenges, I was unhappy with the resulting application size and resource requirements.
Iteration 3: Tauri
After further research, I ultimately adopted Tauri as the foundation of the project.
This provided the balance I was looking for:
- Lightweight distribution
- Strong performance
- Native desktop capabilities
- Familiar React-based front-end workflows
The final architecture combines a React front end with a C++ backend responsible for audio processing and system-level functionality.
Designing an Experience
Unlike many software products, OSCIL-8R does not revolve around complex workflows or task completion.
The primary objective is creating an engaging sensory experience.
As development matured, I began exploring visual directions inspired by:
- Analogue oscilloscopes
- Vintage synthesisers
- Hi-fi equipment
- Retro-futuristic industrial design
I deliberately introduced subtle depth and physicality into the interface to make it feel less like a conventional application and more like a piece of audio equipment.
The goal was to create an experience that felt tactile, expressive, and closely connected to the music itself.
Balancing Simplicity and Customisation
One challenge throughout development has been balancing accessibility with flexibility.
At its core, OSCIL-8R performs a single task.
However, users experience music differently and often have strong preferences regarding visualisation behaviour.
To support this, the application includes:
- Multiple visualisation options
- Extensive parameter controls
- Real-time adjustments
- Pre-set creation and management
Rather than overwhelming users with complexity, settings are organised to encourage experimentation and designed to be a part of the experience - not hidden behind a menu.
Learning Through Building
Perhaps the most valuable aspect of OSCIL-8R has been the opportunity to learn through building.
The project pushed me well beyond my existing development experience and required me to explore:
- Desktop application architecture
- Audio processing
- Performance optimisation
- State management
- Framework evaluation
- Cross-language communication between React and C++
Unlike my professional projects, there were no predefined requirements, stakeholders, or deadlines.
Every technical and design decision was my own responsibility.
This freedom allowed me to experiment, fail, iterate, and ultimately develop a much deeper understanding of both software engineering and product creation.
Current Status
OSCIL-8R remains an active project and continues to evolve.
The current focus is refining the experience, improving performance, and preparing for a public alpha release.
Future development will be heavily influenced by user feedback, allowing the product to evolve based on how people actually interact with it rather than assumptions made during development.
Reflection
OSCIL-8R began as a personal curiosity but became one of the most valuable projects I have undertaken.
It challenged me to move beyond my comfort zone as a designer, deepen my technical skills, and think about software from a fundamentally different perspective.
Most importantly, it reminded me that successful products are not always defined by efficiency or productivity.
Sometimes the goal is simply to create an experience that people enjoy returning to.
