<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jake MacMullin on Medium]]></title>
        <description><![CDATA[Stories by Jake MacMullin on Medium]]></description>
        <link>https://medium.com/@jmacmullin?source=rss-34ca2ac79601------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*tI_Lr8rKsa9qW-27.jpg</url>
            <title>Stories by Jake MacMullin on Medium</title>
            <link>https://medium.com/@jmacmullin?source=rss-34ca2ac79601------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:29:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jmacmullin/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Tim,]]></title>
            <link>https://medium.com/@jmacmullin/tim-d887a98e4558?source=rss-34ca2ac79601------2</link>
            <guid isPermaLink="false">https://medium.com/p/d887a98e4558</guid>
            <dc:creator><![CDATA[Jake MacMullin]]></dc:creator>
            <pubDate>Tue, 22 Sep 2015 09:23:03 GMT</pubDate>
            <atom:updated>2015-09-22T09:23:03.674Z</atom:updated>
            <content:encoded><![CDATA[<p>Tim,</p><p>I’ve been developing software for Apple platforms since Mac OS X Public Beta (in 2000). I’ve used Radar all that time and whilst in 2000 it seemed to be a much better way of tracking bugs than some of the alternatives (like Bugzilla) it has failed to keep pace with developments in bug reporting elsewhere in the industry.</p><p>If you were to ask people developing software for Apple platforms (both within Apple and beyond) if they’re satisfied with Radar I’m sure you’d hear a resounding ‘No’!</p><p>Some degree of dissatisfaction with tools is to be expected, and some amount of dissatisfaction need not impact on the quality of software being developed. The level of dissatisfaction with Radar is well beyond this though and it is having a material impact on the quality of software being developed for Apple platforms. The shortcomings in Radar are resulting in a poorer experience for your customers. If you improve bug reporting, you’ll reduce bugs and increase the satisfaction of your customers.</p><p>It’s not just external developers who are frustrated with Radar, but Apple engineers too.</p><p>If the people building your software are frustrated but don’t feel empowered to make the changes they’d like to see then that’s a problem.</p><p>In case no one’s told you, here’s some changes I think could improve the bug reporting experience:</p><p>1. Allow developers to indicate that they’re happy to make a report public.</p><p>2. Allow developers to search public bug reports.</p><p>These two alone would make a huge difference. Instead of wasting time wondering if what I’m seeing is a bug or not, I could quickly determine if anyone else has ever encountered the problem and perhaps see how they worked around it.</p><p>3. Provide meaningful feedback to developers about the bugs they’ve reported. Most of the time we report bugs and never hear anything about them again. I understand that internally there might be work happening to fix a bug and there might be comments and discussion happening about the bug within radar but none of this is visible to the reporter.</p><p>4. Allow developers to comment on or vote for other public bugs. Rather than asking people to file multiple duplicate bugs that result in incomplete patchy information you could allow developers to see an existing bug report and to add comments about their experience. This would help create a more complete picture of the issue and would let you see which issues were causing problems for the most people.</p><p>5. Open source more frameworks. Let us help fix the bugs we find. If we had access to source code we could more easily identify bugs and submit proposed fixes along with our bug reports.</p><p>Thanks for your time. I know you and the rest of the team at Apple care about creating great experiences for your customers. Improving bug reporting will help all developers (inside and outside Apple) to create great experiences that our customers love.</p><p>Kind Regards,</p><p>Jake MacMullin</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d887a98e4558" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>