Replace Current Loader with the Skeleton Component

[abhayymishraa]

Is your feature request related to a problem? Please describe.

Currently, the website uses a loader to display components while content is being fetched or rendered. While functional, the loader is good but we can use skelton instead of that as it will look amazing when the state is loading!!!

---

Describe the solution you'd like

Implement the Skeleton component as a replacement for the current loader. The Skeleton component provides a more visually appealing and professional loading state, elevating the overall look and feel of the website.

---

Describe alternatives you've considered

1. Retaining the current loader

2. Creating a custom skeleton loader: Although this would work, it would require additional development time and effort compared to using the ready-made ShadCN Skeleton component.

---

Some Examples

1. 
2. 

---

Additional context

• The ShadCN Skeleton component can significantly improve the perceived performance of the website by offering a sleek and modern loading experience.
• Here’s the documentation for ShadCN Skeleton.
• Incorporating this feature will enhance the overall user experience, ensure aesthetic consistency, and align the website with current UI/UX best practices.

[abhayymishraa]

I would like to discuss it first before implementing!!!

[arkid15r]

This sounds like a good idea.
@Rajgupta36 @harsh3dev @yashpandey06 @Yashgupta9330 any opposite opinions?

[yashpandey06]

@arkid15r

Introducing a skeleton loader is a great idea, especially if it helps address specific challenges in the application.

High Latency in Fetching Data: When there is a noticeable delay in retrieving data, a skeleton loader can significantly enhance user experience by providing immediate visual feedback.
Are we noticing any delay in Algolia ?

Dynamic Content Changes Based on User Interaction: In scenarios where content updates frequently due to user actions, a skeleton loader ensures a smooth transition, reducing the perceived waiting time.

If these challenges exist in the application, incorporating a skeleton loader would make a strong case for its implementation. That said, even without these issues, adding a skeleton loader can still be valuable as a UI enhancement to improve the overall user experience.

Let's wait for others views also !

[harsh3dev]

@arkid15r @abhayymishraa Yes I was also thinking of the same feature.

[abhayymishraa]

@arkid15r could you assign this issue to me ?