🔷 [Epic] Near Event Ticketing UX

[charleslavon]

• High Level Goal:

Create a UX leveraging Near technologies ( Accounts, KeyPom, Wallet-selector, NFTs, etc) to issue tickets for in-person event series, aiming to solve 4 issues with existing ticketing platforms:

1. they are cost prohibitive (especially for larger events)
2. they maintain custody of the proceeds from ticket sales and delay paying event producers until a week after an event occurs
3. they lack of feature parity across mobile platforms
4. They do not provide a simple way to deploy a white labeled ticketing platform personalized to an event producer’s brand.

User Stories & Product Hypothesis
Keypom's implementation

---

MVP Goals

• Demonstrate use cases which solve real world problems, where we can get at least 10s of users to participate in user interviews during development and MVP usage during a Beta Release
• Build the MVP along with a well-documented boilerplate template that would enable developers to quickly launch and customize their own ticketing system. or cross-chain asset management tool that already has the wallet, mpc contract, and user onboarding flows implemented.
• Deliver an MVP for Alpha (internal) usage testing within 6-weeks
• Deliver a release to Beta users within 2-weeks post Alpha

Potential Goals Beyond the MVP

• Showcase Chain Abstraction via Cross Chain management of NFTs or FTs with v2.multichain-mpc.testnet, wallet-selector, and keypom’s event & ticketing flows.

This epic includes two deliverables.

1. A minimally branded, mobile-optimized consumer app that enables event producers to create events and setup tickets; with a corresponding UI that is user focused that enables ticket purchasing and scanning to validate a ticket..
2. A Boilerplate template application, similar to this Loyalty Program Template, that allows developers to quickly customize and deploy their own event ticketing program.

Things we'll want

1. 90% coverage by unit tests for each functional flow
2. Devs/Docs people who were not involved in building this to test through the flows once as an event creator, and again as users purchasing tickets and access an event.
3. When the UX is minimally functional end-to-end, get initial feedback from potential Beta users.
4. A link to the status of the Pagoda managed services that support this UX ( e.g. API Proxies for stripe and IPFS, etc)
5. Review with Dustin for a perspective on monetizing the Pagoda managed services and determine potential pricing tiers
6. A security review on the overall UX
7. Document what changes would be needed to ensure that tickets can be scanned while network connectivity is problematic
8. Document the expected limits on scalability (e.g. tickets purchased per min, tickets validated per min, etc)
9. Monitoring & Alerting for key performance indicators
10. Document deployment processes for the app and all supporting services
11. Document where & how nonces are used, and how they might cause failures.
12. Create a blog for docs.near.org (perhaps on the process of building this app and guidance for developers on how to use the template)
13. Create a marketing blurb for twitter and nearweeknews
14. Additional promotion (DevHub's weekly meeting?)

Success Metrics

Weekly

1. Support Ticket Volume: Monitor the number and nature of support tickets raised. A decrease in monthly support tickets can indicate an improvement in user experience and overall UX.

Monthly

1. A month-over-month increase in the number of NFT transactions from Events as a percentage of total NFT transactions on Near.
2. A month-over-month increase in the # of clones of the boilerplate template app
3. A month-over-month increase in the claims of proof-of-attendance NFTs which become accessible to users after their tickets are scanned at the event.
4. Positive feedback on the overall event producer experience and impact on their profitability from event producers.
5. Positive feedback on the overall user experience and ticket pricing from attendees.

Quarterly

1. A quarter-over-quarter increase in Repeat Attendee Rate: Measure the proportion of attendees who return for subsequent events in a given series. This can help gauge the loyalty and satisfaction for a producer’s community.
2. A quarter-over-quarter increase in Producer Onboarding Rate: The rate at which new event producers start using this product. Growth in producer adoption reflects the platform’s value proposition to event organizers.
3. An increase in NFT Ticketing Adoption Rate: For each producer’s event, Track the percentage of tickets issued via this product against the total number of traditional tickets made available on other platforms. An increasing trend can indicate successful platform adoption and acceptance of the overall UX.

Tasks

Beta Give feedback

1. https://github.com/near/pagoda-experiments/issues/1
2. https://github.com/near/pagoda-experiments/issues/2
3. https://github.com/near/pagoda-experiments/issues/3
4. https://github.com/near/pagoda-experiments/issues/4
5. https://github.com/near/pagoda-experiments/issues/5
6. https://github.com/near/pagoda-experiments/issues/6
7. https://github.com/near/pagoda-experiments/issues/7
8. https://github.com/near/pagoda-experiments/issues/8
9. https://github.com/near/pagoda-experiments/issues/9
10. https://github.com/near/pagoda-experiments/issues/10
11. https://github.com/near/pagoda-experiments/issues/11
12. https://github.com/near/pagoda-experiments/issues/12
13. https://github.com/near/pagoda-experiments/issues/13
14. https://github.com/near/pagoda-experiments/issues/14
15. https://github.com/near/pagoda-experiments/issues/15
16. https://github.com/near/pagoda-experiments/issues/17
17. https://github.com/near/pagoda-experiments/issues/20
18. https://github.com/near/pagoda-experiments/issues/18
19. https://github.com/near/pagoda-experiments/issues/16
20. What improvements are needed to faciliate a developer using the ticketing repo as a boilerplate app #1194
    +0
21. Explore using create-near-app as the means to make our template apps available for devs to build upon. #1198
    +0