The parking ticket machine might make things deliberately slow because the printer needs to warm up or something.

Maybe it needs up to 5 seconds to warm up if it's in deep sleep, so splitting this into three 2s periods provides the least frustrating user experience.

As soon as you need to deal with real hardware things always start to get complicated.

More likely it's warming up the mobile comms state machine, without checking if it's actually needed. Unlike mobile phones which try to keep their data connection somewhat live, IoT things often drop back to the lowest state to save power (and possibly SIM cost)

https://www.sharetechnote.com/html/Handbook_UMTS_RrcStateCha...

And programmed on BASIC Stamp on some godforsaken discontinued hardware. :)

More likely it was written by some cheap interns and requires getting unique ticket id from server for "controlling" purposes. Then there is one part time employee (met him, small talked a little) who goes from car to car with terminal and checks if those tickets are valid. I have some experience with gprs systems here, so probable flow:

- press button

- gprs roundtrip about button press with "no payment, free ticket" (2s)

- machine shows "printing ticket", asks server what to print (aka the idiotic unnecessary step)

- gprs roundtrip (2s)

- printer warmup? (?s)

- prints ticket

> to save power (and possibly SIM cost)

Nope, costs per sim are monthly per card, until you hit the data limit, then per MB. Those machines typically have enough power to keep connection alive.

More likely a parking machine needs to be accessible to all users, and some people get confused when technology works too fast.

Perhaps if you get confused by fast things you shouldn't be driving?

Perhaps if you're driving, the things around you need to give you time to react to other things around you. Fewer things are more frustrating than getting honked at because you pressed a button, then got distracted by a car pulling up which you needed to look at to be aware of, then missed the printer asking if you want a receipt, and then having to press another button to talk to someone to ask for a reprint which, of course, holds up the line of cars growing behind you while someone gets paged to come to the kiosk.

So you wrote this new scenario where the parking ticket machine does NOT print a ticket unless you confirm it (after you already pressed the button)? And you get... mildly inconvenienced by some honking. Yeah you shouldn't drive.

No, not printing the ticket isn't the scenario. Not printing the receipt for payment is the scenario.

It's not a new scenario. It happened to me.

I'm not mildly inconvenienced by some honking. That's just aggravating. I'm inconvenienced by having to call to get a receipt.

The cell providers also get really opinionated about how much / how often your IoT device talks to the cell towers when they seek to approve your device.

Even if it's free, doesn't it have to put the ticket cookie in some database?

Other machines can do it with single roundtrip (2s pause between pressing and printing). That one single manufacturer is slower than everyone, but hey, maybe the app (which requires location, phone number and vehicle number) will be faster?

Finance can be fast if wanted, and I don't think there' s a deliberate delay in Wise's animation.

In my country, we have a similar system, and before my bank sends me a push notification about the outgoing transfer, the push notification for incoming transfer pops up for most of the time. The delay between push notifications rarely goes above 2 seconds.

Ours has an upper limit to prevent abuse of the system, but you can't beat instant, actually.