Craig Hockenberry“We treat all developers the same.”
I'm fine with that not being true, and there are good reasons for it not being true, but I wish Apple would stop saying it.
Falls into the Google-not-being-evil category.
Michael Thole
- 3 Followers
- 172 Following
- 71 Posts
Taking a professional break. I've built stuff that you've hopefully used from Apple, Square, and DoorDash.
@manolo Perfect! I like it.
@manolo Inappropriate/illegal parking in a residential area could also result in this prize 💩
@kyleve Which color are you getting and how does it look IRL?
@chrisvasselli I’ve made a few of these graphs myself over the last few years. I always wish the ObjC chunk would go down faster, haha.
@kyleve So happy to see you thriving!
@batson Dynamically loading from a configuration file that you ship with the app would be even more accessible... so that's a lose-lose.
You could dynamically load the configuration over HTTPS, removing the secret from your .ipa bundle. Better! But "bad guys" could still run your app with an HTTPS proxy and gain access to your secrets that way. Then you get into certificate pinning and other arms-race stuff that usually isn't a good use of your time.
@batson I wouldn't use a .plist file that gets embedded into the app and dynamically read from or anything like that-- that just adds complexity for no benefit IMO.
I would try to structure the code for my app such that all this type of stuff is available in one place (i.e. Config.swift that vends a struct with some `let` properties) and then injected into actual usage.
@batson IME, it’s generally just fine to hardcode the client ids in your Swift code. You will need to treat the id as not secret, though— it’s only mildly obfuscated.
Is there a way to tell Apple TV that I never ever want to see any sports stuff? Half the main screen is full of this now. 😢