The podcast discusses challenges faced during summer, troubleshooting a photo widget bug, testing and releasing an app update, operating WidgetSmith, and the forgiving nature of users.
Software development is constantly changing and unforeseen issues can arise, emphasizing the importance of making reasonable efforts to fix problems and being proactive in addressing user reports.
Neglecting customer support can lead to unresolved issues, highlighting the significance of promptly addressing user concerns and implementing better testing strategies.
Deep dives
Dealing with Unexpected Challenges and Bugs
The episode begins with a story of how the host encountered a bug in his app Widgetsmith after a user reported a problem. He explains the pressure and stress he felt due to the scale of his app and the potential impact on users. The host emphasizes that software development is constantly changing and that unforeseen issues can arise. He highlights the importance of making reasonable efforts to fix problems and being proactive in addressing user reports.
Navigating a Large-Scale Bug Fix
The host discusses the steps he took to address the bug in Widgetsmith. He shares how he isolated the issue, identified the cause, and developed a solution. He explains the challenges of resizing images within the memory limits of the widget extension. The host reflects on the pressure of fixing the bug before it impacted a significant number of users. He describes testing the fix with his family and through beta testers before submitting the updated version for app review.
The Importance of Customer Support
The host admits to neglecting customer support during the period of focusing on coding. He acknowledges that many users had reported the same issue, and he takes responsibility for not being more attentive. He discusses how he responded to support inquiries and app store reviews, emphasizing the significance of addressing user concerns promptly and with care. The host realizes the need to implement in-app messaging and better testing strategies to avoid similar issues in the future.
Lessons Learned and Feedback for Apple
The host reflects on the lessons learned from the bug fix experience and suggests that Apple should document the limits in WidgetKit to help developers navigate potential issues. He conveys a sense of relief and satisfaction in resolving the problem and winning the race against iOS 17.1's rollout. The host concludes by expressing gratitude for the support and understanding of Widgetsmith users throughout the process.
What happens when you break 50 million home screens?
This episode of Under the Radar is sponsored by:
Indeed: Join more than three million businesses worldwide using Indeed to hire great talent fast.
Links and Show Notes:
Correction: Since recording this episode I've discovered that the bug actually only occurred on the iOS 17.2 Beta and not the 17.1 GM build as I had originally thought. A testing device I was using was actually on the Public Beta program when I thought it was only running the GM builds. Either way the panic was real and the urgency was still just as palpable. The bug was affecting every user on the Beta Program which isn't insignificant. That makes me feel a bit better about my process for catching bugs like this, since I didn't miss it in an entire beta cycle, just a few days since the beta 1 was released.
