BuidlZone-Labs/zicket-web

Implement the Post-purchase experience

Open

#166 opened on Jul 23, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (43 forks)auto 404
GrantFox OSSMaybe RewardedOfficial Campaign | FWC26difficulty: hardenhancementfrontendhelp wanted

Repository metrics

Stars
 (4 stars)
PR merge metrics
 (PR metrics pending)

Description

Description

Develop the post-purchase experience, including ticket viewing, sharing, and usage. This design was completed with issue #92

Design Reference

https://www.figma.com/design/o9EayHeZkGOxzeCLd80WPW/Zicket-%F0%9F%8E%AB--Copy-?node-id=4413-11232&t=GfzTR6hw2x7C9yvb-4

QR code component already exists.

Required Screens

  • View history
  • View ticket detail
  • “Proof without identity” explanation(Private sharing)
  • Expiry / event-time UX

Acceptance Criteria

  • Tickets are easy to use
  • Privacy preserved in sharing
  • Clear event-day flow
  • desktop mode should be available
  • Consistent app theme

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.