The UI on /centres is confusing and can make people feel that the page isn't just gonna load. This should be resolved by reviving the Skeleton cards so people feel that there's still hope.

#westillloveyou

The Pagination Component provided by Ant.design is not SEO friendly which can cause problems with indexing. Something that could limit the usage of this information

There are reported cases of Inaccurate maps. These need to be fixed, in order to reduce the chances of users being misguided.
Here are our options to fix the maps

• Check all the maps one by one and resolve them to accurate maps.
• Perform an automated check with string comparison and see if the user specified is closely matching or not, if not closely matching resolve to nearest city/district.

These are two proposals. The first one would guarantee less errors but there are low chance of human errors.

Second Approach

Considering the second approach would make it simpler for us to implement, however the edge cases could be frustrating and we might need to look for them.

The following edge cases are really troubling.

• Center is in the same district as the result provided but they are not the same. This harms the trustworthiness of the data source.

This one case requires a hybrid approach, where a score is assigned to each VaccinationCentre for it's Google Api Response and if the score is low, we can personally take a look. This has a guarantee of providing us better results while enabling the Nearest Vaccination Centres use case that I have planned.