How I Found a Front-End Bug on Spotify's Mobile App: Bug Bounty and Beyond
Tags: webdev, javascript, bug, programming
Published: 2023-11-07 19:52:40

**Introduction:**
Have you ever come across a minor issue in an app or a website and thought, "I should report this"? That's exactly what happened to me when I stumbled upon a front-end bug in Spotify's mobile app. This blog will take you through my bug-hunting journey, the bug itself, my motivations, and the opportunities it uncovered.

**Section 1: The Bug Discovery**
It all began when I noticed something amiss in Spotify's Premium user interface. A tiny glitch that might escape the eye of many but can have a significant impact on user experience. Let's take a closer look:

Bug Screenshot:

![Bug Screenshot](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2qe26s9nii1c1jqrabis.png)

This visual anomaly was a misplaced `<br>/` instead of `<br/>` in the code. To the untrained eye, this might seem trivial, but as a front-end engineer, I couldn't let it go unnoticed. Small details matter in design, and this bug was a testament to that fact.

**Section 2: Reporting to Customer Support**
I decided to report this bug directly to Spotify's customer support, thinking they might appreciate the attention to detail. Here's how the conversation went:

https://x.com/AswinBarath2/status/1721972258791432435?s=20

Engaging with customer support was an important step. It highlighted the role of user feedback in software development. Our conversation demonstrated Spotify's dedication to listening to its users' concerns.

**Section 3: The Bug Details**
Now, let's delve deeper into the bug itself, as explained in my tweet:

The bug involved a `<br>` tag, a line break in HTML, that was supposed to be invisible to users but was erroneously visible as `<br>/`. Moreover, the word "for" was missing in the context of the Premium Individual plan.

Such small discrepancies can be confusing for users, particularly those who aren't tech-savvy. This highlights the importance of meticulous coding and design in software.

**Section 4: Why I Reported It**
As a front-end engineer, I understand the significance of an optimal user experience. Even minor issues can affect how users perceive a service. That's why I promptly reported the bug. I believe in crafting seamless experiences, and this bug needed fixing.

**Section 5: The Opportunity**
Reporting the bug wasn't just about spotting an issue; it was also about seizing an opportunity. Here's how I expressed my intentions in a tweet:

I'd be thrilled to contribute further to Spotify and potentially join their team. If the opportunity arises, my email address is aswin2001barath@gmail.com. Exploring such opportunities is an exciting prospect for any developer.

**Section 6: Creating Social Proof**
Beyond the bug report, I aimed to create a social proof of my bug-reporting skills by sharing this journey on Twitter. It's not just about Spotify; it's about inspiring fellow developers to be vigilant and proactive when they encounter issues in the software they use.

**Section 7: The Benefits of Fixing the Bug**
Resolving this bug isn't just about cosmetics. It's about improving user experience, reducing confusion, and delivering a higher quality service. Even the tiniest bug fixes can have a profound impact on a product.

**Section 8: Addressing Security Vulnerabilities**
Moreover, bug reporting isn't limited to user experience; it can also contribute to enhanced security. Bugs are sometimes a window for vulnerabilities. By identifying and reporting them, we help create a safer online environment for everyone.

**Section 9: Showcasing Your Resume**
If you'd like to explore my qualifications and experience, you can find my developer profiles over here: https://linktr.ee/AswinBarath
I'm ready and eager to embrace new career opportunities.

**Section 10: Conclusion**
In conclusion, this journey is not just about a bug report but about the broader impact of vigilant users who take the time to provide feedback. I appreciate Spotify's quick response and hope this bug will be addressed soon.

I invite you to engage with my Twitter thread for a concise overview. Thank you for joining me on this bug-hunting adventure, and let's make the web a better place together!

**Closing Thoughts:**
If you've ever spotted a bug in an app or website, consider reporting it. Your keen eye and attention to detail can make a difference. Keep an eye on your surroundings, for you never know where opportunities may arise.

**References:**
- Twitter Thread: https://x.com/AswinBarath2/status/1721972731032285530?s=20