BLOG
Author: Chandraprakash Suthar
Date: 3 December 2025
When I first received access to Amazon’s new development kit, it came with a codename that sounded like it belonged in a sci-fi novel: Kepler.
At the time, it was a secret project. A quiet initiative to reimagine the operating system for the living room. Today, the world knows it as VegaOS, a Linux-based alternative to the Android-based Fire OS that has powered Amazon’s TV devices for years.
For the past 20 months, I have lived and breathed this platform. My journey started with a bare-bones SDK and evolved into developing apps for major streaming providers. This is the story of that transition, the technical hurdles we cleared, and what it really takes to build for the next generation of TV.
I still remember my first boot of the Kepler environment. It was version 0.4, a remarkably young release. To give you an idea of how early we were, the sample app provided wasn’t a media catalogue or a streaming player. It was a single screen with two UI components: a button and a colored background. You clicked the button, and the background changed color.
That was it.
For a senior engineer used to the rich ecosystems of mobile and web, this was jarring. But it was also an invitation. We weren’t just building on a platform; we were essentially growing with it.
The challenge was twofold. First, I had to master developing for the TV form factor – a 10-foot experience where “touch” is replaced by “focus” and navigation is linear rather than free-form. Second, I had to do it on a platform where StackOverflow had zero answers.
When you are working on the bleeding edge, there are no tutorials. Our “experts” were the engineers building the OS itself.
The Amazon Kepler forums became our lifeline. It wasn’t the typical corporate support channel; it was a collaborative trench. The Amazon team was accessible, working alongside us to debug race conditions and rendering quirks. We were reporting issues that would become patch notes in the next SDK release.
This collaboration was vital because VegaOS is not Android. It is a Linux-based OS that treats React Native as a first-class citizen. This architectural shift meant we couldn’t just rely on our old Android-specific hacks. We had to think in pure React Native and native C++ modules.
As the platform matured, so did our ambitions. We moved from changing background colors to porting full-scale OTT applications. This introduced real-world engineering constraints.
Focus Management became our daily obsession. It wasn’t that the platform lacked documentation or safety nets, in fact, Kepler’s native support for FocusManager and TVFocusGuideView proved incredibly helpful. The challenge lay in the paradigm shift.
The focus management model differed significantly from what we were used to on tvOS or Android TV. We had to relearn how to structure our spatial navigation logic to ensure that pressing “Right” on a remote felt just as intuitive and seamless as it does on those mature platforms.
Adaptive Video Playback required a mindset shift. Instead of wrapping native players like ExoPlayer, VegaOS implements W3C web standards directly. This was actually a relief as it allowed us to leverage our existing experience with web players like Shaka Player rather than building raw MSE implementations from scratch.
Since Shaka handles the heavy lifting of adaptive bitrate switching, we could focus simply on optimization. The goal was to ensure this web-architected stack performed indistinguishably from mature Android-based Fire TV apps on resource-constrained hardware. This strategy proved highly effective, delivering reliable performance for both our internal projects and client applications.
One of my proudest contributions during this time came from a gap in the ecosystem. As we approached launch, many organizations realized that the Google Interactive Media Ads (IMA) SDK – the industry standard for monetization was not officially supported on this new Linux-based environment.
You cannot simply drop an Android JAR file into a Linux environment. The ecosystem needed a solution, and my organization, Logituit, was chosen to build it.
I worked as a senior developer on what became a wrapper over Google’s IMA. We had to architect a solution that bridged the gap, by leveraging web technologies inside a webview to render the ad logic while maintaining a seamless native feel for the user. Seeing organizations across the globe adopt this solution has been incredibly motivating.
As the “Kepler” designation began to fade into “Vega,” Amazon pushed for wider adoption. I found myself on stage at workshops and conferences, speaking alongside talented engineers from Callstack, Meta, and Amazon.
It was surreal to teach a technology that I was still discovering myself. But that is the nature of engineering. You don’t wait until you know everything; you share what you know now.
Logituit was also selected for a special program to help other organizations fine-tune their Vega apps. This was my favorite phase. I got to dive into codebases from various companies, helping them migrate their existing React Native TVOS apps to VegaOS.
This wasn’t just copy-pasting code. We had to deeply understand:
After nearly two years, VegaOS has officially launched on the Fire TV Stick 4K Select. Seeing apps run smoothly in production is the best validation for the 20 months of architectural pivots and debugging we put in. It proves React Native is ready for the living room.
I’m proud of the foundation we’ve built, but I’m even more excited about the future this platform enables – maybe a future where a single React Native codebase could seamlessly power production apps across every major TV platform, from Android TV and tvOS to VegaOS, Tizen, and webOS.
I’m always happy to chat about React Native, TV development, or the quirks of VegaOS. Feel free to reach out!
Chandraprakash Suthar is a Senior Software Engineer at Logituit with over five years of experience in the JavaScript and React ecosystem. His expertise includes building scalable web, mobile, and TV applications, along with developing robust SDKs using React, React Native, and Next.js. He is passionate about exploring JavaScript technologies in depth to solve complex problems.
Outside of work, he is an avid photographer, a backpacker, and someone who enjoys teaching.
Also Read:
SHARE THIS ARTICLE
Stay up to date on latest trend in video tech
Related Posts
To provide the best experiences, logituit.com use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behaviour or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
