App performance — a pain?
App performance is a silent killer — we are always conscious about it but we start to act when it hits hard on the business & user experience.
Here are some reviews of Paytm latest version:
Apps trying to strike between UI & UX:
Users are always excited about the new features and UI changes but the UI tends to fade away over the days or weeks. Users are judging the apps based on how quickly they can get the job done, on the engineering front — all the beautiful icons, shades, and other UI by the designers get integrated in a very short period of time without having to validate the impact of the app performance.
Let’s look at why the app performance isn’t thought through well during such exercise:
Tools and coverage, performance on the server-side is about optimizing the API response time dynamically over the traffic, and constant updates without having the users know about the changes that are happening. However, the client-side is a tricky piece. Developers are often equipped with 1–2 devices (one of their own as well) to look into the changes and use Android / Xcode for monitoring app performance which often just covers only a few %age of the updates being pushed.
Also, developers focus on the areas where the updates are being made — Not the entire flow and use case. It’s the testers who need to run through the regression or automation for that matter.
In either of this equation:
- Developers are not covering the end-to-end use cases
- Testers do not have a tool for monitoring app performance
We are missing a huge opportunity to solve this particular gap. In the recent webinar — where I spoke about app performance addressing the current state of app performance monitoring and why we fail to catch some important performance parameters to avoid such obvious pain.
What takes the biggest hit and how can we add performance as part of our dev-release / QA & Beta cycle.
We had faced a similar set of challenges with most of the companies building apps.
this isn’t a blocker because people started to live with the pain.
Here are some tools and process you can use to capture performance metrics:
At Perfachhi, we started to experiment and learn about solving this particular problem of having to silently integrate something that keeps churning out performance data regardless of the stage the app is in. But the goal was to also monitor the app before going to the playstore.
Get your free trial here!
We focused on how can we help developers from getting some important aspect of performance during this phase:
- Start-up times
- Memory leaks
- API calls
- Frame drops
- Method calls
- Network usage
and also how they overlap with each other.
Monitoring performance metrics pre-prod adds a tremendous amount of value by either being aware of the issues or solving them before going live. Engineering teams can adapt to tools that make it easier to pinpoint issues and help gather information through the testing cycle.