| How to submit apple Bug or functional requirements? |
| Submitted to the Radar may encounter a situation, that is, before the issue has been submitted, it will be marked as "duplicate", do not panic, in fact, here contains a Radar submission skills. As mentioned above, the only way to the apple bug Bug Reporter feedback is, in other places had been no use, apple is not recommended, if you go too far, Apple may also be subject to punishment. So, how to make apple pay attention to your question? Daniel Pasco, an experienced Apple Developer, teaches us the experience in his article: The team of engineers is always faced with too many problems to be solved, and the engineers regularly meet with their supervisors to sort out the problem and decide which problem to solve. The more a problem is reported, the more it needs attention, and it will be easier for engineers to make judgments. For all software companies are like this, when you release a product, people are likely to report one or two cases of edge (edge case) of the problem, you will certainly want to fix it in the time allowed, but if there are hundreds of people reporting the same problem, the problem is very serious. And to be solved. Apple is no different from other companies in this regard. In a sense, the question of repetition is a vote, or a support for an existing problem. The more times a question is obtained, the higher it will be. Therefore, if you find a problem, put forward in the Radar, can be Radar to publish the original blog or forum, called for other developers to ask the same Radar, prompting Apple engineers pay more attention to this problem. However, we must exercise restraint, pay attention not to abuse. In addition to submit a repeat problem, and may not be commonly used techniques, you can go with the apple engineer, if you submit the Radar for several days no movement, you can contact Apple engineers, in order to obtain a feedback. Of course, here is how to pick up and up the skills we need to work on his own. Are you ready to see here, want to go to a few bug submitted to Bug Reporter? But foreign Apple developers of this Radar system is not how to buy it, why? Fix Radar or GTFO Apple's Bug Reporter system, the biggest problem is that the developer submitted questions, can not quickly receive effective feedback. The general scenario is that you submit a question, and then it is marked as duplicate and close, then there is no then. Other developers can not see your submission to the Radar, you can not see Apple's engineers for this problem, you can not know when you submit the question can be repaired. If your Bug is very urgent or has some other problems, Apple may contact you directly, but this is rare Mattt God once mentioned, a Radar in the proposed for 7 years before being repaired, in addition to submit Radar skills, lack of effective means of communication is the cause of this result. In addition, the Bug Reporter system as well as UI is not pretty, completely unlike Apple products, the developer is not friendly enough defects. In 2012, some apple developers can not stand Bug Reporter system as a black hole, launched the "Fix Radar or GTFO", calls for developers to submit repetitive Radar, want to improve the apple Bug collection system, make it more open. Others have done a openradar, the developer submitted to the official Bug Reporter, you can also submit their Radar here, developers can see other people's Radar and discuss. The developers of these efforts received a certain effect, in September 2013, apple redesigned the Bug Reporter system, improved its UI and experience, but for developers open Radar requirements is not satisfied, you still do not know after you submit a question actually what happened. However, there are developers on the "Fix Radar GTFO" campaign and disagree, as the article said, "or": In fact, developers do not need a Radar, the need for Radar is apple, if Radar for apple to work very well, then there is no problem. For example, whether or not to open the Radar above, if the open Radar will cause some bad consequences, such as Bug malicious use, Radar priority is active user interference and so on, so it is not open. Developers need to do is file and forget (submit and forget), submitted to the Bug has done the developer's responsibility, then leave it to apple. Yes, maybe we missed it, if we know that the Radar submission will be taken seriously, so there is no need to ask for more, after all, for the improvement of products is the most urgent apple, rather than developers. So, the information asymmetry is the root of all evil, so let's see, an Radar is submitted, apple is how to deal with it. Apple's internal is how to deal with Radar? One who visited Apple's internal developers said, Apple has a special Mac app for submission of Bug, in this app, Apple engineers to the labeling and classification of problems, different engineers on the same issues were discussed, the final priority evaluation, such as evaluation "Show-Stopper" problem is the first time to solve, otherwise it will not release |
