


first iteration
mobile
release
Business context
AutoLogg has been the go-to digital trip logbook in Austria since 2010. Thousands of drivers use it daily. The in-house team was fully booked supporting those users. There was no capacity left to rethink the product, and the product needed rethinking. The UI looked its age. Core flows had grown heavier with each release. New users were dropping off before they ever logged a trip.
AutoLogg didn’t need extra capacity. They needed a partner who could take ownership of the transformation without becoming overhead
Rebuilding the product experience
Senior ownership from day one
%201.avif)
AutoLogg 2.0 shipped as a modern Flutter app, without adding load to in-house team
%201.avif)
AutoLogg 2.0, a redesigned mileage tracker with fleet functionality and automated trip logging
.avif)
Redesigned trip logging to cut steps and add immediate feedback, so it feels quick instead of form-like.
Added auto-assign and smarter defaults so users don’t have to enter the same details every time.
Implemented NFC pairing in the frontend and validated it with real-world testing using physical tags.
Added map-based views and live tracking so drivers and admins can see a trip’s route and current status.
Introduced fleet mode with admin controls for users/roles, assignments (vehicles + trips), issue tracking, and reporting.
Enabled audit-ready templates that users can generate quickly and send directly from the app for tax and compliance needs.
A new UI/UX foundation
for a new AutoLogg
AutoLogg 2.0 launched with a transformed UI/UX foundation and a unified Flutter frontend. The app is easier to pick up for new users and easier to maintain across web and mobile
.avif)
.avif)
.png)

.avif)

.avif)
.avif)
.avif)