February 2018 Summaries

We've released several new features in the bug reporting product, including alerts for the three most common network request errors: network request failures, network requests that timed out, and network requests that took too long to complete. These updates aim to address common pain points faced by app developers when fixing bugs and crashes. We've also introduced Extended Bug Reports, which include sections prompting users to detail steps taken to reproduce a problem, actual results seen, and expected results. Additionally, we've improved in-app notifications to appear at the bottom of the screen with "Dismiss" and "Reply" buttons, allowing users to read information on their own time or reply directly from the notification. Our crash reporting product now includes features such as automatic severity classification and the ability for developers to reply to end-users who experienced a crash. These updates aim to improve user engagement, retention rates, and overall app stability.

The bug life cycle is the process by which bugs are discovered, verified, prioritized, assigned to developers for fixing, and ultimately resolved or closed. The typical bug undergoes three phases: Bug Understanding, where it's verified as a valid bug; Bug Triage, where its priority is determined and assigned to a developer; and Bug Resolution, where the cause of the error is identified and fixed. Within these phases, various statuses such as UNCONFIRMED, CONFIRMED/OPEN, IN_PROGRESS, RESOLVED, VERIFIED/CLOSED, and RE-OPENED are used to track progress. Tracking metrics like Closed vs. reported bugs, Average time to fix, Bug distribution by severity, Bug distribution by module, Bug distribution by root cause, and Bug leakage provide insights into the effectiveness of the bug tracking process and help identify areas for improvement. A well-designed workflow and tools can facilitate efficient handling of bug reports, while a culture that encourages communication, clear assignment, and accountability is essential for successful bug management.

The text outlines the process of managing app bug reports, emphasizing the importance of understanding the bug life cycle, which typically includes phases such as Bug Understanding, Bug Triage, and Bug Resolution. Each phase involves steps like verifying the bug's validity, prioritizing it based on severity, and assigning it to the appropriate developer. The document highlights the flexibility of workflows in bug tracking systems like Bugzilla and JIRA, which can be customized to fit the specific needs of different projects. It also discusses the significance of tracking metrics such as closed vs. reported bugs, average time to fix, and bug distribution by severity, module, and root cause to identify areas for improvement in the development process. Best practices such as maintaining a no-blame culture, encouraging communication among stakeholders, ensuring clear assignment of responsibilities, and using appropriate bug tracking tools are recommended to enhance the bug management process.

The difference between alpha vs beta apps, and nightly vs production builds, lies in their purpose and position in the mobile app development cycle. A build is the compiled source code of an app, while alpha, beta, nightly, and production builds represent different stages of testing and iteration. Alpha builds are initial working versions with missing features, beta builds mark the completion of development and focus on quality and usability, nightly builds reflect daily changes and can be buggy, and production builds are stable and ready for distribution to end-users. The process involves iterative testing and feedback loops, with each build serving a specific purpose in the development cycle.

In the mobile app development cycle, various builds play distinct roles, each characterized by different stability and usability levels. Alpha builds represent the initial phase where core functions are present but may be too buggy for general use, often tested internally or by select external testers. Once feature-complete and stable, apps transition to the beta phase, where beta builds are tested by a broader audience in real-world scenarios to gather feedback and fix remaining issues. Nightly builds, produced automatically each day, incorporate daily changes and are typically unstable, serving as a tool for continuous integration throughout the development process. Finally, production builds are the stable iterations of the app, marked as "release candidates" after rigorous testing, and are distributed to end-users as the finalized product. Various build tools like GNU make, XCodeBuild, Ant, Maven, and Gradle facilitate the creation and management of these builds, with continuous integration practices ensuring that changes are promptly tested to maintain build integrity.

The Instabug team has successfully refactored their iOS SDK by splitting it into smaller, autonomous frameworks that each own a product. This was done to improve modularity, increase productivity, and reduce dependencies between teams. The new setup involves identifying components, deciding what goes where, abstracting business logic, creating dependencies, designing cross-framework communication, managing versioning, and relying on build scripts. The team has also adopted unit testing, UI testing, and manual QA testing to ensure a smooth transition. This refactoring process has improved the company's agility and will positively impact Instabug in the long term.

Life Sum is a Swedish digital health startup that aims to make people healthier and happier by using applied psychology and technology. Founded in 2013, the company offers a mobile app that helps users achieve their health goals through personalized habits and nutrition plans. With over 26 million registered users worldwide, Life Sum has gained popularity for its easy-to-use interface and effective approach to promoting healthy living. The company prioritizes user feedback and releases new builds every other week, often testing internally before distributing them to the wider public. Life Sum's tech stack includes GitHub, Xcode, and Android Studio, with Instabug being a key tool for collecting and managing bug reports and user feedback. According to Sebastian and Tim from the team, the app's success lies in its ability to make healthy living simple and accessible, while also providing a premium version of their nutrition plan for users who want more personalized guidance.

