How infoadcraftstudio-hub/munshi-app works
Munshi is a shopkeeper’s digital credit-ledger PWA. The main workflow is recording customer credit or payments, then viewing balances and sending reminders; supplier accounts, sales/profit, offline use, and AI tools are separate capabilities. The README documents these features and the stack, but the tree contains no application JavaScript or migrations, so implementation-level wiring cannot be verified. Feature paths use the existing index.html; AI logic is documented as a dashboard-managed Edge Function.
Main entry points: index.html Munshi app · sw.js Service worker · manifest.json PWA manifest
Components 18
Ledger
- Munshi app
index.html - Customer accounts
index.html - Credit and payments
index.html - Customer balances
index.html - Supplier accounts
index.html - Supplier transactions
index.html
Shop Operations
- Sales and profit
index.html - Trash and restore
index.html - Payment reminders
index.html - AI queries and receipts
App Platform
- Offline data
index.html - Offline sync
index.html - Service worker
sw.js - PWA manifest
manifest.json
External Services
- Supabase
- Google Sign-In
Other components
- Shopkeeper
Connections 19
- Shopkeeper → Munshi app: uses
- Munshi app → Customer accounts: manages
- Munshi app → Credit and payments: records
- Credit and payments → Customer balances: updates
- Munshi app → Supplier accounts: manages
- Munshi app → Supplier transactions: records
- Munshi app → Sales and profit: shows
- Munshi app → Trash and restore: restores
- Munshi app → Payment reminders: sends
- Payment reminders → WhatsApp: delivers via
- Munshi app → AI queries and receipts: requests
- AI queries and receipts → Supabase: runs as function
- Munshi app → Offline data: stores offline
- Offline sync → Offline data: syncs
- Offline sync → Supabase: syncs to
- Munshi app → Offline sync: uses
- Munshi app → Supabase: reads and writes
- Munshi app → Google Sign-In: authenticates with
- Service worker → PWA manifest: caches