Challenge

A technician in an industrial field doesn't choose where there's a signal. They go to the equipment, collect the sample, record the data, and move on to the next one. Connectivity is intermittent by definition, and the application needs to function in that scenario.

ALS Global is a world leader in testing, inspection, and certification services, with a presence in over 70 countries. In Brazil, its tribology unit focuses on the analysis of industrial fluids. Technicians visit plants and facilities to collect oil and lubricant samples from operating machinery.

ALS S360 is the application that supports this fieldwork, allowing for offline recording and later synchronization.

The problem lay in this process. The synchronization took 182 seconds to complete. In a routine with multiple data collections per day, this time becomes an operational bottleneck. The technician has to wait, and the analysis cycle starts later.

ALS Global contacted Evo Systems with a clear objective: to fix the slow performance without replacing the application.

Transformation_

S360 was developed in Flutter (Dart). The analysis began with reading the existing code, focusing on the synchronization flow.

The diagnosis revealed two main points.

The first problem was redundant calls. The process triggered multiple requests to the server, repeating operations already performed, generating overload with each synchronization.

The second issue was with the API. Some endpoints were returning more data than necessary, sending complete structures when only specific fields were being used. This excess data consistently increased transmission time.

These problems were not noticeable in everyday use, but they accumulated with each cycle.

With the bottlenecks identified, optimizations were applied directly to the existing code. There were no changes to the architecture or structural modifications that would put the product at risk.

Unlike approaches that prioritize rewriting, Evo Systems focused its intervention on specific causes. Corrections were made in a targeted manner, preserving the rest of the system.

Benefits_

The synchronization time was reduced from 182 seconds to 50 seconds, an improvement of 72%.

This reduction directly impacts operations. Waiting time decreases and the analysis cycle starts earlier, increasing the efficiency of fieldwork.

The implementation was completed in 110 hours, without any changes to the architecture or regressions in the application's functionality.

The results show that significant performance gains can be achieved with accurate diagnosis and targeted interventions, without the need to rebuild the product.

Tools used_

• Flutter (Dart)

Is your field app experiencing a synchronization issue?

Performance issues in offline applications often accumulate silently. The system works, but operates below optimal levels.

Evo Systems analyzes the code, identifies bottlenecks, and implements scope-defined fixes without compromising product stability.