You are browsing as a guest. Sign up (or log in) to start making projects!

J.A.R.V.I.S.

  • 3 Devlogs
  • 3 Total hours

StarkOS is a client-side, browser-based operating system themed around an Iron Man HUD. It features a custom window manager with draggable, glassmorphic interfaces and a central Arc Reactor clock. The core of the system is the J.A.R.V.I.S. command terminal, which dynamically launches and manages integrated offline apps, including a persistent notes editor, a local-file image gallery with a fullscreen lightbox, and an embedded media player. To make it feel like a native environment rather than a standard webpage, the project also incorporates a simulated terminal boot-up sequence and overrides the browser's default right-click with a custom context menu.

Ship #1 Changes requested

I built StarkOS, a fully functional, browser-based simulated operating system themed around an Iron Man HUD, engineered entirely from scratch without frameworks using vanilla HTML, CSS, and JavaScript. The project features a custom window manager with draggable, glassmorphic interfaces and a J.A.R.V.I.S. command terminal that controls integrated apps like a Schematics analyzer with holographic filters and clickable coordinate pins, as well as a System Logs editor that utilizes JavaScript Blobs to export real text files directly to a user's local drive. Developing this native desktop experience inside a browser presented unique mathematical and UI challenges, particularly calculating smooth window drag coordinates, programming boundary-detection geometry for the custom right-click menu to keep it on-screen, and handling persistent local file generation, but overcoming these technical hurdles as a solo developer is what I am most proud of. To test it out, users simply open the index.html file, grant location access to initialize the OpenWeather API satellite link and personalized city-detecting terminal greeting, type commands like help or open schematics in the mainframe, and test out the interactive UI and file export features.

Try project → See source code →
Open comments for this post

28m 19s logged

Today’s session focused on bridging the gap between the offline sandbox and real-world data. I integrated the HTML5 Geolocation API to ping coordinates upon system boot, feeding that exact latitude and longitude directly into a live OpenWeather API fetch request. This allowed me to project real-time local temperature, meteorological conditions, and the current city directly into the central Arc Reactor HUD overlay. To tie the entire ecosystem together and enhance the immersive J.A.R.V.I.S. experience, I engineered an automated welcome protocol within the terminal mainframe. This sequence triggers instantly upon a successful location lock, outputting a dynamic security clearance message customized for the detected city. The entire OS now feels significantly more alive, perfectly complementing the rock-solid local storage and offline blueprint capabilities established in earlier sprints.

Today’s session focused on bridging the gap between the offline sandbox and real-world data. I integrated the HTML5 Geolocation API to ping coordinates upon system boot, feeding that exact latitude and longitude directly into a live OpenWeather API fetch request. This allowed me to project real-time local temperature, meteorological conditions, and the current city directly into the central Arc Reactor HUD overlay. To tie the entire ecosystem together and enhance the immersive J.A.R.V.I.S. experience, I engineered an automated welcome protocol within the terminal mainframe. This sequence triggers instantly upon a successful location lock, outputting a dynamic security clearance message customized for the detected city. The entire OS now feels significantly more alive, perfectly complementing the rock-solid local storage and offline blueprint capabilities established in earlier sprints.

Replying to @sarveshwaran_k2008

0
Open comments for this post

1h 18m 5s logged

Today’s developmental sprint successfully overhauled the system’s data architecture, transforming temporary network processes into permanent local workflows. In the Schematics layout, I pruned the tactical archives database to focus exclusively on Counter-Strike and Call of Duty: Mobile, transitioning all map arrays from temporary web placeholders to absolute local routing path links for optimized, offline tactical data processing. Concurrently, I upgraded the System Logs engine by engineering a local file-export mechanism utilizing JavaScript Blobs and modifying the window interface with a direct action button, enabling users to physically save and download encrypted text data directly to a local drive as a standardized document to secure data persistence beyond temporary browser memory cache.Yet to add the feature to track weather.

Today’s developmental sprint successfully overhauled the system’s data architecture, transforming temporary network processes into permanent local workflows. In the Schematics layout, I pruned the tactical archives database to focus exclusively on Counter-Strike and Call of Duty: Mobile, transitioning all map arrays from temporary web placeholders to absolute local routing path links for optimized, offline tactical data processing. Concurrently, I upgraded the System Logs engine by engineering a local file-export mechanism utilizing JavaScript Blobs and modifying the window interface with a direct action button, enabling users to physically save and download encrypted text data directly to a local drive as a standardized document to secure data persistence beyond temporary browser memory cache.Yet to add the feature to track weather.

Replying to @sarveshwaran_k2008

0
Open comments for this post

1h 35m 29s logged

Just pushed StarkOS v4.0. The whole thing is really coming together as a fully functional, client-side web OS. I built out a central Arc Reactor HUD clock and solid glassmorphic windows with a reliable drag-and-drop system. The J.A.R.V.I.S. terminal is the core router now—typing commands actually launches apps like a persistent local-storage notes app, a media player with a permissive YouTube embed, and a schematics gallery that reads local files and opens them in a custom lightbox modal. I also added some native OS feel by writing a terminal boot-up sequence on page load and overriding the browser’s default right-click with a custom Stark-themed context menu. It’s stable, the UI is locked in, and it actually feels like a real desktop environment now. Next up, I might build a calculator or wire in a live weather API.

Just pushed StarkOS v4.0. The whole thing is really coming together as a fully functional, client-side web OS. I built out a central Arc Reactor HUD clock and solid glassmorphic windows with a reliable drag-and-drop system. The J.A.R.V.I.S. terminal is the core router now—typing commands actually launches apps like a persistent local-storage notes app, a media player with a permissive YouTube embed, and a schematics gallery that reads local files and opens them in a custom lightbox modal. I also added some native OS feel by writing a terminal boot-up sequence on page load and overriding the browser’s default right-click with a custom Stark-themed context menu. It’s stable, the UI is locked in, and it actually feels like a real desktop environment now. Next up, I might build a calculator or wire in a live weather API.

Replying to @sarveshwaran_k2008

0

Followers

Loading…