Helping drivers: how we created a smart car control system
Smart system for remote car control. Works on iOS and Android.
3 years
of work on the project
Task
The client bought a new car. He was afraid that he might be broken into or stolen. If he leaves the car in a parking lot in a large shopping center, he will not immediately notice that it is missing. For example, he will not hear the alarm and will call the police late when the hijackers will have already disappeared.
The car enthusiast wants to make driving easier. For example, to warm up the engine in advance on a winter morning, if it is -30°C outside.
The car owner wants to save on gas. He does not know what to change – his driving style or the travel routes. Fleet owners and taxi aggregators need to monitor their drivers’ trips. The navigator helps do this, but drivers may turn it off or refuse to send geodata.
Solution
System “Smart control” allows users to control the car from a distance, for example, start the engine, open doors or the trunk, etc. Works through the GLONASS system.
Provides several levels of protection against theft and helps to track where the car is, whether its doors, windows and trunk are open, etc. It also collects statistics on driving styles via a mobile application.
To start using the system, users need to register their car with a dealer and download the app. It has two roles: the owner of the car and the driver who temporarily drives it, for example, rented or uses a company car. There is a program for car fleets that can link several cars to one account.
Development Process
The development process lasted 3 years. There were no terms of reference for the application. The backend was also on the customer’s side. We worked almost in the blind. Now the application is being tested, and the verification is carried out in three stages. First, our QAs use the app without a car. Then the project manager and analyst test the cases on the vehicle. At the final stage, the client conducts their own testing. The results are shown to the management.
The Hardest Part
Working without terms of reference was the hardest part. During the project, the client provided information about changes in the specification, design and logic of the mobile application. There were many changes in the process. For example, we were working on one solution, and the client told us what to do differently. Or the backend developers rewrote something, so we had to adjust. Therefore, there were quite a few bugs in the application.
How we solved these tasks
We made the functionality using a spec for backend integration. We passed data according to the specification and watched how everything worked. Then we checked it on a test car: do the doors, trunk, etc. open. The client has already created a technical specification list, according to which we will make adjustments. Now it is possible to see where the logic has changed and how much it will affect adjacent blocks.
Yuri Egorov
“ In this project, we realized that the most important thing is the presence of some terms of reference. This helps understand the product as a whole and eliminate bugs. The second point is if we are making a device management system, the client should provide this device. Otherwise, it is a game in the dark. “
Technology Stack
Android SDK
Language: Java, KotlinAAC (Android Architecture Components)
Dagger
Retrofit
RoomRxAndroid
Firebase Crashlytics
Material Components (Material Design)
AlamofireSwiftRxSwiftUI Kit
MapBoxResults
So far, work continues on the “smart control” system. Once a product is released to the market, dealers will sell it as an add-on for vehicles.
The system collects data on mileage, travel time, fuel consumption, etc. This information will help save on gas and change driving habits to safer ones. The system report can be sent to the insurance company and get a discount on insurance policies.
