DMITRY MELNIKOV
Project 01 · Personal

4th Circle IMS

Unified collection management. Your entire library, everywhere.

Year2026
StatusIn progress
Stack
TypeScript · React · Electron
Backend
SQLite · Google Drive API
Protocols
IPC · REST · HTTP (Web Companion)
One-liner
Keep track of your stuff.
Fig. 01

Dashboard view, light/dark

Overview 01

Total control. A hybrid system that balances the performance of a desktop app with the accessibility of the web.

4th Circle IMS (Inventory Management System) was designed to solve the “siloed data” problem common in local inventory tools. It provides a powerful Electron-based desktop application for data entry and asset management, paired with a lightweight companion web app for mobile viewing.

The system handles diverse entity types — from physical books and vinyl records to digital documents and media files — providing automatic metadata extraction and preview generation.

By utilizing SQLite as the primary storage engine and Google Drive as the synchronization layer, the system ensures data remains private and local while still being accessible across devices.

Timeline Q1 · 2026 Scope Architecture
Desktop Engineering
Cloud Synchronization
Web Infrastructure Scale Desktop + Web
Unlimited Items

Architecture 02

A hybrid core with a unified data model.

4th Circle IMS architecture diagram showing Electron, SQLite, Google Drive, and React Companion Web
Fig. 02 — System Topology · Local Electron desktop workstation with Google Drive sync to Companion Web
Decisions 03

Bridging local and cloud.

/01
SQLite-first persistence

I chose SQLite for its zero-configuration nature and extreme reliability. By storing the database file directly in the user’s library folder, it is ensured that backups and sync are as simple as moving a single file.

Tradeoff · local file management, extreme reliability, multi-user challengies
/02
IPC Security layer

Safety in Electron is paramount. A strict IPC bridge uses runtime validation (via Zod) to ensure the renderer process can only perform authorized filesystem and database operations.

Tradeoff · boilerplate, total isolation
/03
Companion Web (Read-only)

The companion app was intentionally built as a read-only viewer. This allowed to simplify the web architecture significantly, using a simple React frontend that pulls the latest database snapshot from Google Drive.

Tradeoff · limited features, high portability
/04
Binary utility integration

For asset processing (image resizing, video previews), application leverage system binaries like FFmpeg and ImageMagick. This provides near-native performance that would be impossible to achieve with pure JS implementations.

Tradeoff · host dependency, high performance

The purpose of database is not only to store data, but reliably retrieve it

Outcome 05

The library of everything.

4th Circle IMS successfully demonstrates that you don’t need a complex SaaS backend to build a multi-device application. The hybrid architecture provides the speed and privacy of local software with the convenience of a modern web experience.

Impact Zero-latency local work
Mobile library access Cost 3 weeks · Solo build

Fig. 02

Desktop app showing a collection of e-books and articles.

Fig. 03

Documents section with scanned docs, grouped

Fig. 04

Collection of music with ability to play