Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

January 16, 2024

New UI/UX to support pagination / load more history to remove limit of 50 tickets from Transfer History

Understanding the importance of seamless access to transfers history, that is now more visible than ever before with the new Transfers Center, we have introduced a new UI/UX enhancement that supports pagination and 'load more' functionality. This update effectively removes the previous historical limit of displaying only 50 tickets in the Transfer History section.

Transfer History will load 20 past transactions per call, providing a balance between quick access and system performance. This new pagination feature ensures that spectators can navigate through their transaction history smoothly without overwhelming system performance.

How does it reflect in the mobile app ?

Crowdin labels : load_more, load_more_button


Enhanced Email Domain Validation

Since the initial release of our email verification system, we've identified a critical gap in our domain validation process. Key country-based domains such as 'yahoo.de' and 'outlook.fr' were inadvertently omitted. This oversight led to valid email domains being mistakenly flagged as incorrect, resulting in user frustration and inconvenience.

To rectify this, we have significantly expanded our list of recognized email domains. This extensive update is meticulously designed to cover the vast majority of email domains used globally. By implementing this broader domain validation, we expect a substantial decrease in validation errors, directly benefiting all organizers and spectators by ensuring a more inclusive and error-free experience.

December 13, 2023

Initiate transfer from the Transfers Center

Previously, spectators looking to transfer tickets had to navigate through multiple steps: selecting an event, choosing a ticket, and then initiating the transfer, a process that became cumbersome when transferring multiple tickets. This flow was not ideal for those wishing to transfer several tickets at once.

We've streamlined ticket transfer process by introducing a direct transfer accessible from the Transfer tab in the bottom menu. This allows for a quicker and more efficient way to initiate ticket transfers, especially when dealing with multiple tickets.


Lowering the number of notifications received when a ticket is transferred without Accept/Reject enabled

In the past, transfer recipient experienced duplicate notifications for a single ticket transfer when the Accept/Reject feature was deactivated. This often led to confusion, as spectators were mistakenly led to believe they had received multiple tickets or the same ticket repeatedly.

To enhance clarity and user experience, we've make sure that now, when the Accept/Reject feature is disabled, during a ticket transfer, the recipient will only receive a single notification. This change is aimed at eliminating any confusion and ensuring a clear understanding of the ticket transfer process.

How does it reflect in the mobile app ?

  • When accept/reject is disabled, the recipient will receive only one notification for the received tickets (implicit acceptance)
  • When accept/reject is enabled, the recipient will receive two notifications:
    1. One notification for the incoming tickets (before approval)
    2. One notification for the received tickets (after approval - explicit acceptance)
  • When a transfer is rejected by the recipient, the sender will receive one notification for the tickets returned to him.
  • No labels