Today we will study food delivery applications. These applications have multiplied in the last three years. In France, two leaders share the majority of the market:UberEats and Deliveroo. We decided to compare these two challengers to confront them on the following criteria: their energy consumption, their amount of exchanged data as well as their busy memory.
From the point of view of the app weight, Deliveroo is the featherweight. Indeed, its weight (22 MB) is 1.4 times lower than that of UberEats (31 MB).
From the beginning of the match, UberEats takes a clear advantage over his opponent with a launch that consumes 13% less battery. He manages to maintain his advantage during the decisive phase of this match, which consists of ordering a meal (-2.5%). The confrontation ends with two rounds of observation of the rest phases of each opponent, during which the two competitors are tied.
Over the whole match, UberEats wins on the points against Deliveroo that resists well.
Note that we are dealing here with two “heavyweights” who will both mark your battery their footprint!
And the winner is…
For this very first fight, the match is tight but UberEats wins 15.7 mAh at 16.2 mAh in front of Deliveroo, consuming nearly 3.5% less energy. Note however that the Deliveroo app is lighter to download and consumes less data - so if you have a small data package or unstable connection, it can be interesting.
For those who like numbers
|Application||Version||Downloads||Playstore Grade||App weight (MB)||Exchanged data (MB)||Memory (MB)||Energy consumption (mAh)|
|Deliveroo||3.4.1||5 000 000+||4.2||22||3.35||218.85||12.02|
|UberEats||1.201.10002||50 000 000+||4.2||31||3.66||227.74||11.72|
The measurements were carried out by our laboratory on the basis of a standardized protocol, respecting a specific user scenario (launch of the application, selection of a delivery address, scroll on the pages of choice of restaurants and selection of a restaurant, scroll on the page of the dishes and add in the basket). The other scenarios are the launch of the application (20”), inactivity in the foreground (20”) and inactivity in the background (20”).
Receive our newsletter every two months with a selection of our best articles dedicated to applications efficiency.