Before creating a mobile application, it was necessary to refine the customer's existing IT infrastructure and introduce a loyalty system.
Step 1. Loyalty program
We have developed an application with a loyalty system and a user's personal account. It solved a sore problem: the fixed cost of SMS.
At this stage, we implemented one of the most important integrations: we created a new backend for mobile applications and connected to it a service for communication with users of the loyalty system.
As a result, the new application completely replaced the physical bonus card, which previously could be lost, duplicated or transferred to another buyer.
Elektrograd customers got the opportunity not to miss discounts and receive personal offers. And Electrograd reduced the cost of SMS mailings, received a new channel for activating customers at no additional cost, solved the problem of user bonuses and personalized relationships with its customers.
Once the loyalty program was launched, Business Culture moved on to the next step—beginning to prepare and detail the architecture and design for the new app.
Elektrograd customers got the opportunity not to miss discounts and receive personal offers. And Electrograd reduced the cost of SMS mailings, received a new channel for activating customers at no additional cost, solved the problem of user bonuses and personalized relationships with its customers.
Once the loyalty program was launched, Business Culture moved on to the next step—beginning to prepare and detail the architecture and design for the new app.
Step 2. Mobile app
How we built the work at this stage: we studied the tasks of the customer, thought through the logic and developed design layouts.
First, we carried out pre-project analytics, during which we studied the needs of the user and formed a list of tasks that the application was supposed to solve: a convenient personal account, work with bonuses, search and selection of a store by address and proximity, ratings and reviews, control of write-offs of funds and bonuses.
First, we carried out pre-project analytics, during which we studied the needs of the user and formed a list of tasks that the application was supposed to solve: a convenient personal account, work with bonuses, search and selection of a store by address and proximity, ratings and reviews, control of write-offs of funds and bonuses.
Next, it was necessary to create our own design with a friendly interface, convenient catalog search using various filters, a shopping cart, payment and delivery.
For many offline retailers of this size, this is a difficult task. Difficulties arise due to the large number of legacy IT solutions in the infrastructure: product catalogs, order processing systems, warehouse and logistics management solutions, checkout services.
Together with the client, we decided to significantly save the budget and reduce the time needed to develop a separate mobile application. Therefore, we returned to the mobile version of the site and worked on a native and completely imperceptible transition to the site from the mobile application.
For many offline retailers of this size, this is a difficult task. Difficulties arise due to the large number of legacy IT solutions in the infrastructure: product catalogs, order processing systems, warehouse and logistics management solutions, checkout services.
Together with the client, we decided to significantly save the budget and reduce the time needed to develop a separate mobile application. Therefore, we returned to the mobile version of the site and worked on a native and completely imperceptible transition to the site from the mobile application.
Development
The project had tight deadlines: from the start of development to the agreed release date, we had only 3 months. During this time, it was necessary to draw a design, make a backend, a mobile application and publish them in the Google and Apple stores.
We worked on Scrum, in two-week sprints, after which we received feedback from the customer and made a list of tasks for the next sprint. This allowed us to more effectively manage the functionality of the project: test the operation of new features and evaluate how much they improve the product. As a result of feedback from users, we constantly added a certain value to the product, only the best features: recommendations, reports, instructions for clients.
Three sprints were enough to get the first working version of the application. We have implemented high-quality code in such a way that as the load on the system grows, it will be easy to scale server hardware and architecture.
In order not to waste time, it was important to avoid downtime in the development of a mobile application, so the design went functionally one iteration ahead.
To implement the functionality efficiently and without wasting time, mobile developers must receive:
1. Mobile application screen designs;
2. Efficient API from the server side;
3. Description of the task.
We described the terms of reference for the product in advance, so there were no issues with setting tasks for the development teams.
It remained to work out the design issues and the server API.
We worked on Scrum, in two-week sprints, after which we received feedback from the customer and made a list of tasks for the next sprint. This allowed us to more effectively manage the functionality of the project: test the operation of new features and evaluate how much they improve the product. As a result of feedback from users, we constantly added a certain value to the product, only the best features: recommendations, reports, instructions for clients.
Three sprints were enough to get the first working version of the application. We have implemented high-quality code in such a way that as the load on the system grows, it will be easy to scale server hardware and architecture.
In order not to waste time, it was important to avoid downtime in the development of a mobile application, so the design went functionally one iteration ahead.
To implement the functionality efficiently and without wasting time, mobile developers must receive:
1. Mobile application screen designs;
2. Efficient API from the server side;
3. Description of the task.
We described the terms of reference for the product in advance, so there were no issues with setting tasks for the development teams.
It remained to work out the design issues and the server API.
Design
We started designing from the very beginning of the project. During the first sprint, they created prototypes - black and white layouts of the application screens - and agreed on them within the team before showing them to Electrograd. We followed this same practice throughout the project.
The client was very attentive to the design work and actively provided us with feedback. We managed to harmoniously fit into the existing brand book of the company and coordinate the design.
We conducted several UX studies, which helped us formulate the main requirements for the application design. It was important for us to make a thoughtful and user-friendly interface, with end-to-end navigation.
We conducted several UX studies, which helped us formulate the main requirements for the application design. It was important for us to make a thoughtful and user-friendly interface, with end-to-end navigation.
The main difficulty in working on the server part was that we actually integrated with the corporate information and analytical system "Electrograd".
The following modules and services were developed for the backend:
The following modules and services were developed for the backend:
1. Service for interaction with the customer's information system, queuing system for synchronizing and updating data.
2. API request filtering system - allows you to flexibly pass parameters-values of models and receive the necessary data.
3. Service for working with DaData - it helps to get information about the distance between the current location of a person and the coordinates of the nearest stores.
4. Convenient system for working with API requests.
5. Push notification mechanism - reminds the user of the application about promotions, bonuses or offers to take a survey offered by the company.
6. Mechanism of email notifications.
2. API request filtering system - allows you to flexibly pass parameters-values of models and receive the necessary data.
3. Service for working with DaData - it helps to get information about the distance between the current location of a person and the coordinates of the nearest stores.
4. Convenient system for working with API requests.
5. Push notification mechanism - reminds the user of the application about promotions, bonuses or offers to take a survey offered by the company.
6. Mechanism of email notifications.
Mobile app features
Additional functions
Final step: delivery of the project
The delivery of the project itself took place in several stages. Each stage is the implementation of several ready-made functional blocks. Such a process was not a surprise: we planned all the stages before the start of work. From the first days of work, the team had access to the project plan, everyone clearly knew the deadlines for the delivery of each functional block.
Testing of the project took place before each stage of delivery. QA specialists are involved in the development process from the very beginning. During the implementation of any business feature, after the developer has finished working on it, it is always checked by a quality control employee. If defects are found, the feature is returned for revision.
Also, before the delivery of each stage of the mobile application, we conduct a full test of the entire product. Such a system allows you to approach the release with a high-quality product - in this case, its debugging will take a reasonable time.
Today, the application is already in the stores and available to users. With its help, Electrograd customers can get all the necessary information about their bonuses, choose the right store by location. In the application, you can view the promotion, go to the purchase of goods, leave a review. All this makes the life of Electrograd customers easier and more comfortable. The company also reduces the cost of SMS, reduces the burden on administrators, and manages customer loyalty, increasing the profitability of the entire business.
Testing of the project took place before each stage of delivery. QA specialists are involved in the development process from the very beginning. During the implementation of any business feature, after the developer has finished working on it, it is always checked by a quality control employee. If defects are found, the feature is returned for revision.
Also, before the delivery of each stage of the mobile application, we conduct a full test of the entire product. Such a system allows you to approach the release with a high-quality product - in this case, its debugging will take a reasonable time.
Today, the application is already in the stores and available to users. With its help, Electrograd customers can get all the necessary information about their bonuses, choose the right store by location. In the application, you can view the promotion, go to the purchase of goods, leave a review. All this makes the life of Electrograd customers easier and more comfortable. The company also reduces the cost of SMS, reduces the burden on administrators, and manages customer loyalty, increasing the profitability of the entire business.
The Electrocity application in Google Play or App Store
Do you want a mobile app? Call +7 (3412) 901-907 or write to office@businessculture.ru, we will be happy to study your task, advise and make a quality product!
Do you want a mobile app? Call +7 (3412) 901-907 or write to office@businessculture.ru, we will be happy to study your task, advise and make a quality product!
