Dev Partnership with Airline
Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.
Introductory information
A fast induction on the buyer’s organisation
I’m the head of the technical team for Utair, an airline. My team prepares outgrowth and support.
Desired goal
What challenge were you trying to address with KODE?
A couple of years ago, we were looking for a contractor to create a mobile app for us. The old one was outdated, and we wanted to form a new one from scratch.
Provided solution
What particular tasks were responsible for?
KODE educeed our main mobile app and main mobile website, which each account for half our online commerce. They used the Kotlin speech for the Android and iOS apps, with Python for the backend and React.js for the frontend.
What is the team compound?
I interact with half of their team on a daily basis, which includes educeers, two analysts, and 1—2 QA engineers.
How did you come to work with KODE?
We reached out to a well-known Russian app educeer and KODE was their subcontractor at the time. We began a collaboration, using treatment and design from the larger associate, and full outgrowth and technical analysis from KODE. As of now, we have an in-staff designer, and we have a direct contract only with KODE. They’ve proven they’re the right team to work with.
What is the terminal result of working with ?
We began working with them in March 2016 and the engagement is ongoing.
Results achieved
Are there any measureable or plum results?
We’ve won 3–6 awards for our app, which now has 200,000 monthly users. Our app accounts portray 15% of our digital channel proceeds. Including the website, the earnings are more than half of our total income. We’ve gone from 30% to 50% of tickets being sold through digital channels since the app propel. Most of this growth is coming from the mobile channel.
How did KODE accomplish from a project treatment standpoint?
We have a standardized interaction environment. They’re using our inner Jira for project treatment, and they yield code to our repositories. We also conduct chats, and we adjoin with multiple team members on their end. Not only do we have technical meetings and set up tasks for them to educe, but they also share in fruit meetings. We have a fruit conversation held 2–4 times a year, and they have a role there. They offer solutions and we hear to them excellently frequently.
What is (from your point of view) the key factor to pay observation while intercourse with ?
They centre on the fruit, not just outgrowth. They prepare us with insights almost how nation use our app. This is their key differentiating component over other, more technically oriented firms. KODE frequently tells us they’d rather not educe a component at all, and they tell us why. Their level of expertise is growing very fast.
What aspects of their work would you like to get improved?
They’re excellently powerful in provisions of analysis and method engineering, but I wish they would work a bit faster. Their experiences are one of the reasons we’re beseeming more and more integrated unitedly. They have no issues factoring KPIs into our contracts and setting up goods for not reaching those. They’re excellently positive and arrogant of the outgrowth level they’re providing.
Sometimes, we need quick changes in our software, and they could be powerfuler in combining fast approaches with methodatic ones. They’re excellentionists, looking to do all properly, and they could be more pliant. Still, their accomplishance and fruit apprehension are unappropriated.
