Jumping Park

Verified: Jumping Park is a kiosk-first consent platform built with Next.js and Firebase.

Verified: The product supports document lookup, registration, email OTP, consent review, accompanying-minor records, signature capture, a success flow, and administrative operations.

Partial: I contributed to authentication and OTP hardening, production hardening, offline and idempotency work, CI and quality gates, accessibility, SEO and the public surface, operational documentation, and ongoing maintenance. This is subject to contributor and company confirmation of shared boundaries.

Partial: Alex Franco contributed to the initial server and Firebase foundation, early administration, minor-management UX, role and access work, and early data or cost optimization, subject to Alex’s confirmation of the final wording.

Verified: The operational flow runs through document lookup, registration, email OTP, consent review, accompanying-minor records, signature capture, a success flow, and administrative operations.

Partial: The flow is described from the implementation and code structure; a point-in-time deployment observation does not prove uptime, availability, or defect-free operation.

Verified: The product chose Next.js and Firebase as its technical foundation for the consent workflow.

Partial: I was responsible for later authentication and OTP hardening, production hardening, and offline or idempotency behavior, behind rollout flags — this is implementation scope, not a claim that the product is secure or compliant.

Verified: The codebase contains explicit reliability and quality mechanisms, including rollout-gated offline or idempotency code and selected Playwright or Axe smoke coverage.

Partial: These are implementation facts, not proof of complete production behavior or conformance. Security and privacy follow-ups remain separate maintenance work.

Verified: Repository CI and quality automation includes quality, dependency-audit, and build checks with selected Playwright and Axe smoke coverage.

Blocked: Complete offline operation, legal validity of consent, compliance, uptime, and production-security maturity were not verified and are not claimed.

Verified: Selected Playwright and Axe smoke coverage exists in the repository as implementation facts.

Partial: Full test totals, Lighthouse scores, WCAG conformance, and performance results require dated reproducible reports and are not claimed here.

Blocked: Company permission for product identity, links, screenshots, and approved technical details is required before any client-identifying artifact is published.

Blocked: Exact contribution percentages and non-commit responsibility boundaries remain internal until both contributors confirm them.

Blocked: Security remediation status must be owned and reviewed before any security or compliance claim.

Verified: This case study is product-anonymous: the project name appears, but no company name or public product URL is disclosed.

Partial: Media artifacts are synthetic placeholders pending company approval of anonymized screenshots or recordings.