Changi Singapore

Support for two mobile apps enhancing the experience of travel and city exploration.


  • Scope Business analysis, workshops, UX/UI design, frontend, backend, Flutter development
  • Timeframes February 2021 – January 2022
  • Technologies Flutter
  • Business sector Travel
  • Model of collaboration Hybrid: established scope, close cooperation, team extension
  • iteo Team 2 x Project Managers
    2 x UX Designers
    2 x Business Analysts
    4 x Flutter developers
    1 x Quality Assurance engineer
    1 x UI Designer
    1 x Software Architect
    3 x Backend developers
    3 x Frontend developers

Our team has done incredible work recognizing the clients needs and areas of uncertainties. It allowed us to propose a great UX and UI design for the whole application.


  • 2021

    Project launch

  • 2022

    End of works

  • Project’s highlights

    We put a special emphasis on the audit and workshop phase to get to know all of the project’s shortcomings and plan a wholesome strategy to make it more intuitive, user friendly and functional. 


    Business needs & goals

    The Client needed us to fix all the loopholes in the ready-made project. It involved working on an orderly methodology and processes. 


    Changi Recommends

    Being a subsidiary of Changi Airport Group, the app’s goal is to enhance the travel experience of its users, whether it’s a business or leisure trip. It includes a number of relevant travel services: taxis, e-commerce, insurance, currency exchange, and more. 

    Changi mobile

    Changi MVNO is an application working as a Mobile Virtual Network Operator – it sells SIM cards and plans, phone numbers, as well as mobile internet. 


    UX workshops

    Changi Recommends

    We started with product, analytical and audit workshops to establish our Client’s priorities.

    After completing the design (UX, UI), we’ve launched the process of the app development. In the first iteration we’ve focused only on the e-commerce part of the “super app”. Clients could create their accounts and buy whatever needed throughout the webview.

    Changi Mobile

    We conducted a thorough technological audit to establish further works.

    Workshops allowed us to decide upon:

    • application shell (architecture), servers, setting up of the environment’s infrastructure

    • mobile application shell (including deployment – testflight)

    • customer account creation functionality (initially, as an attempt to separate Changi Go from Changi Mobile)

    • purchase of a plan (sign up new lines) – as a basic version (only a number) – this would however include sim card delivery tracking, change of that process, cancellation (initially without add-ons and user validation in this stage)

    • payment and billing, downloading past bills (without purchasing add-ons)

    • data user history

    • account management, view and update MVNO account details

    This part involved much more backend work on our end, since we were responsible for connecting the new app to the system which required a perfectly working synchronization. The design, however, remained the same as in the previous version of the app.


    Challenges & solutions

    The multitude of services and their previous manner of presentation was one of the most demanding challenges in the project.

    It was difficult to contain such a substantive amount of information on a phone’s screen to make it convenient and attractive for a user. That’s why we needed to work out an adequate approach and convince the Client that it’s the best way to go. 


    Changi Mobile required a solid backend which was supposed to be an engine for the whole project and one of our largest challenges.

    It needed to be written from scratch in a corrected architecture with a better handled integration.


    Another challenge we faced was cooperation with the Client’s backend team.

    The most problematic part were frequent changes related to the parts of the application we’ve already finished working on.

    Quality Assurance

    The project required a lot of testing, since we had to cover our day to day work, previous increments we’ve built, but also backend synchronization. Therefore a QA expert input was crucial for us to continue work.