How ayushrajak19/scan-mobi works
ReviewFlow lets vendors configure a branded review destination and share it via QR/NFC. Customers scan or tap, choose a rating and describe their experience, receive an editable draft, then submit their own review through Google. The server also handles vendor accounts, dashboard settings, scan/draft counts, QR generation, and persistent SQLite data. The excerpts show server-side routes and database operations; the customer UI implementation was not sampled, so UI relationships reflect README-documented behavior.
Main entry points: app.js Web interface · server.js Draft generation · index.html Branded review page
Components 14
Vendor management
- Vendor accounts
server.js - Vendor settings
public/assets/app.js - QR and NFC
server.js
Customer review flow
- Web interface
public/assets/app.js - Branded review page
public/index.html - Experience input
public/assets/app.js - Google submission
public/assets/app.js
Application server
- Draft generation
server.js - HTTP routes
server.js - Application data
server.js
External services
- Groq API
- Google reviews
Other components
- Vendor
- Customer
Connections 12
- Vendor → Web interface: uses dashboard
README.md - Web interface → Vendor accounts: creates account
README.md - Web interface → Vendor settings: configures business
README.md - Vendor settings → QR and NFC: gets QR
README.md - Customer → Branded review page: scans or taps
README.md - Branded review page → Experience input: collects rating
README.md - Experience input → Draft generation: requests draft
README.md - Draft generation → Groq API: generates draft
README.md - Experience input → Google submission: reviews draft
README.md - Google submission → Google reviews: opens review form
README.md - HTTP routes → Application data: reads and writes
server.js - HTTP routes → Draft generation: routes draft requests
server.js