SwiftGen VS KeychainAccess

It is important to say that there is an elegant solution to the resource consistency problem that we haven’t adapted yet. Instead of testing raw values of UIStoryboard.Name cases, we could just generate the UIStoryboard.Name enum. Please refer to SwiftGen for the details.

Your strings should work as-is if you use a tool like SwiftGen (it generates compiler-enforced types for use in your app).

Tools like https://github.com/SwiftGen/SwiftGen can be used to ensure at compile time that all keys used in your app are actually defined. Having keys organized as hierarchical enums, with auto-completion in Xcode is also a nice plus.

Our project includes a Gemfile which we use to specify some external dependencies. I'm trying to add SwiftGen (https://github.com/SwiftGen/SwiftGen) to the project. We want to eventually deprecate Cocoapods so I can't use that installation method.

https://github.com/SwiftGen/SwiftGen/issues/627#issuecomment-715259788

Or you can use something like SwiftGen and have code generation for your localized strings and have it checked at compile time instead of getting those pesky typo errors at runtime that you never check ;)

I normally don‘t use third party libraries if I can avoid it… but using keychain is such a pain that I always use KeychainAccess (https://github.com/kishikawakatsumi/KeychainAccess).

KeychainAccess - Simple Swift wrapper for Keychain. Language: Swift.

I use KeychainAccess. It's pretty simple and straightforward to use. The good thing about using a third-party wrapper is that it'd take care of some edge cases and quirks that I may not have run into yet but someone else might have.

However, if you store secrets on the device, you must use Keychain to securely store them. Do not just store them in a text file or something.