With the popularity of iPhone, Android or any smartphones, there is demand of doing online updates of profiles or transactions on the run.
When comes to designing the user interface and recommending the functionality for mobile banking, we have to remember that there are limitations to the amount of contents, features, not to mention the types of transactions allowed and the encryption logic to use. One important note for developing mobile apps for online transactions is not to allow caching or to store unnecessary user profile and date inside the smartphone’s memory.
Below are the basic recommendation for consumers’ needs in performing banking activities on-the-go:
| Login | Accounts | Transfer | Payment | Settings | Miscellaneous |
| 2FA | Account Summary | Immediate/Future Funds Transfer to My Account | Add to My Payee | Application version display | Maintenance Page |
| SMS content in app | Account Details | Immediate/Future Funds Transfer to Another Account | Immediate/Future Bill Payment to Prearranged Payees | Language change | App update screen |
| SMS regenerating | Transaction History | Immediate/Future Funds Transfer to Other Bank Account | One Time Payment | Error Screen | |
| Flash SMS | Schedule Transfer Summary View/Amend/Cancel | Schedule Payment Summary View/Amend/Cancel | Logout | ||
| Terms and conditions | Contact US | ||||
| Language switch | Idle Session Timeout | ||||
| Home Screen |
Advertisement
0 Responses to “Basic Requirements for Developing Mobile Banking Apps”