There are much better choices now, this project is a bit outdated.
I'd base a new app on AFNetworking, not asi.
ImageManager is not needed, as AFNetworking is better suited.
Pull-down-to-refresh is overused already, and most times the wrong context. (Originally, you were loading new tweets ON TOP, not general loading)
The whole tableview examples shouldn't be necessary.
I wouldn't put maps in a example, most apps aren't gonna use it.
JSONKit is great, but also soon iOS4-Legacy.
Adding SVProgressHUD only leads to apps that over-use the modal-loading principle, like the GitHub Issues app. The better way is to make a non-obstrusive, non-modal loading inside the controller, which can be cancelled anytime.
As for the random categories... meh. Get BlocksKit or something actually useful.
"ImageManager is not needed". As a novice to iOS programming, I'm curious to know what is the preferred way to retrieve and cache remote images and display them in an ImageView. Thanks.
I'd base a new app on AFNetworking, not asi. ImageManager is not needed, as AFNetworking is better suited.
Pull-down-to-refresh is overused already, and most times the wrong context. (Originally, you were loading new tweets ON TOP, not general loading)
The whole tableview examples shouldn't be necessary.
I wouldn't put maps in a example, most apps aren't gonna use it.
JSONKit is great, but also soon iOS4-Legacy.
Adding SVProgressHUD only leads to apps that over-use the modal-loading principle, like the GitHub Issues app. The better way is to make a non-obstrusive, non-modal loading inside the controller, which can be cancelled anytime.
As for the random categories... meh. Get BlocksKit or something actually useful.