{"slug": "migrating-fintally-from-react-to-slint-ui-achieving-a-100mb-native-memory", "title": "Migrating FinTally from React to Slint UI: Achieving a 100MB Native Memory Footprint", "summary": "The developer behind FinTally, a local-first personal finance platform written in Rust, migrated the app's frontend from React.js to Slint UI across its Auth, Budgets and Transactions screens, bringing the interface to a sub-120MB system RAM footprint. On a 6GB-VRAM test machine, active local LLM calls used 3.4GB VRAM and 500-600MB RAM, dropping to 100-120MB system RAM when idle. The developer says the native compilation path also opens the door to ARM mobile builds once the full route tree is migrated.", "body_md": "# Migrating FinTally from React to Slint UI: Achieving a 100MB Native Memory Footprint\n\nIn local-first software architecture, system resources are non-negotiable. Web wrappers and heavy web engines tax system RAM before a single line of business logic executes.\n\nTo solve this, **FinTally** has officially completed its core frontend migration from **React.js to Slint UI** across three critical system endpoints:\n\n1. **Auth**\n2. **Budgets**\n3. **Transactions**\n\nBy moving to statically compiled native UI bindings, the entire application interface now executes inside a sub-120MB memory envelope.\n\n## \n\nOur testing baseline on a 6GB VRAM system yielded exceptional execution-on-demand specs. The table below outlines how local inference and idle execution scale across hardware tiers:\n\n| Hardware Tier | Active AI / LLM Call Load | Idle / Post-Inference State | \n|---|---|---|\n| **High-End GPUs***(e.g., RTX 5090 / 20GB VRAM Class)* | ~5 GB VRAM | ~100 MB System RAM *(Runs silently 24/7)* | \n| **Mid-Range GPUs***(6GB VRAM Baseline Test System)* | 3.4 GB VRAM & 500 MB – 600 MB RAM | 100 MB – 120 MB System RAM | \n| **Entry-Level GPUs***(4GB VRAM Class)* | ~2 GB VRAM | Sub-120 MB System RAM | \n\n## \n\nBecause Slint UI compiles down to native machine instructions rather than relying on dynamic web interpreters, these low-footprint optimizations apply universally:\n\n- **Mobile Compilation:** Light enough to execute natively on ARM mobile hardware once the entire route tree migration completes.\n- **Desktop & WebAssembly (WASM):** Shared memory models guarantee high-throughput responsiveness regardless of execution target.\n\n### \n\nWe are actively working on pushing memory usage down even further, establishing a low-latency execution pipeline that seamlessly bridges local privacy-first inference with fallback cloud reliability.\n\n*Follow the live engineering discussions on* *Twitter/X**and* *LinkedIn**.*\n\n## About the author\n\n- Systems Engineer focused on low-latency architectures, bare-metal C/C++ FFI, and production Rust backends. I specialize in eliminating runtime bottlenecks at the C-ABI boundary—building high-throughput polyglot extensions (PyO3, FFI) and zero-copy memory pipelines for AI/ML inference and SaaS infrastructure. Core Stack: Rust (Axum, Candle, SQLx), C++17/23, C23, PyO3, PostgreSQL, MinIO. Proof of Work: Creator of FinTally—a pure Rust finance platform evolved from legacy Node.js/Django to FastAPI + PyO3, and ultimately rewritten into a full-stack Rust architecture powered by bare-metal C/C++ native engines via extern \"C\" FFI.\n\n## Comments\n\n[Join the discussion](https://hashnode.com/posts/migrating-fintally-from-react-to-slint-ui-achieving-a-100mb-native-memory-footprint/6ae822857cfb115319e58df6)\n\nNo comments yet. [Be the first to comment.](https://hashnode.com/posts/migrating-fintally-from-react-to-slint-ui-achieving-a-100mb-native-memory-footprint/6ae822857cfb115319e58df6)", "url": "https://wpnews.pro/news/migrating-fintally-from-react-to-slint-ui-achieving-a-100mb-native-memory", "canonical_source": "https://anshugondi.hashnode.dev/migrating-fintally-from-react-to-slint-ui-achieving-a-100mb-native-memory-footprint", "published_at": "2026-11-02 05:41:25+00:00", "updated_at": "2026-11-21 06:14:12.169632+00:00", "lang": "en", "topics": ["developer-tools", "ai-infrastructure", "large-language-models"], "entities": ["FinTally", "Slint UI", "React.js", "Rust", "WebAssembly"], "also_reported_by": [], "takeaway": "Replacing a React web frontend with statically compiled Slint UI cut FinTally's idle system RAM to 100-120MB, while local LLM inference on a 6GB-VRAM machine used 3.4GB VRAM and 500-600MB RAM.", "recommendation": {"advice": "For local-first apps that run on-device LLMs, compile the UI natively with a toolkit like Slint instead of shipping a web engine, then budget VRAM and RAM separately for active inference versus idle states.", "playbook": "inference-serving", "playbook_url": "https://wpnews.pro/playbooks/inference-serving"}, "alternates": {"html": "https://wpnews.pro/news/migrating-fintally-from-react-to-slint-ui-achieving-a-100mb-native-memory", "markdown": "https://wpnews.pro/news/migrating-fintally-from-react-to-slint-ui-achieving-a-100mb-native-memory.md", "text": "https://wpnews.pro/news/migrating-fintally-from-react-to-slint-ui-achieving-a-100mb-native-memory.txt", "jsonld": "https://wpnews.pro/news/migrating-fintally-from-react-to-slint-ui-achieving-a-100mb-native-memory.jsonld"}}