Description
If this library gets popular then it can become a victim of its success.
If both an app and a dependent library use this library then their configurations and state could clash.
The current singleton approach is handy and may cover the vast majority of use cases, but many use cases may need to create dedicated instances that don't share config/state with other instances (ex: configuring GZIP might work against some servers used by the app, but not others used by a dependent library.
It looks like InternalNetworking, ANRequestQueue, and ANImageLoader would need to be refactored.