Making a better view of a public services
to clarify padle court availability from their API
My mock-up for this webapp
Playing weekly padle with some friends,
We always need to go on a website to book courts, but somehow, this website is pretty badly done, requiring 10 clicks to check all availability.
While checking availabilities, I realized my browser was making calls to an open API that would easily give me all infos about those courts.
I then had the idea of making a small page that would gather datas from all courts, and display them on the same page.
Here is the result :
In a near future, the idea is to display some weather data, to ease the booking decision : If it’s too hot, too windy, early nighttime, or just rainy !
Why not also a notification system for creating alert if only one court left for a particular time, or if only few hours of good weather planned in a week..
Another nice implementation would be to book court automatically.. but let's see.
Why all that ?
This idea is a perfect exemple between Ux Design and coding. It’s a perfect case of how to adopt and implement coding at a personal scale. I even chose this project as a use case for a little coding workshop - here more details about that, but we found out it was a bit too complex for a beginner’s workshop.
When the weather will be implemented, I may even sell this code to the padle court itself.
If you have any suggestions, contact me via What`s App!
