Event listings
An event feed with filters by date and category.
Events · iOS + Android
An events guide app for Armenia: date and category filters, search, a personal list of upcoming events, and ticket purchase and refunds inside the app. We continued an existing build, integrating with the client’s API and code. Stack: PHP Symfony, React, Kotlin, Swift.

In short: what the product is and who we built it for.
An event organizer in Armenia came to us to build an events guide app. Users had to be able to find events easily, filter them by date and category, keep a personal list of upcoming events and buy tickets without leaving the app.
What made the project special is that it was not built from scratch: we were continuing a product that was already under way. The team had to get to grips with someone else’s code, integrate with the client’s API and back end, and take the app all the way to a full release.
The client needed a convenient events guide with fast search, flexible date and category filters and clear navigation through a large catalog of events. Users should not only browse listings but also plan what to attend through a personal list with reminders.
The second goal was to implement the full ticket purchase cycle inside the app: choosing a date and seat, placing the order, paying and being able to request a refund, all of it connected to the client’s existing infrastructure.
How we built the product, from architecture to process.
We worked in Agile with an upfront discovery and analysis phase: first we untangled the legacy code and the client’s API, fixed the scope of the improvements and planned the release. The mobile clients are native, Swift for iOS and Kotlin for Android, while the server side and integrations are built on PHP Symfony and some of the interfaces in React.
Our main focus was seamless integration with the client’s back end: listings, ticket purchases and refunds run on the client’s infrastructure, and the app serves as a convenient storefront and planning tool for the user.
Tools chosen to fit the product’s goals.
The client side is built in Swift for iOS and Kotlin for Android. Native development gives full access to the platform’s system APIs: push notifications, the events calendar and the payment flow, with no restrictions.
We considered the alternatives: React Native (a quick start, but a weaker payment UX and limited API access) and Flutter (similar capabilities, but a separate build pipeline). Native development was chosen because of the payment flow and UX requirements.
Key capabilities that solved the business problem.
An event feed with filters by date and category.
Fast search for events by name on the home screen.
Description, showtimes, venue and organizer.
A personal list of upcoming events with reminders.
Choice of date, seat and row, checkout and payment.
Refunds for previously purchased tickets inside the app.
Key product screens, step by step.



The start screen opens with vivid event listings: event search, a “Venues and organizers” block and curated event collections with cover images. Users immediately see what is on and can open the details in a single tap.
Next to it is the “My events” section with the list of selected events, a universal ticket and reminders, as well as an event card with a description and a buy button.

The project followed an Agile methodology in six stages: business analysis, discovery, analytics and design, development, testing and support.
This sequence let us carefully work through the client’s legacy code and API, plan the improvements and take the app to release without compromising on quality.
The search screen returns results as a list with cover images, category and date filters and sorting. Users can quickly narrow a large catalog down to the events they want.
The event card shows the description, session schedule, venue and price: everything needed to decide whether to buy a ticket.



