an app for one of the top-10 payday loan brands in Europe


iOS / Android

About the project
Making of

Why Native?

In one of our notes we've already covered how a native app can provide value for the business and users. The case goes almost by the book. At the very start the web-version + mobile app were made as an MVP. While the service grew, it required a more sophisticated and user friendly front end. Unfortunately, a hybrid app became a stopper. Any major change in the web-front would most likely lead to app malfunction. Thus we developed native applications for both platforms.

Native solution now allows to develop backend, web-front, and mobile as separate services. This gives more flexibility for the business development and new products inclusion.

The Switch

It was crucial to keep the existing active user base. Encouraging users to install another app (even a better one) could lead to low conversion rate. Also, the hybrid app would stop working the minute the web-site updated. This could cause negative feedback from daily active users.

To avoid these problems we have used a small trick. Each app in the store has its own ID. While publishing the new native app we have used hybrid version ID. The new app loaded into the same slot where the old app used to be.

From the user perspective it looked like a common version update. Most devices have the auto-update option enabled. The native app "updated" the already installed hybrid version, providing almost 100% adoption rate. This technique allowed us to switch most of the users without causing any trouble.

Tip: if you take a look at the link to the Google Play Store, it will end with "hybrid". It's a relic of the past, as the app itself is native.

Project phasing

Why Native?

The Switch