April 2, 2024

Extended mobile storage capabilities

Previously, our branded wallet was storing data in file storage format which was convenient and lightweight way to handle small amounts of persistent data in application such as user preferences and simple app settings. Unfortunately, it was not intended to store complex data structures or large datasets, ie Ticket, causing App to crash when more than a thousand tickets were held by a spectator.

We revamped our storage approach in order to support five thousands tickets and improve overall performances, scalability and offline capabilities of our branded wallet.

March 13, 2024

Redesign of the "Tickets returned for resale" screen

Our burger menu, was caught between two worlds: the new user experience introduced in the past 3 sprints and the old UX in some subsequent screens, in particular the screens related to resale. If unaddressed, this design disparity would not only mar the aesthetic appeal of our app but also complicate its usability, making it difficult for users to properly track their tickets on resale efficiently.

As we introduced tabs for events (Upcoming, Past) and for transfers (Pending, Completed), we followed the same approach in order to replace the previously two collapsible menu entries, which led to the Pending/History resale screens, by a consolidated into a single, more efficient entry point.

Upon selection, users will be directed to a new screen, where the resale process is neatly organized into two tabs: Pending and Completed. This streamlined process not only makes better use of space but also aligns perfectly with our sleek new UX design, ensuring a more cohesive and enjoyable user experience.

	Before Redesign	After Sprint 2 (Jan 16)	After Sprint 4 (Mar 13)
Burger/More menu
Resale screens

Prevent spectators to dismiss implied navigation when Notifications campaign redirection is configured for SCREEN_NEXT_MATCH

This update will prevent spectators from dismissing ticket-related notifications by simply closing the popup, clicking the "Close" button.

By only be able to click "OK", the spectator will be redirected to the first ticket of next match.

Before	After Sprint 4 (Mar 13)

January 16, 2024

Minimalistic banners for My Tickets screen

Currently, when spectators launch the app, they are greeted with an overwhelming amount of information. Our goal is to adapt the layout to prevent information overload without compromising the delivery of crucial details, targeting the 'orange' banners invitating spectators to enable bluetooth and/or transfer tickets.

New banner on My Tickets	New popup (by clicking "Learn more")

Crowdin translation keys (in base.json)

Key	EN
transfer_warning_title	Please transfer your tickets
transfer_warning	There are several tickets for this event, please send them to your guests.
transfer_warning_action	Transfer ticket
different_location_warning_title	Please transfer your tickets
different_location	You have tickets in different locations within the stadium. Please transfer tickets to your guests or visit our FAQs.
different_location_warning_action	Transfer ticket
permission_required_ios_title	Turn on Bluetooth on your device
permission_required_android_title	Turn on Bluetooth and Geo-location on your device
permission_required_ios	Bluetooth permission is required to activate your ticket(s)
permission_required_android	Location (and Bluetooth - if you are using Android 12 version and above) permission is required to activate your ticket(s)
restricted_spectator_title	Account temporarily restricted

New UX for the "Main" menu and subsequent screens

In our ongoing mission to enhance the user experience on our Mobile Wallet, we are excited to announce the latest improvements targeting the "Main" menu and its associated screens. This update is built on top of the Mobile improvements introduced in Breithorn V3.

A new app build is needed

Menu Reorganization for Improved Usability

The "Main" menu has undergone a thoughtful reorganization. Our objective was to enhance clarity and ease of use. We've moved away from the previous design that relied on expandable and collapsible elements, opting instead for simpler menu items. This change not only makes the menu more straightforward but also allows for quicker navigation.

Visual Upgrades for Accessibility and Aesthetics

The visual layout has been optimized to facilitate a more intuitive user experience. We've focused on decluttering the interface to present a clean, accessible, and user-friendly menu that aligns with modern design standards.

Streamlined Interaction

Users can now enjoy a more streamlined interaction with the menu. The restructuring allows for immediate access to various features without the need to navigate through multiple levels. This direct approach respects the user's time and simplifies their journey through the app.

Menu	Profile

New "Support details" screen for Enhanced On-Site Operations

To simplify on-site operations and provide a better support experience for spectators, we are proud to release the new 'Support Details' screen. This feature is designed to display essential information about the spectators at a glance, including a QR code linked to their email address.

With a handheld barcode-scanner compatible with 2D QR Code, it eliminates the need for manual email entry, thereby speeding up support processes and reducing the likelihood of errors that can occur with paper-based email collection.

This new screen is directly accessible from the "Main" menu, by taping on "Support Details" (crowdin key support_details_title in base.json file).

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.

Browser not supported