Lifesum, a Swedish digital health startup founded in 2008 and headquartered in Stockholm, aims to improve users' health and happiness through applied psychology and technology. Initially launched as a calorie-counting tracker named Shapers Club, it has evolved into a comprehensive health app offering weight loss and nutrition support, boasting nearly 26.5 million users globally. With over $10 million in Series B funding, Lifesum is transitioning from a startup to a more established organization, supported by a team of 65 employees across various functions. The app is primarily free, but a premium version offers specific nutrition and diet plans. Lifesum's development process includes regular feedback collection through social media, support teams, and focus groups, with GitHub used extensively for product management and issue handling. The company employs a dedicated QA team for testing and utilizes Luciq to streamline bug reporting and feedback processes. Lifesum maintains a bi-weekly release cycle, prioritizing features based on user feedback and company goals, and emphasizes simplicity and efficiency in its operations and development strategies.

Luciq BugSquad experienced a significant 200% growth in team size, prompting a strategic overhaul to enhance productivity and reduce dependencies by restructuring their engineering approach. They reorganized into small, autonomous cross-functional teams called Squads, each owning a specific product, and began refactoring their monolithic iOS codebase into multiple smaller frameworks to address challenges like inefficient feature planning and duplicated efforts. This refactoring involved identifying distinct components such as Bug Reporting, Crash Reporting, Surveys, and Chats, and ensuring the Core component remained lightweight, containing only shared functionalities like networking and logging. The use of CocoaPods facilitated framework separation and dependency management, while cross-framework communication was defined through public APIs. Each framework was versioned separately, allowing Squads to release independently. Despite maintaining local frameworks, Luciq still temporarily distributes them as a single framework due to Xcode limitations, using build scripts to create fat binaries for different architectures. Rigorous testing ensured quality throughout this transformative process, which has positioned Luciq to be more agile and autonomous, with a promising pipeline of developments on the horizon.

O2 Czech Republic, a major integrated operator in the Czech Republic, has successfully launched its Smart Box, a DSL modem, Wi-Fi router, and smart home gateway in one device. The company's Cloud & Mobile Development Lead, Ondrej Sebelik, discussed how they manage feedback and bug tracking using Instabug. The Smart Box was designed to be user-friendly, allowing customers to interact with the company through the app, which has become a natural way for them to ask questions or resolve issues related to their broadband service. Ondrej highlighted the importance of Instabug in providing reliable bug reporting, logs, two-way communication with users, and video capture, among other features. The integration with GitHub has streamlined the process, allowing developers to investigate and fix bugs efficiently. Ondrej shared tips for fellow entrepreneurs, emphasizing the importance of testing, listening to users, embracing mistakes, and using Instabug as a tool for stability and performance monitoring.

O2 Czech Republic, a leading telecommunications provider, has made significant strides in the market by launching the O2 Smart Box, a multifunctional device combining a DSL modem, Wi-Fi router, and smart home gateway, managed through a mobile app that serves as a central hub for user interaction. The company has integrated the Luciq tool for effective bug reporting and user feedback management, allowing seamless communication between users and developers, and enabling efficient issue resolution. The development team, consisting of nine members, utilizes a tech stack that includes GitHub, Jenkins, and Firebase to ensure continuous integration and delivery, while also leveraging Luciq to streamline bug tracking and enhance user experience. The Smart Box is envisioned to become the standard modem for O2’s customer base, with the company aiming for widespread adoption. The integration of Luciq with GitHub has been instrumental in reducing the gap between users and developers, facilitating swift bug resolution, and maintaining a clear connection between customer feedback and developer response.

Instabug has recently introduced several new features and improvements to its in-app surveys, bug reporting, and crash reporting products. The company prioritizes user feedback, aiming to help developers build better apps by understanding their end-users' needs. New survey types include NPS (Net Promoter Score) surveys, which provide a numerical indication of user loyalty, and custom surveys that allow developers to ask multiple questions with various answer types. These updates aim to enhance user engagement, improve data-driven decision-making, and facilitate bug diagnosis and fix. Additionally, Instabug has made improvements to its crash reporting product, including the ability to symbolicate crashes using dSYMs and a new section showing the distribution of crashes across OS versions, app versions, and devices.