The full purchase cycle lives inside the app: an event card with a trailer, rating and showtimes, choice of date, venue and time, seat selection by row and the total price with a link to payment.
The “My tickets” section stores purchased tickets with the date, venue and event status, including the cancellation and refund scenario.
The core of the project was continuing an existing product and integrating with the client’s third-party API and code. The team had to fit carefully into the existing infrastructure without breaking the ticket sales processes that were already running.
The Agile approach with a discovery and analysis phase reduced risk: the scope of improvements was fixed in advance, and ticket purchases and refunds run on the client’s back end without duplicating logic.
The app collects users’ personal data: name, contact details and ticket history. Payments go through an external payment gateway, and card data is not stored on the server.
User data is processed under the requirements of the client’s jurisdiction and stored on the client’s servers, with role-restricted access.
2 native apps (Swift for iOS, Kotlin for Android) integrated with the client’s back end.
Date and category filters plus event search on the home screen.
A personal list with reminders about upcoming events.
Ticket purchase and refunds inside the app.
Completion of a previously started project: integration with the client’s third-party API and code.
Roadmap: venue map, seat selection and cart (next version).
The cost depends on the number of integrations (payment gateway, ticketing system), the set of screens and the requirements for personal data processing. We provide an exact estimate after analyzing the specification.
Yes. The team works through existing code: we audit the architecture, draw up an improvement plan and agree on the scope. We have done this before: the Move2Armenia project started with a partially built back end.
The user selects a ticket and pays through an external payment gateway. Card data is not stored on the client’s server. A refund is initiated in the app and processed on the payment gateway side.
Users’ personal data (name, phone number, ticket history) is stored on the client’s server and processed under the requirements of the client’s jurisdiction. Payment details are handled by an external gateway, without storing card data. We also provide templates for the client’s privacy documentation.
A typical range for completing native iOS and Android apps with back-end integration is 12–20 weeks, depending on the scope of integrations and the complexity of the business logic. We fix the exact timeline after discovery.
Companies from retail, medtech, logistics and e-commerce that we helped build digital products.
The full spectrum of development — from native mobile apps to web platforms, AI and cloud. Pick a direction or order a turnkey project.
Native iOS & Android plus cross-platform Flutter and React Native — from MVPs to apps with millions of installs.
Learn moreNative Swift / SwiftUI iOS apps — with Apple Pay, Sign in with Apple, App Store Connect deployment pipelines.
Learn moreNative Kotlin / Jetpack Compose Android apps — Material 3, Google Play release pipelines, Firebase integration.
Learn moreSingle Dart codebase across iOS, Android, web and desktop — with native modules where needed.
Learn moreProduction web apps on React, Next.js, Vue and Node — SaaS dashboards, B2B portals, marketing-conversion stacks.
Learn moreREST, GraphQL and gRPC APIs — designed for partners, mobile clients and internal microservices.
Learn moreBespoke platforms for mid-market and enterprise teams — internal tools, vertical SaaS, mission-critical backends. Discovery to launch in 12–36 weeks.
Learn moreFocused MVPs in 12–20 weeks — one or two integrations, real users on day one, telemetry built-in.
Learn moreEnd-to-end ownership of a digital product — design, build, ship and continuous evolution.
Learn moreTool-using agents that plan, retrieve, act and self-evaluate — in customer service, ops automation, internal copilots.
Learn moreAWS, Azure and GCP architecture, Kubernetes, Terraform/Pulumi, CI/CD and observability — SRE-grade operations for product teams.
Learn moreTechnical SEO, Core Web Vitals, structured data, internal-link architecture — built into your engineering process.
Learn moreRelated cases

A Tilda website for a Novosibirsk builder that turns traffic into estimate requests: per-m² pricing, real projects, an object map and verified reviews.
View case
A Tilda landing page for a pipe manufacturer, launched in 2 weeks: product specs, standards, a PDF catalog without sign-up and a lead form.
View case
Single-page Tilda landing with Telegram-bot lead capture for an ad agency — shipped in two weeks, US & EU ready.
View case20 articles across 5 categories — engineering-led guides on AI, SaaS, MVP, compliance and mobile for US and EU product teams.

Performance-tested comparison of RN (New Architecture) and Flutter (Impeller) across hiring, time-to-market and EU/US compliance.
Read article
Real cost ranges by region (US onshore, Western EU, EU nearshore), team and feature scope. With a worked fintech example.
Read article
Data-driven framework for choosing iOS-first or Android-first in 2026 — US & EU market share, ARPU, review timelines, EU DMA.
Read articleTell us where your project stands today, including any code and APIs already in place, and we will plan how to take it to release. Let’s discuss how a similar solution could work for your business.
Share a few details and a senior consultant will reply within one business day.
Email: sales@yusmpgroup.com
Phone: +374 44 871 811
Offices: KAMAR Business Center, Vazgen Sargsyan St. 2, Yerevan, Armenia · Remote — East-Coast US overlap (9 AM–1 PM ET)