4 ms·

Not directly related but another "today" App Store rejection story for rules being incorrectly applied: I had an app get rejected today for referencing MacPaint

Not directly related but another "today" App Store rejection story for rules being incorrectly applied: I had an app get rejected today for referencing MacPaint in the subtitle. It was in the subtitle because one of the major features is that it exports images to MacPaint format. The reviewer cited their rule about not using Apple trademarks in the title or subtitle. Which is fair enough, except that their trademark on MacPaint expired in 2007 (I checked before submitting actually). I ended up changing the subtitle, removing MacPaint, and the app was approved later today. I did call out in the resolution center that the trademark had expired, but of course I got no reply.

threeseed 5y ago
Apple still has an active trademark for MacPaint in UK [1]. If you're app is for sale in the UK, which almost all are, then Apple is obliged to enforce their trademark. [1] https://trademarks.ipo.gov.uk/ipo-tmcase/page/Results/1/UK00001254435 https://trademarks.ipo.gov.uk/ipo-tmcase/page/Results/1/UK00...
- WoodenChair 5y ago
  Fair enough, I didn't think to look abroad. But just for context, suppose my app subtitle were "PDF to Apple Pages." I think if it's in the context of a file format, as mine was, there should be some sort of leeway. "Photo to MacPaint Converter" is basically what my subtitle was.
- kragen 5y ago
  "Enforcing your trademark" does not entail removing claims that a program can export to the trademarked program's file format.
  - threeseed 5y ago
    Rather than turning every app submission into a legal dispute I suspect it's easier for them just to say "don't use our trademarks without permission".
    - WoodenChair 5y ago
      > Rather than turning every app submission into a legal dispute I suspect it's easier for them just to say "don't use our trademarks without permission". Sure, it's definitely "easier." But given all of the bad press they've been getting about how they treat developers on the App Store, maybe it's time for them to stop just doing what's easier for them and start sometimes doing what's better for developers. Now this can't come from individual reviewers, so I don't fault the reviewer for enforcing their policy. I fault their policy for having limited nuance.
    - kragen 5y ago
      Easier for them, intolerable for everyone else.
    - Nevermark 5y ago
      Why not automatically direct developers to an auto-escalation form when something small like this gets violated. The form could first strongly discourage the use of trademarks. But then provide fields for escalating the user of the trademark, based on the developers description of why the trademark is required to describe basic functionality of their app. Auto-escalation options seem like a good thing for an iron gatekeeper to be providing if they want to reduce frustration with the shadow they are casting over techdom.
  - donarb 5y ago
    You're allowed to use their trademark terms in your product description, just not in the title or subtitle of the app.

threeseed 5y ago

Apple still has an active trademark for MacPaint in UK [1]. If you're app is for sale in the UK, which almost all are, then Apple is obliged to enforce their trademark. [1] https://trademarks.ipo.gov.uk/ipo-tmcase/page/Results/1/UK00001254435 https://trademarks.ipo.gov.uk/ipo-tmcase/page/Results/1/UK00...

WoodenChair 5y ago
Fair enough, I didn't think to look abroad. But just for context, suppose my app subtitle were "PDF to Apple Pages." I think if it's in the context of a file format, as mine was, there should be some sort of leeway. "Photo to MacPaint Converter" is basically what my subtitle was.
kragen 5y ago
"Enforcing your trademark" does not entail removing claims that a program can export to the trademarked program's file format.
- threeseed 5y ago
  Rather than turning every app submission into a legal dispute I suspect it's easier for them just to say "don't use our trademarks without permission".
  - WoodenChair 5y ago
    > Rather than turning every app submission into a legal dispute I suspect it's easier for them just to say "don't use our trademarks without permission". Sure, it's definitely "easier." But given all of the bad press they've been getting about how they treat developers on the App Store, maybe it's time for them to stop just doing what's easier for them and start sometimes doing what's better for developers. Now this can't come from individual reviewers, so I don't fault the reviewer for enforcing their policy. I fault their policy for having limited nuance.
  - kragen 5y ago
    Easier for them, intolerable for everyone else.
  - Nevermark 5y ago
    Why not automatically direct developers to an auto-escalation form when something small like this gets violated. The form could first strongly discourage the use of trademarks. But then provide fields for escalating the user of the trademark, based on the developers description of why the trademark is required to describe basic functionality of their app. Auto-escalation options seem like a good thing for an iron gatekeeper to be providing if they want to reduce frustration with the shadow they are casting over techdom.
- donarb 5y ago
  You're allowed to use their trademark terms in your product description, just not in the title or subtitle of the app.