You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First the jargons 😅
▶ QoE (Quality of Experience): This is how users feel about using an app-
• How smooth the app feels when scrolling
• How quickly the app responds to user input
• Whether the app crashes or freezes frequently
▶ QoS (Quality of Service):
It's about the measurable, behind-the-scenes factors that contribute to how well the app runs-
• Crash/ ANR rate
• App startup time
• Network request response times
• Frame rate (how many frames per second your app can render)
• Memory usage and management
• Battery consumption
The graph and explanation illustrate the relationship between Quality of Service (QoS) disturbances and Quality of Experience (QoE).
At low QoE levels (bottom of the curve): When the app's performance is already poor, even significant improvements in QoS (reducing disturbances) only result in small QoE gains. This suggests that when an app is performing badly, it takes substantial effort to improve the user experience.
At high QoE levels (top of the curve): When the app is performing well and users are satisfied, even a small increase in QoS disturbances can cause a sharp drop in QoE. This indicates that users have high expectations for well-performing apps, and any degradation is quickly noticed and negatively impacts their experience.
So, at first we need to monitor various signals to that's making the app laggy. Once we fix them, we need to monitor even more closely now, because we have set better standards for our users. You can read about the massive effort that Reddit had put to do the same (link in the comment).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
First the jargons 😅
▶ QoE (Quality of Experience): This is how users feel about using an app-
• How smooth the app feels when scrolling
• How quickly the app responds to user input
• Whether the app crashes or freezes frequently
▶ QoS (Quality of Service):
It's about the measurable, behind-the-scenes factors that contribute to how well the app runs-
• Crash/ ANR rate
• App startup time
• Network request response times
• Frame rate (how many frames per second your app can render)
• Memory usage and management
• Battery consumption
The graph and explanation illustrate the relationship between Quality of Service (QoS) disturbances and Quality of Experience (QoE).
At low QoE levels (bottom of the curve): When the app's performance is already poor, even significant improvements in QoS (reducing disturbances) only result in small QoE gains. This suggests that when an app is performing badly, it takes substantial effort to improve the user experience.
At high QoE levels (top of the curve): When the app is performing well and users are satisfied, even a small increase in QoS disturbances can cause a sharp drop in QoE. This indicates that users have high expectations for well-performing apps, and any degradation is quickly noticed and negatively impacts their experience.
So, at first we need to monitor various signals to that's making the app laggy. Once we fix them, we need to monitor even more closely now, because we have set better standards for our users. You can read about the massive effort that Reddit had put to do the same (link in the comment).
⭐ If you like this post, please consider starring this repo!
Beta Was this translation helpful? Give feedback.
All reactions