âThere is everything you need, and nothing infuriatesâ - the truth speaks through the lips of the client
In what form does the task come to you? Is this an oral description of the manager, a diagram on a flipchart, or customer specification? For our development team, this is a user story. And it may look like this: "As a business owner, I want to see accounts in a mobile application." The following questions follow from the story: âWhat information do I need? What should my employees see? Why am I using a mobile application and not an online bank? â
In order for the user to get what they want, a concise wording of the story should hide deep product analytics. We read about what does not lie on the surface under the cut.
Markswebb is a word familiar to everyone on our project. Analysts from a consulting agency each year make a rating of mobile banks for business in two categories: individual entrepreneurs and executives. The set of functions, as well as the needs of businessmen, differ in categories.
An inexperienced user will ask: âWhat are you doing at all? Do you support the platform? Everything has been implemented for a long time. â Partly true: making a payment on the phone is not news. But mobile payments are not the only task of a mobile bank for a business. There is also bookkeeping, acquiring, reporting, etc. - the list is rather big.
Striving for the heights Markswebb is a powerful mobile banking engine. The number of evaluation criteria is just crazy - 443 in 2019, two times more than in 2017. You canât keep up with it everywhere: you have to maneuver between the weight of the features in the rating and the complexity, not forgetting the value for the user and the financial effect. Then everyone is satisfied: users, managers and analysts of Markswebb.
But just chasing competitors is boring. Therefore, from time to time we make wow features where the ingenuity of the product and the team is used:
- Guys, let's make a QR code
- Well, itâs everywhere: in utility bills, on-line cash registers, even at Subway employees, there is ... What else can you think of?
- Hmm ... Can we add a code to the invoice for payment?
âWhat problem will we solve?â
- Well, the counterparty sent me an invoice and wants money. Gathering details with your hands is long and tedious. Now, if I could just point the camera at the expense ...
No sooner said than done. Now, at Alfa-Business Mobile, when you click the "Set Invoice" button, we generate a QR code with the details of the future payment, convert it to base64 and send it with other parameters to the reporting system. The system maps the data into a pre-marked template, collects a picture from the characters and returns the file in pdf format. The result can be seen below.
If the organization wants money, but doesnât want to display a document, the user can share the details on the screen or send to the messenger. A QR code is also recognized in every way: when you hover the camera, download pdf / png / jpg files inside the application, when you open it from the outside using the "Open with" button.
Dear users, thanks for your feedback! We rejoice when you are happy and sad with you. To find out your opinion, functional support, feedback from managers and, of course, reviews in stores help you. We monitor and analyze feedback on two platforms. Notes about the lack of useful features are turning functional requirements. Complaints about a long download or application crashes - in terms of performance and stability. Moreover, the more calls, the higher the priority.
To keep the teams up to date with the latest developments, our developers have written a chat bot. Information from the App Store is collected in RSS format, parsed and, in the presence of something new, sent to the Slack channel. In the case of Google Play, a token is requested for feedback through the developer's console, and scheduled reviews also go to chat.
Good reviews are nice, and bad reviews are helpful. Therefore, special attention is paid to negative assessments. For each such case, we look at the platform and version of the application, and try to reproduce it in a test environment. Often the problem is fixed in the latest version of the front, then we advise the user to update. It is not always possible to fix a bug promptly, because some problems are global in nature. One example is the automatic code substitution from SMS. Google has updated its privacy policy and has prevented parsing messages. Fearing removal from the store, SMSki had to be cut out. Then Google proposed a new API, and auto-substitution was returned, but it took a while to resolve the issue.
But enough about the sad.
The withdrawal of operations from branches is a global task of banking applications. Itâs good when a client draws up a product, but doesnât go to the office for it. The user saves time; the bank saves resources. At Alpha Business Mobile, cards, deposits, overdrafts and other products are available for ordering. And so that the user knew about this, we made offers in the form of banners.
The task was difficult: you need to earn money, and not to tire the user of banners. Therefore, the fate of the cross on the banner was decided by three groomings in a row (for reference: Google believes that grooming is a grooming of dogs, but in the case of scrum it is a meeting with a discussion of backlog). Asking for confirmation where it is not necessary is bad practice. But here it is important for us that the user does not hide the offer by accident or on the machine. Therefore, before hiding the banner, we ask you to think again.
A business has many desires to consider when implementing the application. Business and IT complement each other: the more features in the application, the more customers. And vice versa. The main thing is not to forget to make sure that the solutions work. When switching between windows and performing actions in the interface, an event counter is triggered, which sends data to Google and Firebase Analytics. So we find out that the user ordered the product after seeing our banner. Or did not order.
Sources of requirements in the article do not exhaust product analysis. He faces many tasks: prioritization, risk management and so on. However, ratings, feedback and fin. The effect allows you to check that the necessary functions in the application are and do not infuriate the client.
If everything is so, then it worked for a reason :)
In order for the user to get what they want, a concise wording of the story should hide deep product analytics. We read about what does not lie on the surface under the cut.
Learn from your competitor because he will learn from you
Markswebb is a word familiar to everyone on our project. Analysts from a consulting agency each year make a rating of mobile banks for business in two categories: individual entrepreneurs and executives. The set of functions, as well as the needs of businessmen, differ in categories.
An inexperienced user will ask: âWhat are you doing at all? Do you support the platform? Everything has been implemented for a long time. â Partly true: making a payment on the phone is not news. But mobile payments are not the only task of a mobile bank for a business. There is also bookkeeping, acquiring, reporting, etc. - the list is rather big.
Striving for the heights Markswebb is a powerful mobile banking engine. The number of evaluation criteria is just crazy - 443 in 2019, two times more than in 2017. You canât keep up with it everywhere: you have to maneuver between the weight of the features in the rating and the complexity, not forgetting the value for the user and the financial effect. Then everyone is satisfied: users, managers and analysts of Markswebb.
But just chasing competitors is boring. Therefore, from time to time we make wow features where the ingenuity of the product and the team is used:
- Guys, let's make a QR code
- Well, itâs everywhere: in utility bills, on-line cash registers, even at Subway employees, there is ... What else can you think of?
- Hmm ... Can we add a code to the invoice for payment?
âWhat problem will we solve?â
- Well, the counterparty sent me an invoice and wants money. Gathering details with your hands is long and tedious. Now, if I could just point the camera at the expense ...
No sooner said than done. Now, at Alfa-Business Mobile, when you click the "Set Invoice" button, we generate a QR code with the details of the future payment, convert it to base64 and send it with other parameters to the reporting system. The system maps the data into a pre-marked template, collects a picture from the characters and returns the file in pdf format. The result can be seen below.
If the organization wants money, but doesnât want to display a document, the user can share the details on the screen or send to the messenger. A QR code is also recognized in every way: when you hover the camera, download pdf / png / jpg files inside the application, when you open it from the outside using the "Open with" button.
About Subway, by the way, was not a joke. 
Good bank, and interesting contests
Dear users, thanks for your feedback! We rejoice when you are happy and sad with you. To find out your opinion, functional support, feedback from managers and, of course, reviews in stores help you. We monitor and analyze feedback on two platforms. Notes about the lack of useful features are turning functional requirements. Complaints about a long download or application crashes - in terms of performance and stability. Moreover, the more calls, the higher the priority.
To keep the teams up to date with the latest developments, our developers have written a chat bot. Information from the App Store is collected in RSS format, parsed and, in the presence of something new, sent to the Slack channel. In the case of Google Play, a token is requested for feedback through the developer's console, and scheduled reviews also go to chat.
Good reviews are nice, and bad reviews are helpful. Therefore, special attention is paid to negative assessments. For each such case, we look at the platform and version of the application, and try to reproduce it in a test environment. Often the problem is fixed in the latest version of the front, then we advise the user to update. It is not always possible to fix a bug promptly, because some problems are global in nature. One example is the automatic code substitution from SMS. Google has updated its privacy policy and has prevented parsing messages. Fearing removal from the store, SMSki had to be cut out. Then Google proposed a new API, and auto-substitution was returned, but it took a while to resolve the issue.
A cat who is sad every time the user enters SMS with his hands 
But enough about the sad.
There is no more innocent thing in the world than making money
The withdrawal of operations from branches is a global task of banking applications. Itâs good when a client draws up a product, but doesnât go to the office for it. The user saves time; the bank saves resources. At Alpha Business Mobile, cards, deposits, overdrafts and other products are available for ordering. And so that the user knew about this, we made offers in the form of banners.
The task was difficult: you need to earn money, and not to tire the user of banners. Therefore, the fate of the cross on the banner was decided by three groomings in a row (for reference: Google believes that grooming is a grooming of dogs, but in the case of scrum it is a meeting with a discussion of backlog). Asking for confirmation where it is not necessary is bad practice. But here it is important for us that the user does not hide the offer by accident or on the machine. Therefore, before hiding the banner, we ask you to think again.
A business has many desires to consider when implementing the application. Business and IT complement each other: the more features in the application, the more customers. And vice versa. The main thing is not to forget to make sure that the solutions work. When switching between windows and performing actions in the interface, an event counter is triggered, which sends data to Google and Firebase Analytics. So we find out that the user ordered the product after seeing our banner. Or did not order.
But do not do this 
Sources of requirements in the article do not exhaust product analysis. He faces many tasks: prioritization, risk management and so on. However, ratings, feedback and fin. The effect allows you to check that the necessary functions in the application are and do not infuriate the client.
If everything is so, then it worked for a reason :)
All Articles