Kristijan Jurković

Domain money is a company that provides professionally managed portfolios designed for long-term growth. I charted the successful development of Earn, KYC, and deep linking features. I prioritized security by implementing storage encryption.

Fundingport is an innovative online financing platform. It connects borrowers and lenders for corporate finance, commercial real estate, and renewable energies. I've charted the successful development of an Agency product on the back end side and implemented features tested through unit and integration tests via GitLab pipelines.

A Flutter-based mobile app for food purchases in offices. Helped the team build new features and maintain existing popular in-company fridge apps for Android and iOS platforms.

Mentored and code reviewed other team members.

Successfully charted existing popular baking apps rewritten for iOS and Android platforms on MVVM+C and MVVM architecture. Helped the team build new features. Mentored and code reviewed other team members.

Helped the team build new features and maintain a popular loyalty card app used in stores in Germany. Implemented the Christmas redesign feature using Clean-code architecture.

Mentored and code reviewed other team members.

Native mobile (iOS and Android) banking applications for checking and acquiring credit scores.

Charted the successful development of both Android and iOS mobile applications. Prioritized security by implementing certificate pinning and storage encryption.

I worked as part of the team developing healthcare solutions for the US market. This app was coded in a modular way and both apps shared codebase which was completely controlled by the back-end.

To ensure maximum testability, the applications were implemented using MVP architecture in conjunction with dependency injection (Dagger 2) and a reactive approach (Rx Java2).

Tests were written using the JUnit test framework in combination with Mockito for mocking the networking layer and Espresso for instrumentation tests. Finally, a continuous integration environment was set up using Jenkins with Bitbucket repository

I developed and maintained mobile banking applications with a focus on data security, both alone and as a part of a team. I’ve integrated time and event-based mobile tokens (Asseco, Entrust) and worked with SOAP-based web services and RESTful APIs.

To ensure maximum testability, applications were implemented using MVP architecture in conjunction with dependency injection (Dagger and Dagger 2). Unit tests were written using the Mockito for mocking the networking layer. Finally, a continuous integration environment was set up using Circle CI with both GitHub and Bitbucket repositories.

Technologies used include Android Studio IDE, Android SDK, and Java.

I developed and maintained apps for electricity and gas providers in the Netherlands with a focus on data security, both alone and as a part of a team.

To ensure maximum testability, applications were implemented using MVP architecture in conjunction with dependency injection (Dagger and Dagger 2). Unit tests were written using the Mockito for mocking the networking layer. Finally, a continuous integration environment was set up using Circle CI with both GitHub and Bitbucket repositories.

Technologies used include Android Studio IDE, Android SDK, and Java and Kotlin

The client wanted to log out the user automatically after three minutes of inactivity. I used a user interaction listener (part of the Android Activity class) but this method did not track if the user input via the keyboard, only with clicks and scrolls.

I had two options to go with:
1. Inflate a layout into the fragment/activity and iterate through all views and its children recursively after the layout was attached to an activity or fragment.
2. Search only the EditText instances and attach TextWatcher which would track input. This would consume a lot of time and sometimes cause the app to freeze.

Since Android was already doing that while inflating, I went on and created my own custom LayoutInflater which I attached to the activity by replacing the ContextWrapper with my own version, replaced the factory classes, iterated EditText instances, and attached TextWatcher with my own listener on the inflated view so I could track user input and properly log him out after a period of inactivity. 

This approach was faster since it was done while parsing XML itself and in one iteration, unlike the first approach. It was important since most of the interaction with the app are forms which the user has to fill out.