Update 04 March
Well, this dev team has once again screwed up their app. The facility scheduling screen doesn’t render anything — most likely because it’s a cheaply-made web app, and they enabled a modal “cookies ok?” function that doesn’t actually appear on screen. Same for the website but you can overload it and get there at least. Now deal with the slow site.
Poor dev practices coupled with apparently no QA at all. Nice.
Without a doubt the worst piece of garbage I’ve ever used on my iPhone — especially egregious as I’m forced to because the management of this club didn’t bother to perform due diligence when selecting this mess. This is a “web app”, not a real app — in other words, an app done on the cheap. Merely a front end to their website, which is slow and buggy in itself. Refreshes can take upwards of 30 seconds at times. The user flow is terrible, response is flabby, and feedback is mostly “mystery meat”. While there are reservation libraries out there to use, this developer clearly chose to roll their own because hey, how hard could it be to write code for reservations? Well, it’s not trivial. So now we have an environment where the second person to request a court replaces the first person while both people see they have a reservation — until they arrive and have to negotiate on the court, some of them having driven an hour or more to get there. And now a new feature: the courts you’ve reserved show no date or time, so if you have multiple courts booked out over the next few days, you have to guess which is which. This developer is incompetent — but the people at the club who selected this app are really to blame for enabling the developer to inflict this stuff on their members.