March 2022 Summaries

When testing a mobile SDK, it's essential to differentiate between testing the SDK itself and testing a mobile app that has the SDK integrated. Mobile SDK testing focuses on ensuring the core functionality of the SDK works under diverse scenarios while minimizing its impact on the host app's UI, UX, and performance. This requires considering factors such as platform and version support, locale adaptation, resource efficiency, and compatibility with other SDKs. The primary goal is to make developers' lives easier by providing a simple integration process, rock-solid stability, and high-quality code that enhances the host app's features without compromising its performance or user experience.

Mobile SDK testing is distinct from mobile app testing, as it involves ensuring the SDK's core functionality operates seamlessly with minimal impact on the host app's UI, UX, and performance. While mobile app testing focuses on functional, environment, and non-functional testing to ensure the app works as expected, SDK testing demands a higher quality standard due to its integration into various apps targeting a wide range of devices and OS versions. Challenges include maintaining stability, ensuring easy integration for developers, and adapting to different locales and environments without negatively affecting resource consumption or other SDKs in the host app. An effective SDK should enhance the host app's features unobtrusively, behaving as an integral part of the app rather than as third-party code.

Instabug provides detailed information in crash reports, including exception name, app frame, filters for viewing a subset of data, and a wealth of details about the devices and environments where the crash occurred. The report also includes stack traces with highlighted app frames, actions sidebar to change status and priority, and attachments such as custom extra files. Additionally, Instabug offers session profiler graphs showing device environment details before the crash, logs including console logs, Instabug logs, user steps, network logs, and user events. This information enables developers to quickly identify and fix crashes, understand their impact on users, and prioritize them accordingly.

Monitoring is the process of ensuring an application's system operates as it should, tracking metrics such as speed and scope. Observability, on the other hand, collects data from individual user sessions to provide a wealth of information that allows developers to devise solutions much quicker before users bounce or give up on their app entirely. While monitoring can tell you when an issue occurs, observability helps identify precisely what's causing the problem and how to fix it. Both tools complement each other and are essential for maintaining a well-functioning app that consumers actually use. Observability provides more context about system problems, analyzing user sessions to give actionable insight into issues like session replay, device battery, network connectivity, and more. The key differences between monitoring and observability lie in their approach: monitoring is limited by the predictability of system failures, while observability compensates for this limitation by collecting data from individual user sessions. Observability tools collect three types of data: metrics, logs, and traces, which provide a wealth of information to help developers identify problems and devise solutions quickly.

Luciq's crash reports provide comprehensive insights to help developers quickly identify and address app crashes. These reports include detailed information about each crash occurrence, such as the exception name, app frame, and an overview of affected users and occurrences over time. Developers can utilize extensive filters to narrow down crash data by app version, date, device, and user attributes, among other parameters. The crash details section offers insights into the environments and devices where crashes occur, while the stack trace highlights app frames to aid in pinpointing the offending line of code. The actions sidebar allows developers to manage crash statuses, assign tasks, and communicate with affected users. For a deeper investigation, the occurrences page provides granular details like device environment snapshots, repro steps, and session profiler graphs, which illustrate device conditions leading up to the crash. Additionally, extensive logging captures console, user, network, and custom events, equipping developers with the necessary data to resolve crashes efficiently.

The first line of code in Instabug's dashboard was written in 2014, when most of the tools and concepts used today did not yet exist or were not very mature. At that time, AngularJS was a good choice for building the dashboard due to its popularity and stability. However, since then, web development has evolved significantly, and newer frameworks like Vue and React have gained popularity. Google stopped supporting AngularJS in December 2021, making it difficult to maintain and update. Instabug decided to migrate from AngularJS to a new framework, considering factors such as time needed for initial setup, compatibility with animations, and support for dependency injection. After evaluating options, they chose Vue over React due to its better configuration, code writing ideology, market strength, and compatibility with certain features. The migration was done incrementally, dividing the system into smaller components and migrating a small piece at a time to reduce expenses and risks. NgVue library played a crucial role in integrating Vue components within the AngularJS application. The migration process enabled Instabug to use the latest technologies without sacrificing maintenance and development speed, allowing them to continue growing and scaling their product.

We adopted front-end test automation to improve the efficiency of our delivery process, enabling us to test the application on a high level while adhering to our core principle of delivering quickly and efficiently. We chose Cypress as the best fit for our project due to its ease of use, configurability, and active community. Automation played a crucial role in helping us migrate and refactor our codebase safely, saving time and effort previously spent on manual testing. Integrating automation into our development process simplified the release process and made it easier to manage, while adding test automation to our CI/CD pipeline will help us automatically run our test suite as part of the build process. Front-end test automation has become a crucial part of our release process, preventing bugs from going into production and ensuring that new features do not break old ones without sacrificing speed.

As the complexity of their application increased, the team decided to implement automated front-end testing to enhance their delivery process while maintaining efficiency. Automation allowed them to test both simple and complex scenarios in a browser environment, simulating real user interactions and ensuring changes did not inadvertently introduce bugs. After evaluating several technologies, the team selected Cypress for its ease of learning, configurability, and active community support. Integrating automation testing into their workflow facilitated safe code migration, reduced manual testing effort, and accelerated their release process by integrating test automation into their CI/CD pipeline. The integration of automation into their development process, including combining their main application and automation repositories, simplified management and release. The adoption of Cypress played a significant role in confidently migrating to VueJS, discovering bugs early, and optimizing testing efforts for larger applications, emphasizing the importance of automation for freeing up resources for more critical tasks.

