System Evolution
A chronological view of Helyx Labs development
July 2023
Where it Really Began
My journey into building things started back in 2023, when I was in 6th grade.
That was the first time I was introduced to HTML at school. A lot of the credit for making it interesting goes to Saket Sir, who taught it in a very engaging and enjoyable way. The classes never felt dry or overly technical — they felt creative, which made a big difference.
For the first time, I wasn’t just using technology. I was starting to understand how things on the web were actually made.
September 2023
Exploring More
Even though the school lessons were enjoyable, I remember feeling like I had only seen a small part of something much bigger.
That curiosity pushed me to start learning HTML on my own. I spent time experimenting, trying things out, and slowly understanding how pages were structured.
One major advantage I had during this phase was the environment at home. Both my parents are software developers, so I had constant support, guidance, and answers whenever I got stuck or confused.
That support played a huge role in keeping the learning process smooth and encouraging.
Late 2023
Learning by Building
Over the next couple of years, I kept building small projects and websites.
Most of them were never published — they were purely for learning and experimentation. But those projects helped me develop a solid understanding of HTML, CSS, and JavaScript.
More importantly, they helped me become comfortable with the process of creating something from scratch, breaking it, fixing it, and improving it.
This was a very quiet phase — no public releases, no products — just learning and practice.
March 2025
Discovering Python
By March 2025, I wanted to build things that went beyond the frontend.
While I was comfortable with HTML, CSS, and JavaScript, I felt the need to work with something more logic-driven — programs that didn’t just display information but actually performed tasks and calculations.
On my father’s advice, I started learning Python.
I learnt entirely through YouTube, without any formal classes, spending the month exploring the language through practice and experimentation. Python immediately clicked with me and introduced me to a new way of thinking about programming.
It sparked my interest in mathematical computations, logic-based problem solving, and early AI and machine learning concepts
By the end of the month, Python had become a tool I was genuinely comfortable with, marking a clear shift in my journey from frontend development to more general-purpose programming.
April 2025
The Idea of Whispr
In April 2025, I started questioning how inefficient normal computer workflows felt. Even simple tasks required multiple steps, constant window switching, and endless distractions.
That thought led to the idea of Whispr, powered by WhisprAI — a minimal bar that would stay on the screen, listen to voice input, understand instructions, and respond conversationally.
The goal was simple: express intent instead of navigating software.
At this stage, Whispr existed only as a concept, but it marked the beginning of a much bigger direction.
May 2025
First Working Prototype
During the summer break in May 2025, I began building Whispr and developed an early prototype that could record audio on a button click, transcribe it using an open-source model by OpenAI, and open the app or website I instructed it to.
For the first time, Whispr moved from concept to something that actually worked.
August 2025
Whispr Goes Public
In August 2025, our school disabled Google Chat for student accounts, a decision made for safety reasons. Since it had been our primary communication channel, this change created an immediate gap.
In response, I built WhisprLink, which became my first publicly accessible project. It worked, gained real usage, and still exists at its original domain, with access still limited to my classmates.
More importantly, this experience taught me the responsibility that comes with building things for real users. It also changed my mindset — Whispr didn’t have to remain a private experiment; it could be built openly.
September 2025
Building Under Pressure
By September 2025, I had realised that the original “bar at the bottom” idea for Whispr wasn’t very practical. Around the same time, with the CBSE Skill Expo approaching, I decided to quickly build a proper application instead.
That’s when the Helyx Labs App was created — named quite literally because there wasn’t time to overthink branding. I developed the early alpha versions and eventually a working prototype capable of opening apps and websites through voice commands, now in a more stable and structured form.
Shortly after, I learned that the project hadn’t been selected at the school level for the expo. Even so, I continued building and improving the app.
November 2025
Expanding Helyx Core
By November 2025, the Helyx Labs App had evolved significantly. I had integrated Helyx Ignite, Helyx Aud, and Helyx Cogni, along with a proper login and logout system.
These additions allowed the app to handle voice interactions, generate mood-based playlists through Spotify, and use Google’s then-flagship AI models, Gemini 2.5 Flash & Pro for AI-driven features.
This phase also marked the formation of my first real user base, with around 10 active logged-in users using the app.
Around this time, I also began exploring machine learning through Hugging Face, which gave me early exposure to ML concepts and a practical understanding of how servers and hosted systems work.
November 2025
The Birth of Spectra
By December 2025, I had begun questioning the practicality of building a standalone app. Most users simply don’t install niche applications, no matter how capable they are.
That thought led to a new idea: instead of another app, why not build a browser — something people already use constantly? The vision was a productivity-oriented browser that could combine AI, music, focus, and user-centric features in a single environment.
This is when Spectra was conceived. The Helyx Labs App became a proof-of-concept project, and I began developing Spectra, carrying forward its core ideas while introducing an entirely new direction.
February 2026
Spectra Becomes Real
By February 2026, Spectra had reached the 1.x.x stage and had grown into something far more stable and refined. It wasn’t just functional — it performed reliably and smoothly.
The browser now featured polished visuals, improved graphics, and more advanced data handling, making it feel like a complete product rather than an experiment.
Around the same time, I upgraded the website to use a CMS-based system, allowing content to be updated dynamically without modifying the code — a practical improvement that significantly reduced maintenance effort.
March 2026 — Upcoming
Completing Spectra 1.x
By March 2026, Spectra’s first development phase is expected to reach maturity. The 1.x series is centered around a clear objective: making Spectra a stable, usable, and dependable browser.
Spectra 1.0.0 establishes the initial functional browser, with 1.1.0 focusing on UI and homepage refinements, including visual and layout improvements.
Further updates strengthen core browser behavior.
1.2.0 introduces permission handling for device features such as camera, microphone, and location, while 1.3.0 adds history management, persistence, and navigation memory.
The phase is planned to conclude with Spectra 1.4.0, bringing a dedicated settings system, personalization controls, and user-facing configuration options — completing the foundational structure of the browser.
May 2026 — Upcoming
Modern Browser Necessities
By May 2026, Spectra’s second development phase is planned to focus on features that users naturally expect from a modern browser. The objective of the 2.x series is completeness, usability, and structural maturity.
Spectra 2.0.0 represents the “real browser” leap, introducing major interface and workflow improvements such as a sidebar, enhanced navigation, a bookmarks system, improved tab management, and an optional download manager. This version is intended to elevate Spectra to everyday usability standards.
2.1.0 refines bookmarks and navigation with a dedicated manager, folder organization, and potential import/export capabilities.
2.2.0 explores an extensions or plugin system, establishing a framework for modular features if technically feasible.
2.3.0 emphasizes productivity and UX enhancements, including improved sidebar tools, quicker interactions, and interface refinements.
Overall, the 2.x cycle is aimed at making Spectra feel complete, ergonomic, and aligned with modern browsing expectations.
Upcoming
Intelligence and AI era
The Spectra 3.x series represents a conceptual shift from a traditional browser to an intelligence-driven environment. In this phase, AI is planned to become a native part of the browsing experience rather than an added feature.
Spectra 3.0.0 is designed as the primary milestone, introducing deeper AI integration, contextual assistance, and workflows where the browser can actively help interpret and process information.
3.1.0 focuses on enhanced AI features and smarter interactions, while 3.2.0 explores context-aware behavior and session understanding.
3.3.0 is intended to strengthen the productivity layer, enabling users to analyze, transform, and work with content more efficiently.
Overall, the 3.x cycle centers on intelligence, adaptability, and redefining how users interact with the web.
Upcoming
Identity and Multi-Profile era
The 4.x series will focus on making Spectra truly user-centric. The goal is to support multiple identities, giving each user their own profile, history, and settings while keeping everything secure and personalized.
Spectra 4.0.0 will introduce a multi-profile architecture, enabling profile switching, session isolation, and profile-specific histories and configurations.
Later updates are planned to expand profile personalization with avatars, preferences, and possibly themes (4.1.0), strengthen security and data protection (4.2.0), and add cloud backup and sync functionality for seamless continuity across devices (4.3.0).
Overall, the 4.x cycle emphasizes ownership, identity, and continuity, ensuring Spectra adapts to each user individually.
