@Ankit

🚀 Devlog #6: Reworking the First Impression

“The first thing users see is the boot screen and login screen.”

After testing ARESOS and reviewing feedback, I spent time improving the startup experience of the operating system.

One major issue was that some parts of the interface felt too similar to common AI-generated dashboard designs. The goal was to move toward a cleaner and more believable operating system experience.

Changes made:

• Redesigned the ARESOS boot screen
• Created a custom animated ARES logo
• Improved boot sequence and startup flow
• Simplified boot messages and visual hierarchy
• Redesigned the login screen layout
• Improved typography, spacing, and consistency
• Removed unnecessary futuristic UI elements
• Strengthened the overall ARESOS visual identity

One challenge was getting the logo animation right. Early versions looked incomplete during startup and made the logo difficult to recognize. Several iterations were needed before the animation felt natural and readable.

The login screen also went through multiple revisions to balance branding and usability. The final design keeps the logo as the primary focus while making authentication simple and distraction-free.

This update doesn’t add new functionality, but it significantly improves the first impression and overall experience of using ARESOS.

🚀 Devlog #5: Terminal, Archives, and the v2.0 Release

As development continued, I spent most of my time improving the terminal experience.

ARESOS now supports command chaining, pipes, redirection, aliases, environment variables, command history expansion, and a growing collection of filesystem utilities.

I also added ZIP archive support. Files can be archived, extracted, and restored directly from the virtual filesystem through terminal commands.

One of the goals for this release was making the terminal feel more useful rather than simply displaying simulated output. A lot of time went into testing command interactions, filesystem behavior, and archive handling.

With the shell, filesystem, desktop environment, and documentation now in place, ARESOS v2.0 is ready for its first public release.

🚀 Devlog #4: Building the Mission Control Workspace

“An operating system becomes useful when everything works together.”

After building the core desktop environment, I focused on creating a workspace designed specifically for productivity and organization.

ARESOS now includes a collection of integrated tools including Calendar, Todo Manager, Settings, Notification Center, Focus Session controls, and system management panels.

Instead of forcing users to switch between multiple websites and browser tabs, the goal was to create a centralized mission-control experience where scheduling, task tracking, configuration, and daily planning happen inside a single environment.

This was the point where ARESOS stopped feeling like a collection of windows and started feeling like a complete productivity operating system.

“A web operating system needs files.”

Content

ARESOS includes a custom Virtual File System inspired by Unix-like directory structures.

The filesystem is stored entirely inside the browser using localStorage and supports:

Directories
Files
Creation
Deletion
Navigation
Persistent storage

The most interesting part is that Terminal and File Explorer both interact with the same underlying filesystem state.

Creating a folder through Terminal instantly appears inside File Explorer without refreshing the page.

“Window drag and resize in React is easy. Making it feel like a real OS is not.”

Content

One of the biggest challenges was creating a desktop environment that behaves like a real operating system.

ARESOS supports:

Draggable windows
Resizable windows
Minimize animations
Maximize mode
Focus management
Dynamic z-index stacking

Initially, dragging felt sluggish because CSS transitions were conflicting with real-time position updates. The solution was temporarily disabling transitions during drag operations and restoring them afterward.

This dramatically improved responsiveness and made window movement feel much smoother.

“An operating system isn’t a collection of apps. It’s the layer that controls them.”

Created OSContext.tsx as the central operating system kernel.
Every window, process, notification, and desktop state flows through a single source of truth.
Implemented process spawning, window registration, focus management, and desktop state persistence.
Separated OS logic from application logic to keep the architecture modular.
This became the foundation that every other subsystem relies on.

ARES Devlog — Virtual Mother Rover Online

Today I completed the first end-to-end rover pipeline.

Completed:

✅ Backend Ground Server
✅ WebSocket Communication
✅ Frontend Integration
✅ Virtual Mother Rover Simulator
✅ Mission Control Integration
✅ Live Map Integration
✅ Telemetry Integration

The dashboard is now receiving live rover state packets from a simulated Mother Rover.

Current metrics streamed:

• Battery
• Signal Strength
• Temperature
• Speed
• Heading
• Coordinates

Current Architecture:

Virtual Mother Rover
↓
FleetPacket
↓
Backend
↓
WebSocket
↓
Mission Control
Live Map
Telemetry

Next Step:

Create a hardware-compatible Mother Rover Adapter so a real ESP32 rover can replace the simulator without changing frontend code.