-
Notifications
You must be signed in to change notification settings - Fork 44
Description
The current application relies on blank screens or basic spinners during data fetching, which results in a poor and outdated loading experience. Users often face uncertainty about whether the app is working correctly, while abrupt content pop-ins create jarring transitions. On slower mobile connections, this issue is even more noticeable and negatively impacts usability.
Problems with Current Approach
Blank screens or spinners provide no context about upcoming content.
Users perceive the app as slower due to sudden content appearance.
Creates anxiety and reduces confidence in the app’s reliability.
Inconsistent loading states across sections cause confusion.
Weakens the mobile experience on slower networks.
Why Skeleton Loading
Modern UX standards now favor skeleton loading over spinners:
87% of top applications use skeleton loaders instead of spinners.
Users perceive skeleton loaders as 23% faster than traditional loading indicators.
Provides a smoother, more professional, and trustworthy experience.
Proposed Solution
Implement skeleton loading components across the app to replace existing spinners and blank states. Skeletons should:
Mimic the layout of the final content for better user predictability.
Provide a consistent and professional loading experience across all modules.
Improve perceived performance, reduce uncertainty, and enhance mobile usability.