Lack of a transparent development system and the presence of errors in the code.
At the time of the prototype launch, there was no system for setting goals, interaction, development. As a result, an impressive technical debt with outdated code and, consequently, a large number of bugs has accumulated.
The system is not ready to work with new clients.
The platform first served one festival organizer, handling promotions and tasks. Expanding required a flexible system where each event operated independently in time, payments, and promotions.
Low payment activity of users.
Electronic tickets, used for payments at festivals, allowed refills only via the event marketplace’s payment form. However, limited integration with one provider reduced ticket purchases and refills, lowering event monetization.
Optimization of development processes and streamlining of the software base.
To solve the issues, QA and PM identified errors and ensured fixes via proper task management in Jira and Slack. We set project goals and developed a strategy with a detailed step-by-step progress plan.
Changing the architecture of the event marketplace.
We modified the web app so each event operated independently, letting organizers set dates, locations, user settings, and generate reports without conflicts. To boost speed, we migrated to a cloud DBMS.
Improvement of the payment acceptance system.
We integrated multiple payment systems—Klarna, PayPal, Secure EFT, and major card networks—to meet user needs. Additionally, we enabled instant synchronization for fast fund transfers to the bracelet-ticket.
Although the organizer's admin panel and ticket store have a comprehensive, customizable functionality, it did not allow issuing access cards for staff serving festivals or VIP guests. The problem solution was a development based on Vuetify to simplify the interface of a separate control panel for working teams, that ensured managing tickets with customizable access levels for locations and entertainment. Its availability allowed the organizers to distinguish between visitors and groups, check in guests by categories and zones, and also upload flexible reports with information about the team.
After changing the marketplace architecture, there was a need to customize the panel in such a way that all settings of the festival would automatically display on the visitor's page. So, numerous settings and functions allow you to organize an event entirely according to the tasks of the event maker. As a result, the user can get a ticket of different access levels in the personal account, sell or change a card, and top up the balance in real time with its instant upload to the bracelet. The visitor can view the history of transactions and purchases, and receive additional bonuses from the organizers during the event. The organizer can upload event reports using custom filters and parameters, considering the information from all visitors tickets.
With the development of the admin panel for individual event organizers, there was a need to create a custom panel for issuing tickets for visitors. The FTL team has developed a customizable ticket dashboard where organizers can create promotional codes, and special offers, and control the number of tickets and access levels (ticket types). Also, the managers run partner offers that a visitor can receive for the balance on the ticket bracelet. At the same time, there are options to automatically synchronize ticket stores with all organizers' offices on the event maker side and to upload to third-party platforms for sale in just two clicks.