5 ms·

Why is this arrogant? If they are asking about the Touch Bar, it's most likely because the developer mentioned adding some feature to the Touch Bar in the relea

by donarb 6y ago

Why is this arrogant? If they are asking about the Touch Bar, it's most likely because the developer mentioned adding some feature to the Touch Bar in the release notes and it is not apparent what that feature is. You can't advertise something that doesn't exist.

_qulr 6y ago
No, the developer did not mention Touch Bar in the release notes, and the app has no specific Touch Bar features. Nothing about Touch Bar is required in the App Store guidelines.
- dsl 6y ago
  You either referenced NSTouchBar or included a library that did so. Sometimes it is as simple as a error reporting library or ad network client trying to enumerate the device hardware. The Human Interface Guidelines explicitly lay out what is allowed and not allowed with the Touch Bar. For example, you can't turn it in to an extended display. https://developer.apple.com/design/human-interface-guidelines/macos/touch-bar/touch-bar-overview/ https://developer.apple.com/design/human-interface-guideline...
  - _qulr 6y ago
    > You either referenced NSTouchBar or included a library that did so. Who are you talking to?
    - dsl 6y ago
      You were speaking authoritatively about the underlying code of an app that had a review issue related to Touch Bar, and made an incorrect statement that there are no design requirements for that feature. I was giving you guidance on why that item gets flagged for review.
      - _qulr 6y ago
        > You were speaking authoritatively about the underlying code of an app I know the developer, who was talking about the rejection. > that had a review issue related to Touch Bar, Several other developers chimed in and said they randomly got the same exact question. It's not a "review issue" per se, although it does prevent the app from getting approved. It may be some weird kind of obnoxious poll Apple is running. (Apple really wants devs to support Touch Bar.) > and made an incorrect statement that there are no design requirements for that feature. I was giving you guidance on why that item gets flagged for review. No, this is an incorrect interpretation of what I said. What I meant was that the App Store Review Guidelines don't require you to support the Touch Bar. You can have a Mac App Store app with no Touch Bar customization. None of my apps have any.
        hobofan 6y ago
        Yup, sounds very much on par with our experience. On the first version of our app, we especially mentioned in the review comments (and configured in the release build) that we do not support iPads, as that wasn't a priority for our initial release and would have required additional testing work. Review came back as rejected with a comment along the lines of "Hey, why don't you support iPads?".
- donor20 6y ago
  False. If you are using touch bar libraries you MUST have touch bar features and the reviewer can ask you where they are. This really shows why apple needs to be strict with devs. They will include third party code (ad networks etc) without enough care - the networks then try to device fingerprint etc. And 98% of the touch bar library use with no touch bar feature is abusive. They should let devs appeal, but if a dev lies and claims no touchbar library use when there is some, ban their account permanently. The reviewer in these cases may want to see the touchbar feature that justifies library use, the app author saying they don't have any touchbar feature means use of library is improper. So many devs do NO due diligence on the third party libraries they import.
  - _qulr 6y ago
    > If you are using touch bar libraries you MUST have touch bar features and the reviewer can ask you where they are. Ok but there are no touch bar libraries in this case. > They will include third party code (ad networks etc) without enough care - the networks then try to device fingerprint etc. Not the case here. Also, if this issue was triggered by code, then it would come up in every update, instead of just occasionally at random.
    - donor20 6y ago
      My point is simply there are guidelines around touchbar - despite your claims. Stop trying to claim that there is no guideline - as I have repeatedly pointed out - if you are using touchbar libs to fingerprint devices for ad networks - that is not allowed as one example. If this app wasn't doing any of that, then great! The reviewer was wrong. But to claim no rules around touchbar usage and calls is entirely false.
      - _qulr 6y ago
        > Stop trying to claim that there is no guideline - as I have repeatedly pointed out As I have repeatedly pointed out, I was never trying to claim that. You are arguing against a straw man. You're right. You win. The straw man is defeated.
      - 6y ago

by donarb 6y ago

_qulr 6y ago

No, the developer did not mention Touch Bar in the release notes, and the app has no specific Touch Bar features. Nothing about Touch Bar is required in the App Store guidelines.

dsl 6y ago
You either referenced NSTouchBar or included a library that did so. Sometimes it is as simple as a error reporting library or ad network client trying to enumerate the device hardware. The Human Interface Guidelines explicitly lay out what is allowed and not allowed with the Touch Bar. For example, you can't turn it in to an extended display. https://developer.apple.com/design/human-interface-guidelines/macos/touch-bar/touch-bar-overview/ https://developer.apple.com/design/human-interface-guideline...
- _qulr 6y ago
  > You either referenced NSTouchBar or included a library that did so. Who are you talking to?
  - dsl 6y ago
    You were speaking authoritatively about the underlying code of an app that had a review issue related to Touch Bar, and made an incorrect statement that there are no design requirements for that feature. I was giving you guidance on why that item gets flagged for review.
    - _qulr 6y ago
      > You were speaking authoritatively about the underlying code of an app I know the developer, who was talking about the rejection. > that had a review issue related to Touch Bar, Several other developers chimed in and said they randomly got the same exact question. It's not a "review issue" per se, although it does prevent the app from getting approved. It may be some weird kind of obnoxious poll Apple is running. (Apple really wants devs to support Touch Bar.) > and made an incorrect statement that there are no design requirements for that feature. I was giving you guidance on why that item gets flagged for review. No, this is an incorrect interpretation of what I said. What I meant was that the App Store Review Guidelines don't require you to support the Touch Bar. You can have a Mac App Store app with no Touch Bar customization. None of my apps have any.
      - hobofan 6y ago
        Yup, sounds very much on par with our experience. On the first version of our app, we especially mentioned in the review comments (and configured in the release build) that we do not support iPads, as that wasn't a priority for our initial release and would have required additional testing work. Review came back as rejected with a comment along the lines of "Hey, why don't you support iPads?".
donor20 6y ago
False. If you are using touch bar libraries you MUST have touch bar features and the reviewer can ask you where they are. This really shows why apple needs to be strict with devs. They will include third party code (ad networks etc) without enough care - the networks then try to device fingerprint etc. And 98% of the touch bar library use with no touch bar feature is abusive. They should let devs appeal, but if a dev lies and claims no touchbar library use when there is some, ban their account permanently. The reviewer in these cases may want to see the touchbar feature that justifies library use, the app author saying they don't have any touchbar feature means use of library is improper. So many devs do NO due diligence on the third party libraries they import.
- _qulr 6y ago
  > If you are using touch bar libraries you MUST have touch bar features and the reviewer can ask you where they are. Ok but there are no touch bar libraries in this case. > They will include third party code (ad networks etc) without enough care - the networks then try to device fingerprint etc. Not the case here. Also, if this issue was triggered by code, then it would come up in every update, instead of just occasionally at random.
  - donor20 6y ago
    My point is simply there are guidelines around touchbar - despite your claims. Stop trying to claim that there is no guideline - as I have repeatedly pointed out - if you are using touchbar libs to fingerprint devices for ad networks - that is not allowed as one example. If this app wasn't doing any of that, then great! The reviewer was wrong. But to claim no rules around touchbar usage and calls is entirely false.
    - _qulr 6y ago
      > Stop trying to claim that there is no guideline - as I have repeatedly pointed out As I have repeatedly pointed out, I was never trying to claim that. You are arguing against a straw man. You're right. You win. The straw man is defeated.
    - 6y ago