Oh shit , I thought I was in rcosplaygirls , rcosplay or rComicBookHotties . Go OP , go reap your karma ! <| sep |> Somebody please find me a video of the camera slowly zooming in on the reporter at the top of Kyle Field . <| sep |> Tenants are the people who live in your building . Tenets are conceptual principles . <| sep |> That is a fine approach . Singletons can be dangerous but assuming you will continue to use your API throughout the lifecycle of your app , a singleton is definitely appropriate here . That is also fine , but I also don ' t see any issue with keeping the token in memory while your app is active to limit keychain access overhead . Yes . Though depending on needs , I would consider an auth system that allows token refreshing , if that isn ' t a part of your validateToken method already . Signing in on mobile apps is annoying . I would also be sure to validate when your app becomes active as well , since there is no guarantee a token will expire while the app is completely suspended and not just in the background . Instead of storing Json directly , you might consider unpacking your user Json as an actual object model . If you used a persistence API like Core Data you could fetch from there . Or use a singleton like you did for your API . Nope , seems about right