In a restaurant, there are moments when everything has to work. The pass is full, orders keep coming in and the team needs the POS to be there — no drama, no surprise screens.
That's why we've improved the Last.app update system, so new versions install more intelligently, without interrupting operations during peak hours.
Updates that adapt to the restaurant's pace
Until now, updates could appear based on when a device was switched on or connected — and that sometimes meant bad timing. Very bad timing.
With the new engine, the POS is better at detecting when there's activity and when it can update without getting in the way. Fewer unexpected interruptions, more continuity during service.
On Android and iOS, almost invisible
When a new version is available, the user will see a notification.
From there, the system waits for the app to be idle before applying the update. No sudden closures, no cutting an action halfway through, and no appearing right when you're cashing out a table.
On Windows, more room to decide
On Windows, the app needs to close to update. So now you can postpone the update for 1 hour, up to a maximum of 4 times.
Additionally, if the POS detects a moment of inactivity, it will take the opportunity to update automatically — without the user having to do anything.
Basically, less noise in the middle of service
This change isn't just about updating better. It's about letting you work better.
Fewer interruptions.
Fewer surprises mid-service.
More peace of mind for the team.
Because technology should adapt to the restaurant's pace — not the other way round.