How I Built a 50% Cold Archival Engine to Keep SaaS Databases Under 500 MB
How I built a chronological 50% cold storage engine using Google Sheets to keep multi-tenant SaaS Postgres databases lean, fast, and 100% free.
Read Full Article →Behind-the-scenes engineering write-ups, experiments, and technical deep-dives into mobile architectures, PWAs, full-stack Next.js systems, and hardware workarounds.
Building native-feeling experiences in the browser with Flutter Web, touch gesture tuning, local IndexedDB caching, and offline-first service workers.
High-performance Next.js App Router applications, Cloudflare edge functions, Supabase relational stores, and low-latency API orchestrations.
Interfacing directly with mobile cameras, WebRTC hardware streams, payment protocol translators, and debugging low-level device driver quirks.
Custom Shopify Liquid theme optimization, headless storefront integrations, checkout conversion speed, and structured inventory sync.
How I built a chronological 50% cold storage engine using Google Sheets to keep multi-tenant SaaS Postgres databases lean, fast, and 100% free.
Read Full Article →How a quick hack to bypass a broken iPhone camera module led to a deep dive into WebRTC hardware constraints—and an accidental fix for the root issue.
Read Full Article →Finding what to watch shouldn't take forever. How I built ViewPick, a swipe-based movie discovery PWA with Flutter Web, Supabase, and TMDB API.
Read Full Article →Perceived performance always trumps server round-trip latency. By rendering state changes immediately on the client and resolving sync asynchronously in the background, web applications feel as responsive as compiled native software.
What manifests as a black screen or unresponsive hardware sensor is frequently a frozen low-level software driver. Direct, constraint-level WebRTC queries can trigger system-level reinitializations that revive stalled modules without physical repairs.
Consolidating mobile and web experiences onto unified architectures (like Flutter Web and responsive Next.js) eliminates duplicated feature work, speeds up client releases, and dramatically simplifies ongoing maintenance.