Luciq's transition from AngularJS to VueJS highlights the evolving landscape of web development and the strategic decisions companies must make to stay current with technology. Originally, AngularJS was chosen for its reliability and Google's backing, but the cessation of its support in 2021 necessitated a change. After evaluating Angular, React, and Vue based on setup time, compatibility, and developer preferences, Vue was selected for its simplicity and modern features. The migration process is being tackled incrementally, allowing Luciq to continue developing new features without disrupting existing operations. This gradual approach, supported by the NgVue library, enables the integration of Vue components into the current system, balancing the need for modernization with the demands of a fast-paced growth environment.

Application observability is a step up from traditional mobile application monitoring, providing developers with unprecedented insight into their app's performance. It gives them the full context of sessions where errors occurred to quickly fix issues and identify areas of poor performance before they cause any problems. Observability helps fix crashes faster by capturing more comprehensive information like network logs, repro steps, session profiles, and more about each crash. It also boosts app startup times, identifies and fixes all exception types, including NDK crashes, C++ crashes, SwiftUI exceptions, and network crashes. Additionally, observability helps identify and fix OOM and ANR errors, measures forced restarts, accelerates workflows, reduces alert fatigue, minimizes the need for error logging, and ultimately improves app user experience.

The mobile app industry is facing high expectations from users, who now demand not only useful features but also flawless performance. With the rise of mobile usage, apps are becoming indispensable tools in people's lives, and poor performance can lead to swift user churn and negative brand perception. Developers must prioritize their users' experience and consider factors beyond just feature development, such as technical debt, crashes, slow loading times, and unresponsive UIs. By optimizing app performance management strategies and using the right tools, developers can deliver a better user experience, increase loyalty, and drive business growth.

The mobile app industry is fiercely competitive, requiring constant innovation and high performance to meet evolving user expectations, particularly as mobile usage has surged post-COVID. Users demand not only innovative features but also flawless performance, with slow or crashing apps leading to high user churn and negative brand perception. Studies indicate that poor app performance is seen as disrespectful by users, who are quick to abandon apps that fail to meet their standards, often discouraging others from using them as well. However, there are significant rewards for apps that perform well, with users willing to spend more on such apps, as evidenced by brands like ALDO experiencing increased revenue from fast-performing apps. To succeed, developers must prioritize both eliminating crashes and optimizing app responsiveness and load times, supported by effective app performance management strategies and monitoring tools that provide real-time visibility into performance issues.

Users are paying more attention to how their apps perform, and higher app quality outperforms low app quality. Application performance monitoring (APM) is a key way to improve app performance and user experience by identifying performance issues such as slow screen transitions, crashes, or network issues before they affect users. APM tools allow teams to easily identify and diagnose performance problems, making it easier to fix them before they become major issues. Apdex scores are used to measure the overall user experience with an app, ranging from 0 (unacceptable) to 1 (excellent), with higher scores indicating better performance. Instabug APM provides a range of features, including customizable metrics, UI hang monitoring, and network issue detection, allowing teams to gain insights into their app's performance and make data-driven decisions to improve it. By following mobile APM best practices and using tools like Instabug, teams can proactively monitor and fix performance issues before they become major problems, resulting in a better user experience and improved app quality.

Mobile observability is crucial for creating a positive user experience in mobile apps. With the growing reliance on smartphones and increasing user expectations, it's essential to ensure app performance and reliability. Observability provides actionable insights into system state, allowing developers to identify issues before they arise and improve overall app performance. This can help mitigate memory issues, faster app launch times, and WebView UX problems, ultimately leading to a better shopping experience. By leveraging mobile observability tools like Instabug, developers can collect data from individual user sessions, debug issues quickly, and make informed decisions to optimize their app's performance and user experience.

Mobile observability plays a crucial role in enhancing user experience by providing deep insights into app performance beyond traditional crash reporting. As users increasingly rely on mobile apps in their daily lives, especially post-COVID, they expect seamless, reliable, and fast-performing digital services. Mobile observability allows developers to anticipate and address performance issues like memory errors and slow app launch times, which could otherwise frustrate users and drive them to competitors. This approach also aids in identifying problems such as WebView failures and optimizing shopping experiences by analyzing user sessions and pinpointing specific areas for improvement. Tools like Luciq enable developers to gather actionable insights, debug efficiently, and maintain a high-quality user experience, ensuring that the app remains competitive and trustworthy in the eyes of consumers.

Mobile application performance monitoring is crucial for ensuring high app quality and user satisfaction, with tools like Luciq APM offering valuable insights into performance metrics such as Apdex scores, UI hangs, app launch times, and network issues. The Apdex score serves as a universal measure of app performance, allowing developers to target specific improvements by monitoring new releases and setting custom thresholds for key metrics. Luciq APM facilitates the diagnosis of UI hangs and app launch delays through detailed filtering and customizable traces, enabling developers to quickly identify and address performance bottlenecks. Moreover, by analyzing network patterns and client-side failures, Luciq APM helps distinguish between server-side and client-side issues, allowing teams to assign problems to the appropriate departments efficiently. Overall, proactive mobile APM practices ensure continuous performance enhancement, thereby preventing potential user dissatisfaction and bug reports.