Back to selected workFinished · Deployable

FeedbackFlow

A local-first product that turns QR codes into secure, actionable and bilingual feedback journeys.

Next.jsTypeScriptSQLiteDockerOAuthPlaywright
Feedback overview4.8
94%
4.8 / 5
Public experienceBilingual forms connected to QR
OperationsLocal SQLite, Docker and documented backups
ControlRoles, secure sessions and request limits
QualityUnit, integration and end-to-end tests

Product overview

From a physical interaction to an informed decision.

FeedbackFlow links a feedback request to a product, service or interaction. Reviewers respond without creating an account; the organization manages forms, alerts, cases and insights from a private dashboard.

The problem I chose to solve

Feedback is only useful when it reaches the right person with context.

Many feedback flows lose context, ask too much of the reviewer or produce data nobody can follow through. The product was shaped to reduce reviewer friction and increase operational clarity for the organization.

System flow

System flow

01Secure QR
02Public form
03Validation
04Local data
05Alerts & dashboard

Engineering decisions

Engineering decisions

Local-first by design
SQLite, local secrets and a persistent volume keep operations simple, portable and controlled by the organization.
Security at the public edge
HMAC tokens, stored hashes, HttpOnly cookies, scrypt, validation and rate limiting reduce the abuse surface.
Operable in the real world
Automatic migrations, access recovery, backup, restore, email OAuth and Docker documentation are part of the product.
Bilingual from the foundation
Portuguese and English are complete journeys rather than a translation layer added at the end.

Ownership & process

AI-assisted engineering with explicit human decisions.

I used AI to accelerate research, implementation and verification. Problem framing, requirements, product decisions, security trade-offs and final acceptance remained my responsibility.

What this project demonstrates

  • Product thinking applied to an operational problem
  • Authentication, permissions and secure public-flow design
  • The ability to connect application, data, email, deployment and support
  • Testing and documentation discipline oriented around operations