El Billing
Cross-platform billing software deployed across 15+ commercial clients in Nepal
A cross-platform billing application with web, desktop and mobile experiences featuring an offline-capable desktop setup tailored for regional merchant reliability.
1. Context & The Core Problem
Retail and commercial operations in Nepal require reliable, uninterrupted billing workflows even through unpredictable network connectivity and across diverse hardware terminals.
2. Engineering Solution & Implementation
Engineered a cohesive cross-platform suite utilizing a robust Laravel & MySQL core backend, responsive React web interface, Flutter mobile app, and a lightweight Tauri 2 desktop client powered by local SQLite storage for offline durability.
Direct Contributions & Ownership
- Architected and implemented the entire multi-client billing platform from database design to client applications.
- Designed local storage schemas using SQLite within Tauri 2 to allow uninterrupted sales processing when offline.
- Built normalized relational database models in MySQL and performant REST APIs in Laravel for synchronised transactions.
- Developed responsive web interfaces with React and companion mobile capabilities using Flutter.
3. System Architecture & Boundaries
System Architecture
Sanitised conceptual schematic representing components and integration boundaries
Tauri 2 Desktop (SQLite)
Runs offline-first sales terminal locally
React Web App
Admin management, reporting and configuration
Flutter Mobile
Field billing and rapid receipts
Laravel REST API
Central business logic, auth and validation
MySQL Cloud DB
Central relational storage of clients and transactions
Data Flow & Interactions
4. Outcomes & Verified Impact
Adopted by 15+ commercial clients across Nepal for daily billing transactions.
Cross-platform consistency enabled staff to operate across Windows/Mac desktop terminals and mobile devices.
5. Key Challenges & Architectural Lessons
Engineering Challenges
- •Ensuring schema consistency and transactional reliability between SQLite (desktop local) and MySQL (central cloud).
- •Minimizing resource footprint on legacy desktop machines by choosing Tauri 2 over heavy Electron alternatives.
Takeaways & Reflection
- •Choosing Tauri 2 over Electron drastically reduced bundle sizes and RAM overhead on client desktop hardware.
- •Designing with offline resilience in mind from day one prevents costly retrofitting of local storage abstractions.