Building QR Scanner Pro: Batch Workflows and an App Lock

QR apps usually die as camera demos. QR Scanner Pro is built as something you can rebrand and ship: scan and generate across the payloads people actually need, keep history locally, and export without jumping through three other apps.

Beyond the viewfinder

Real-time scanning with camera and gallery. Generation for URLs, contacts, Wi‑Fi, crypto addresses, and free text. Customization with styling, templates, and a designer flow. History, favorites, and detail screens backed by Hive.

That’s table stakes. The product depth is in the ops screens.

Batch and export

Events, inventory stickers, classroom materials, and shop menus need more than one QR at a time.

• Batch generation from structured input
• Batch scanning into history
• CSV import for bulk create
• CSV and PDF export for handoff

ExportService and CSVImportService are boring on purpose. Boring is what agencies and indie publishers pay for when they white-label a utility.

App lock is not optional chrome

Scan history can hold Wi‑Fi passwords, payment addresses, door codes, private URLs. Treating that like a photo gallery is a product bug.

AppLockService supports:

• PIN stored hashed in Hive
• Biometrics via local_auth when available
• Failed-attempt tracking and temporary lockout
• Unlock gating around the sensitive surface

It’s not a full MDM story. It’s the minimum respect for “someone handed me their phone.”

Starter economics

AdMob and Google Play Billing hooks, remote config, analytics, and settings are already wired into launch flow — so the hard part of publishing a utility (monetization plumbing) isn’t a blank page.

Targets include Android and iOS; the repo is structured for broader Flutter targets where the plugins allow.

What I’d still harden

Store listing honesty about which platforms are production-QA’d. Biometric UX differs enough across OEMs that lock flows need device-matrix testing. Batch PDF layout will always need edge-case polish for long payloads.

Bet: utilities win on workflow completeness, not on a prettier reticule.

If you’re shipping a “simple” tool: ship the batch screen and the lock screen, or you’re shipping a demo.