What is best practice for Nortarization's management?

Hi.I'm Educational App Developer in Japan.

I have two questions so please tell me.


1.Best practice when there are more than 25 apps.

Nortarization required app-specific passwords.

But I can only have 25 passwords per ID.

We have over 70 apps.Do we have to have 3 IDs?😕


2.Best practice about the application updated every year.

Some of our applications are updated every year. we sell as another title.

Example:"Math 2017","Math 2018","Math 2019"...

We probably need to get a notarized certificate every year, right?

It will exceed 100 apps when it becomes so.😮

it's difficult to manage. Is there any good way?


Thank you for reading poor English.🙂

Replies

1. Best practice when there are more than 25 apps.

The app in app-specific password refers to the notarisation tool (

altool
), not to the app you’re actually notarising. It’s fine to use the same app-specific password for all your notarisation work, no many how many apps you’re distributing.

2. Best practice about the application updated every year.

When you update an app (say Math 2017 to Math 2018), do you change the bundle ID?

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Hi, eskimo.

OMG.I was misunderstood about app-specific password. 😮 Thank you for teaching me.

"For now", our app doesn't have a bundle ID because we don't sell at the mac app store.

I’m glad to hear that you got the app-specific password sorted out (-:

"For now", our app doesn't have a bundle ID because we don't sell at the mac app store.

Ah, um, all Mac apps should have a bundle ID, even if they’re not distributed via the Mac App Store. Bundle IDs are the primary way that macOS identifies apps, and have been required since the first release of macOS, long before the Mac App Store was dreamt up.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

What you say is correct.

However, Until a few years ago, we were supplying .app files directly without being conscious of ID.

(We have been in business since the 90's.

There are still many apps using Flash Projector(stand-alone Flash player / ActionScript2).😮😮😮

We can make app file without being conscious of ID by Adobe Flash/Animate.)


Currently, We manage to e-signing apps and create an installer using the pkgbuild command.

Therefore, Although there is IDs(It's set in the PKG file), We don't know how to handle well.

(On the one hand We have many iOS apps but Know-how is useless because the way is different.)


[Features about some of our apps]

1.There is an application that is put out as another title every year.

2.We can't "update" unless there is a fatal problem.(Insincere but real)😢

3.It isn't necessary to coexist different versions on one PC.

4.Although older versions must also be able to through the Gatekeeper.

(Example)

case 1: You bought my apps for your son. A few years later, your son's brother can use it.

case 2: A school buy my apps and can install for several years.


Could you tell me a good practice?