The Apple Store Bundle Identifier uniquely identifies a single app throughout the system. Typically, a reverse-DNS format i sused for bundle ID strings, i.e., MyProduct from example.com results in the reverse-DNS formatted string "com.example.MyProduct".
We currently use com.cozie.ios on the Budslab Apple developer account and com.cozie.Cozie on Federico's Apple developer account.
This is a bit confusing as we don't own https.//cozie.com. Instead we own https://cozie.app. Hence, we should use app.cozie.ios or app.cozie.apple.
As a generic schema I suggest to use [top level domain].[domain name].ios.[experiment name], e.g., app.cozie.ios for the master branch version and app.cozie.ios.orenth for the cozie version used in the orenth experiment.
Also "apple" instead of "ios" would work, .i.e., app.cozie.apple and app.cozie.apple.orenth.
Further, I suggest to only use lower case letters and periods for separation (for the sake of simplicity and clarity)
mariofrei
commented
2 years ago
The Apple Store Bundle Identifier uniquely identifies a single app throughout the system. Typically, a reverse-DNS format i sused for bundle ID strings, i.e., MyProduct from example.com results in the reverse-DNS formatted string "com.example.MyProduct".
We currently use com.cozie.ios on the Budslab Apple developer account and com.cozie.Cozie on Federico's Apple developer account.
This is a bit confusing as we don't own https.//cozie.com. Instead we own https://cozie.app. Hence, we should use app.cozie.ios or app.cozie.apple.
As a generic schema I suggest to use [top level domain].[domain name].ios.[experiment name], e.g., app.cozie.ios for the master branch version and app.cozie.ios.orenth for the cozie version used in the orenth experiment. Also "apple" instead of "ios" would work, .i.e., app.cozie.apple and app.cozie.apple.orenth.
Further, I suggest to only use lower case letters and periods for separation (for the sake of simplicity and clarity)