Thanks for any thoughts on this!
AlwaysAre there any "gotchas" if you set up a second Apple ID just for your paid developer account?
No. Never do that. App Store Connect has the ability to create kinda-fake Apple IDs just for testing. They use special Apple developer services designed just for testing.I assume you can set up your personal ID as a "developer" in App Store Connect for testing.
This Apple web page has instructions on how to configure your phone for two-factor authentication with multiple accounts. It is very easy. You can do it on your Mac with a separate account but using your phone is so much easier.How do you do two-factor for the "business" ID? (Do you need a separate device for that?) Do you use the same phone number for both accounts (I'm only planning on having one phone, haha)?
PS: Those testing Apple IDs also support two-factor authentication. But for those, I just use SMS. I wouldn't recommend trying to integrate them with real two-factor authentication, or even if that is possible.
I don't know if I could conceive of any "meaningful advantages". There are a number of gotchas and hassles associated with having a separate developer Apple ID. It is just that I can't even imaging trying to use the same Apple ID. Maybe if you are just doing it as a hobby and always plan to do that forever then a single Apple ID might be acceptable.Are there actually any meaningful advantages to having a separate Apple ID for this purpose?
If you have any apps in the App Store, they will be associated with your real name. That can be a bit suspicious. I have an app that has some security features and I've been seriously contemplating considering any Mac app signed by a personal Apple ID to automatically be potential malware. I have a lot of data from the other side of things so I know that signed, malicious Mac apps are always signed with personal (but probably fake) Apple IDs. I consider such accounts practically worthless from a security perspective. This does NOT apply to App Store apps, however. There are more hoops to jump through over there.
One of the biggest hassles is just dealing with multiple Apple IDs. One trick I use is keeping Safari Technology Preview handy and using that exclusively for my business activities. This way, I can login to the forums (and App Store Connect) with my business Apple ID. All of my other Apple interactions (iCloud, etc.) use my personal Apple ID in the normal Safari version. I even use a really old Apple ID for Apple Support Communities (long story). Apple's corporate login procedures are not designed for multiple Apple IDs. But ironically, Apple has made if more difficult to sign in at all recently and now it is a little bit easier to just click on the "Use other Apple ID" button and then I can just pick the appropriate Apple ID and let it autofill the password.
Officially, I am in complete agreement with Eskimo's suggestion to create a corporate entity, especially if you ever intend to charge money or do more than hobby coding. Just don't that that step lightly. It isn't as expensive as you might think, but ideally, put a couple thousand dollars into it to do it right. You will need to pick a business name and make sure it isn't one that someone else has ever used. You WILL get sued if you don't do your legwork and preparation. At a minimum, check domain names and do trademark searches. I strongly recommend consulting with a lawyer. Your corporation would be a global corporation and subject to laws throughout the world. Apple makes compliance with global laws very easy. Apple handles 90% of the details for you. (But not 100%). Read that developer agreement very carefully and have your lawyer do likewise.