...

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.

Image Modified

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

...

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 accept/reject is disableda transfer is rejected by the recipient, the recipient sender will receive :
  • One notification for received tickets
  When a transfer is rejected, the sender will receive :One notification for received ticketsone notification for the tickets returned to him.

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 label : load_more

Image Added