67% of U.S. adults aged 18-29 are regular users of mobile banking apps. With 30-44-year-old respondents, more than half (58%) use apps for mobile banking services; however, there are still many who do not use mobile banking at all. The top 3 reasons for this are:
- their needs are met without any apps;
- they don’t see any reason to use them; and,
- they are concerned about the security level of such apps.
Let’s look more closely at the third reason. The solution to that one can’t possibly be squeezed into one paragraph. Developing a mobile banking app that is both secure and user-friendly can be quite a challenge. Along with that, scammers, frauds and hackers are learning to exploit vulnerabilities of the technologies that seem sophisticated to some developers.
1. Opt For Native Mobile Banking Apps
Let’s start with the basics. What is a native app? Native apps are designed separately for each mobile OS using the appropriate language (Object-C or Swift is used for iOS; Java is used for Android; however, C# can be used for both platforms if Xamarin is used for the development). A native app written for Android won’t run on iPhone and the other way around. Native apps can interact directly with the hardware and software of the device and take advantage of them, accordingly. They have been proven to be more reliable, responsive and perform better than web or hybrid apps.
Many financial institutions opt for developing mobile versions of their websites instead of developing a mobile banking applications. Considering the low level of securing the connection, the data transmitted via a mobile browser can get intercepted by hackers easily. Although some mobile-optimized websites are developed on a quite sophisticated level and provide a better UX and functionality, as well as the security means similar in effectiveness to those featured in native solutions.
Native mobile apps have many advantages in terms of security in comparison to the mobile versions of the websites. They turn multi-factor authentication into a seamless user experience: for example, through face recognition via the front camera or fingerprint scanning via Touch ID technology. With these methods, security checks don’t risk damaging the convenient user experience. You can also embed a certificate into a native app to prevent any man-in-the-middle hacks. APIs allow developers to assess risks with less effort, as it’s easier to create a risk evaluation algorithm in a native app, and it will be more accurate as it can track all the actions taken by the user.
As for costs, they depend on your ideas and the custom features you would like to include in your project, as well as who you hire and how much time the development is going to take. On average, it takes 6 to 12 months to fully design, test and launch a native app. Depending on the hourly rate, the cost of a six-month development of a mobile banking app can vary from approximately $38,400 (if you hire an Eastern European company) to $96,000+ (if you make a deal with a U.S. development business).
2. Secure The Login Process
Generally, there are three elements of customer authentication that can be used to prove that the user wants to log into his/her own account:
- possession (something that belongs to the person, i.e. a certain device or a credit card);
- knowledge (something that only the user is supposed to know, i.e. passwords, PINs); and,
- inherence (something that user inherited genetically, i.e. fingerprints).
It is enough to require just two of the three elements stated above to prove the identity of the user. Fingerprint and facial recognition have become quite popular and easy to use, thus making the user experience even better. If you decide to include them in your mobile banking app development, however, keep one thing in mind: not every user possesses an iPhone, and device hardware can malfunction. So, make sure you provide your users with an option B for a more traditional authentication via a call or text.
It is also important to make sure that, after a certain period of inactivity, the login session times out.
Multi-factor authentication is a must for both traditional banks and third-party startups. The price of multi-factor authentication depends heavily on the number of factors that can be used for authentication. It may vary from $1,400 up to $12,000+.
3. Implement Behavior Tracking
We recommend to consider implementing of real-time behavior tracking features in your banking application. Their aim is to gather user data for further analysis. Such data can be useful for marketing purposes, improving UX, or, what is more important, to help verify activities in order to prevent fraud transactions. On the basis of data being tracked bank then can flag certain activities as abnormal ones (for example, if user has logs in from a new location far from the usual one or if behavioral patterns seem to be unusual for this user).
Behavior tracking can be designed to gather data by monitoring the following user actions:
- gestures and touches;
- activity log (the time and the length of login sessions);
- user actions (which features are used, when and for how long);
- the information about the device (what gadget is being used, technical specifications that might be required to know, etc.).
If you need to get information on your project development our managers will be more than happy to answer any questions
This, of course, is far from exhaustive list; however, it is up to you what data to collect depending on your needs and the level of security you want to provide your users with.
4. Encrypt Data On-Device & On-The-Go
Encryption is what stands between a hacker who intercepts data from a wireless network and the security of the user’s bank account. Basically, if you enable encryption in your app, the data that is stored by the app or transmitted from it (or to it) is encrypted by an algorithm called cipher. The data can be decrypted and read only by those apps or servers that hold the key used during the encryption process.
Most banking solutions currently tend to be initially written in simplified HTML and may not imply such prominent features as geolocation and encryption at all.
Nowadays, there is a widely used standard for data encryption called the Advanced Encryption Standard (AES). The longest key possible for data encryption is the 256-bit option. In addition, 128-bit and 192-bit keys are also options, though they are less secure when it comes to hacker attacks. AES is even used for encrypting classified information by the U.S. government.
You need to make sure that you implement both on-device and on-the-go data encryption. The former option means that the data that is stored by the app on the device itself, and that data must be encrypted in order to prevent any rooting. The latter means that the data transmitted between the servers and the device must get encrypted before transmission and decryption by the recipient.
If you add encryption to the list of features you want to implement in your project, and advertise it accordingly, your potential users will trust your app enough to use it for making a financial transaction. Up-to-date encryption can add upwards of $1,400 to your mobile banking app development cost.
5. Test, Test, Test!
M-banking apps have to be tested thoroughly. You don’t want to drive a car that hasn’t been properly tested, do you?
Of course, every feature should be tested when you develop a banking app. User experience should be flawless and seamless, all links should be correct, there can be no glitches or bugs, and the application should be able to operate under a huge load, etc. But there is one thing that you should pay particular attention to – whether your app can be easily hacked.
Surely, the fact that security testing is flawless does not mean that there aren’t any vulnerabilities left to be exploited. If you dedicate enough time and resources to security testing, mobile banking app developers can eliminate many of those vulnerabilities before data or user money is stolen.
There are several elements that need to be tested by a mobile banking app development company before the app is launched:
confidentiality of the data stored or transmitted;
- integrity of the data (including protection from modification by third parties);
- user authentication process; and,
- availability of the data to those who are authorized to see and/or modify it, etc.
Penetration tests should also be conducted to test the possibility of a hacker affecting any of the elements stated above. During such tests, an attack is simulated to determine whether all the vulnerabilities have been eliminated. The cost of this security check can vary from $1,400 if you opt for very basic testing, and up to $12,000 if you want it to be as thorough as possible.
The Bottom Line
It is easy to get lost in all the numbers. That’s why we have gathered all the necessary information on how much it would cost to develop a mobile banking application that is secure. The table below includes all the details:
|What you get||Time required for development (in hours)||Total Cost, at $35 per hour rate||Total Cost, at $100 per hour rate|
|Native app development||Two apps designed specifically for two mobile OS with basic mobile app functionality||960 hours||$38,400||$96,000|
|Multi-factor authentication||Integrated user authentication options (via password and/or fingerprint scan and/or facial recognition, etc.)||40-120 hours||$1,400-$4,200||$4,000-$12,000|
|Behavior tracking||Features that track the user behavior (gestures, use of certain features inside the app, the length of login sessions, etc.)||40-80 hours||$1,400-$2,800||$4,000-$8,000|
|Data encryption||Data encryption algorithm on-device and on-the-go, according to AES standard||40-80 hours||$1,400-$2,800||$4,000-$8,000|
|Security testing||Revealing vulnerabilities, penetration testing, security assessment||40-120 hours||$1,400-$4,200||$4,000-$12,000|
It is not enough for startup to simply build a mobile banking app that has great UI/UX and functionality. Your app must also be secure to win over potential users, because they want to feel safe when they use an application to manage their hard-earned money.
To sum it up, you need to pay close attention to:
- opting for native app development instead of hybrid/web/cloud-based options;
- multi-factor authentication;
- behavior tracking;
- data encryption on-device and on-the-go; and,
- security testing.
Of course, the price of developing custom mobile apps for banks is not written in stone.
If you want to get a quote on bringing your idea of such an app to life, feel free to contact our EGO-cms specialists. We are always glad to answer any of your questions.