If you use the wrong icons for certain functionality. They will reject it. If it is confusing to the user. They will reject it. If the standard UI components do not work as expected. They will reject it. If an operations fails without appropriate feedback. They will reject it
But they will usually tell you one item in the GUI that they rejected it for. Thus when you fix it and send it back they can tell you about the next one.
They are definitely guidelines, but if you don't have confidence or a good amount of experience with UX, you should treat them as gospel. When developing mobile apps, I kind of feel that providing a good UX should be the highest priority. A lot of developers are pretty bad at UIs, and the HIG provides a very good set of guidelines to follow, at least at the start. You should owe it to yourself to give a HIG a thorough read.
It really depends on how much your devition results in a better user experience.
The HIG is there to help you build an application that users will understand how to use more or less from the start, and make the application easy to use.
If you do some custom things that improve life for the user, Apple will probably let it go. But if you are deviating in ways that make the application harder to use, they will tend to come down on you.
A lot of the possible rejections are pretty reasonably things - for example I was rejected once for a rotated view where the UI elements didn't quite all replace correctly. Once fixed (and it really was a bug on my part) the app was accepted.
指导方针。底线是它必须能够工作，不能使用任何私有 API 或违反协议条款。如果它按照它所说的那样做并且不会立即崩溃，那么您可能会没事。
Guidelines. The bottom line is that it has to work, not use any private API or violate the terms of the agreement. If it does what it says it's going to do and doesn't crash right away, you'll probably be fine.
但有许多应用程序的 UI 相当粗糙（对于其他开发者来说看起来不符合 HIG），但不知何故被应用商店接受。另一方面，人们听说其他应用程序被拒绝，因为审阅者看起来与您看起来非常不同（您会将图标 X 与完全不同的图标 Y 混淆吗？等等）或者错误地使用“”这个词或者” 代替 SDK 协议规则之一中的“和”？
The HIG is more a way to change your odds in a lottery. You greatly improve your odds by not doing anything that clearly looks like a violation of the HIG. There are web sites that list things that appear to at least one reviewer to be violations.
But there are many apps with fairly crufty UIs (that don't look HIG compliant to other devs) but somehow got accepted into the App store. On the other hand, one hears about other apps that are rejected for something that looked to the reviewer very different than it looked to you (would you confuse icon X for the completely different icon Y? & etc.) Or mistake the word "or" for "and" in one of the SDK Agreement rules?
发布评论
评论（5）
这一切都取决于。
如果您对某些功能使用了错误的图标。 他们会拒绝。
如果它让用户感到困惑。 他们会拒绝。
如果标准 UI 组件未按预期工作。 他们会拒绝。
如果操作失败而没有适当的反馈。 他们会拒绝它
但他们通常会告诉您 GUI 中的一项他们拒绝了它。
因此，当您修复它并将其发回时，他们可以告诉您下一个。
It all depends.
If you use the wrong icons for certain functionality. They will reject it.
If it is confusing to the user. They will reject it.
If the standard UI components do not work as expected. They will reject it.
If an operations fails without appropriate feedback. They will reject it
But they will usually tell you one item in the GUI that they rejected it for.
Thus when you fix it and send it back they can tell you about the next one.
它们绝对是指南，但如果您没有信心或没有丰富的用户体验经验，您应该将它们视为福音。在开发移动应用程序时，我觉得提供良好的用户体验应该是重中之重。许多开发人员不擅长 UI，而 HIG 提供了一套非常好的指导方针可供遵循，至少在开始时是这样。您应该彻底阅读 HIG。
They are definitely guidelines, but if you don't have confidence or a good amount of experience with UX, you should treat them as gospel. When developing mobile apps, I kind of feel that providing a good UX should be the highest priority. A lot of developers are pretty bad at UIs, and the HIG provides a very good set of guidelines to follow, at least at the start. You should owe it to yourself to give a HIG a thorough read.
这实际上取决于您的偏差在多大程度上会带来更好的用户体验。
HIG 可帮助您构建用户从一开始就或多或少了解如何使用的应用程序，并使应用程序易于使用。
如果你做了一些定制的事情来改善用户的生活，苹果可能会放弃它。但如果你的做法有所偏差，导致应用程序更难使用，他们往往会责怪你。
许多可能的拒绝都是相当合理的事情 - 例如，我因旋转视图而被拒绝一次，其中 UI 元素没有完全正确替换。一旦修复（这确实是我的一个错误），该应用程序就被接受了。
It really depends on how much your devition results in a better user experience.
The HIG is there to help you build an application that users will understand how to use more or less from the start, and make the application easy to use.
If you do some custom things that improve life for the user, Apple will probably let it go. But if you are deviating in ways that make the application harder to use, they will tend to come down on you.
A lot of the possible rejections are pretty reasonably things - for example I was rejected once for a rotated view where the UI elements didn't quite all replace correctly. Once fixed (and it really was a bug on my part) the app was accepted.
指导方针。底线是它必须能够工作，不能使用任何私有 API 或违反协议条款。如果它按照它所说的那样做并且不会立即崩溃，那么您可能会没事。
Guidelines. The bottom line is that it has to work, not use any private API or violate the terms of the agreement. If it does what it says it's going to do and doesn't crash right away, you'll probably be fine.
HIG 更多的是一种改变彩票赔率的方式。如果你不做任何明显违反 HIG 的事情，你的胜算就会大大提高。有些网站列出了至少一位审阅者认为违规的内容。
但有许多应用程序的 UI 相当粗糙（对于其他开发者来说看起来不符合 HIG），但不知何故被应用商店接受。另一方面，人们听说其他应用程序被拒绝，因为审阅者看起来与您看起来非常不同（您会将图标 X 与完全不同的图标 Y 混淆吗？等等）或者错误地使用“”这个词或者” 代替 SDK 协议规则之一中的“和”？
The HIG is more a way to change your odds in a lottery. You greatly improve your odds by not doing anything that clearly looks like a violation of the HIG. There are web sites that list things that appear to at least one reviewer to be violations.
But there are many apps with fairly crufty UIs (that don't look HIG compliant to other devs) but somehow got accepted into the App store. On the other hand, one hears about other apps that are rejected for something that looked to the reviewer very different than it looked to you (would you confuse icon X for the completely different icon Y? & etc.) Or mistake the word "or" for "and" in one of the SDK Agreement rules?