惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

雷峰网
雷峰网
博客园 - 聂微东
酷 壳 – CoolShell
酷 壳 – CoolShell
宝玉的分享
宝玉的分享
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
罗磊的独立博客
Hugging Face - Blog
Hugging Face - Blog
T
Tailwind CSS Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
IT之家
IT之家
博客园_首页
博客园 - 三生石上(FineUI控件)
博客园 - 叶小钗
Apple Machine Learning Research
Apple Machine Learning Research
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
量子位
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
人人都是产品经理
人人都是产品经理
美团技术团队
小众软件
小众软件
Jina AI
Jina AI
S
SegmentFault 最新的问题
博客园 - Franky
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Building a "Local-First" Expense Tracker with zero server...
SM Shahbaj · 2026-04-24 · via DEV Community
Cover image for Building a "Local-First" Expense Tracker with zero server costs

SM Shahbaj

As developers, we tend to follow a common practice: frontend + api + database. Yet, when I decided to develop the Sheet Manager application, I wanted to break this paradigm. I wanted to create an application which is 100% private, offline, and completely zero-cost.

And Local-First architecture helped me achieve that.

The Architecture

There is no reason why your sensitive financial data should be stored on some PostgreSQL or MongoDB instance somewhere on the cloud. Instead, all of it is stored in the user's browser.

Persistence: I implemented a wrapper for IndexedDB which allows us to handle very large sets of structured data (in comparison to LocalStorage). Plus, unlike LocalStorage, it does not block the main thread.

Performance: Being client-side only makes our UI super responsive since there are no API calls and the latency becomes simply the execution of JavaScript code.

Privacy: This is the main advantage of local-first applications. I literally have no way of accessing the data users enter since it's being stored on their own computers. For a finance application, that's an incredible feature.

The "Zero-Cost" Infrastructure

Can we make a production-ready application without any bills whatsoever?

Hosting: Using Cloudflare Pages and GitHub Pages as the frontend hosting services.
Database: Free (It's inside the user's browser).
Analytics: Keeping analytics light and simple to stay away from trackers.

Challenges of Local-First Development

This was not as easy as it sounds. Developing without backend adds its challenges:
Data portability: In case the user clears browser storage, how can we provide him/her with the option to import/export data? Implemented a JSON/CSV export/import system.
Sync across multiple devices: This is something I want to tackle soon by using WebRTC or Peer-to-Peer synchronization technologies._

Why did I develop this?

In addition to being a software engineer, I'm also very privacy-conscious (I don't even use Facebook and Twitter). We over-engineered the idea of "the cloud" into every tiny utility. Sheet Manager became a proof that we don't necessarily need servers to develop beautiful dashboard-based applications.

Take a look at the project yourself: Sheet Manager

What do you think about the idea of local-first development? How are you handling data persistence nowadays?