You're facing conflicting opinions on mobile app bugs. How do you decide on their severity?

Depends on the type of a Bug. Example: If it's a crash with a huge impact, it should be severe. If the count is less, it should have less priority. If it's a business logic bug having an impact on UX then it can be treated as severe as well. If there's a bug in some cases which is random, such bugs can be fixed on lower priority. High priority should be given to the UX bugs, business logic bugs and crashes.

Main point here is how many users are affected by the bug and is it affecting the main impactful features of the app and causing crashes? So if answer is yes, it should be severe. But if lets say bug is happening in some feature that is not used that much by users and used randomly and also not crashing, we can make it less severe. Simple. And related to business logic bugs, if they are affecting the users on large scale, then make it severe and if its impact is small, we can make it less severe and focus on crashes and most impactful feature bugs. User Experience is all that matters.

When facing conflicting opinions on mobile app bugs, use bug triage to decide their severity. Start by gathering detailed information about each bug, including steps to reproduce and user impact. Categorize bugs by type, such as functional, performance, or UI/UX issues. Assess the impact on users and the app, considering factors like the number of users affected and the frequency of the issue. Prioritize bugs by severity: high-severity bugs cause crashes or data loss, while low-severity bugs affect minor features. Discuss and document severity decisions with your team, and incorporate user feedback to understand real-world implications. This structured approach ensures critical issues are addressed promptly.

From my experience, the bug which is creating a bigger negative impact on users needs to be prioritised first. And functional bugs always take priority over UI bugs as it can heavily affect user satisfaction. And if a bug is in the homepage or dashboard or any other page of the mobile app where user traffic is more, that part of the app should be taken utmost care without any bugs.

When facing conflicting opinions on mobile app bugs, consider user impact to decide their severity. Start by identifying the number of users affected by the bug. Assess how the bug disrupts app functionality, prioritizing bugs that cause crashes or prevent key features from working. Measure the level of frustration or inconvenience the bug causes for users. Analyze user feedback from reviews and support tickets to gauge user perception of the bug's impact. Finally, evaluate the bug's effect on your business goals, such as revenue and user retention. This approach ensures that the most disruptive issues are prioritized and addressed first, maintaining a positive user experience.

When facing conflicting opinions on mobile app bugs, consider their impact on business goals to decide their severity. First, determine if the bug affects revenue-generating features, such as payment processing. Bugs hindering transactions are high priority. Next, assess if the bug impacts user retention or satisfaction, as frequent crashes can lead to user churn. Consider the bug's effect on your brand's reputation; negative reviews can harm your brand. Evaluate whether the bug increases support requests, affecting operational efficiency. Align bug prioritization with your strategic goals to ensure critical issues are addressed promptly.

Data-Driven Decisions: Use analytics to understand how frequently the bug occurs and its impact on user behavior, providing objective insights to prioritize effectively.