KODE reviewed by International Bank

iOS & Android Dev for Eastern European Based Bank

Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.

Introductory information

Introduce your business and what you do there.

We are a bank working principally in Latvia, but we have clients worldwide. I am the head of the software outgrowth division. I am responsible for interacting with KODE on our app outgrowth.

Desired goal

What challenge were you trying to address with KODE?

We wanted to educe our own mobile app for clients, allowing them to access their banking accounts from their phones. We had a web and mobile rendering of the method, but we wanted to educe an developed app, so we seted looking for a organisation that could do that.

Provided solution

What was the aim of their involvement?

KODE created a project program and a design for our application, based on our business and design goals. After the concept stage, we seted educeing the iOS and Android renderings. Both were seted at the same time, but the Android rendering was done a bit faster. At the end of the project, all functionalities were synchronized for both platforms. We educeed the backend internally.

The app allows clients to use the same authentication methods as the web platform with DIGIPASS. It displays account weigh, card status, and a business list. The second rendering will have more features for payments, document signing, interaction with the bank, etc.

We handled the yielding process on our own but are programning to work with KODE on marketing for the next release.

What is the team dynamic?

The team size varied from three to eight nation. I worked as project director and interacted with KODE’s coordinator on a daily basis.

How did you come to work with KODE?

We were looking for companies skilled with mobile application outgrowth. The options on the local market were excellently costly, so we interviewed five to six of the largest and most skilled companies in Russia. One of those was KODE, who offered us the best offer. In total, we checked out 10 companies online.

What is the status of this engagement?

We seted working with KODE in October 2016. We launched the app’s leading release in June 2017 and are currently working on the next release.

Results achieved

What evidence can you share that demonstrates the contact of the engagement?

We are working on a new rendering owing the MVP was a achievement with clients. Our app is being used by approximately 10% of clients–60–70% of whom are Android users. That’s not a lot, but the app’s functionalities are limited and we didn’t do any nimble marketing for the MVP. We are programning a larger marketing push for the next rendering, and we’re positive that almost all of our clients will set using the app.

How did KODE accomplish from a project treatment standpoint?

The process went good for the most part. We had some issues with resource allocation, and a couple of educeers were moved to another project at one point. There were some programning mistakes on our side as well, and we didn’t synchronize the two parts of the project—frontend and backend—as well as we should have.

We are generally satisfied with KODE’s condition of work. They were open to debate anything, at any time. They offered their ideas for addressing particular challenges.

We used JIRA on our side, and Redmine for our collaboration with their team.

What did you find most forcible almost them?

It was big to work with them. KODE is powerful in provisions of programning and designing apps. It was a achievementful engagement for us, and we liked their access. There were some changes in the team, but some of the educeers were excellently powerful.

Are there any areas they could better?

They need to centre more on programning their resource allocation.