+1 I am a small developer with a niche audience (firefighter training, simsushare.com) that has a cross-platform app. Most of my audience is Windows and iOS, but I do need Mac as well.
I don't really need Apple to help with marketing the app, so paying 30% on the Mac App store is way too much for me. On iOS, it is necessary because there is no alternative. Also, my simulation tool has an enterprise subscription, which means Apple can say yes or no and meddle with my business model. Too many restrictions!
Now Apple is saying I have to get my app notarized for Mojave. I don't quite understand why I have to do that in addition to the $99/year I pay for the Mac code sign. Bottom line is that I'm not making a killing by any means and Apple is hurting me by adding all the technical restrictions and financial constraints.
My advice is that before you propose solutions, you ought to really figure out what the problem is. Is it ignorance, laziness, or something else?
I've looked over the various responses and haven't seen one angle -- have you asked your team about why they are not doing what you'd like? There's a lot of advice about read this, do that, etc. but you don't yet know why they are not following what you think is common sense. You might find something surprising by putting it on the table, or at least you'll find the reasons they give. Then you can address those.
My advice is to put this out as a question to your team and see how they react. You might even find out that some of the patterns you think are best are not, i.e., your team has a reason you didn't think of.
For example, I created a 10-element array to speed the search of a big table in which all keys began with a digit from 0-9. The more experienced guy told me that in the .NET world, the convention was to use key-value pairs instead of an array. To satisfy him, I changed it to a hash table, where I hashed the first digit. It seemed pretty silly to me, making a hash table for what to me was clearly a better approach using a simple indexed array. He had in his mind the "right" way to do it, eventhough I still think the hashtable in this case was silly.
I don't really need Apple to help with marketing the app, so paying 30% on the Mac App store is way too much for me. On iOS, it is necessary because there is no alternative. Also, my simulation tool has an enterprise subscription, which means Apple can say yes or no and meddle with my business model. Too many restrictions!
Now Apple is saying I have to get my app notarized for Mojave. I don't quite understand why I have to do that in addition to the $99/year I pay for the Mac code sign. Bottom line is that I'm not making a killing by any means and Apple is hurting me by adding all the technical restrictions and financial constraints.