timothy1ee
commented
10 years ago Good job! Glad things went better this time around. The point of this homework was to explore some challenges involved in developing a richer MVC client.
- For this particular animation, you're right that if you just had a larger image that you move left and right, that would be a better way to do it. We're going to cover view animation in class today.
- If you get a chance, you should attempt more of the optional features. They are trickier than they appear and will help prepare you to build richer apps.
Here's my checklist as I'm reviewing the submissions:
- Code styling. The New York Times has a good summary of appropriate Objective-C coding conventions, you should take a quick look here.
- Was the current user persisted across restarts?
- Did you create a custom Tweet cell and properly set up Auto Layout constraints?
- Did you augment the User and Tweet model with the required properties?
- Date parsing and formatting is expensive, so consider caching in models when you can.
- Does tapping on a Tweet take you to a detailed Tweet view?
- Is the detailed Tweet view styled like the mock?
- Did you add both standard and retina (@2x) image assets? A new feature of XCode is to use the Images.xcassets, it makes it easier to handle the standard and retina assets. If you only included standard assets, it will be scaled for retina displays which makes them a little blurry.
@timothy1ee, Done with the twitter homework. Things went much better this time round. I'm especially happy with the animation on the 'sign in' screen.
I basically made the equivalent of an animated gif. Any thoughts on how to do this in a more efficient way? It take 250 images which bloats the codebase and slows down load time. I had to write a ruby script to slice out all the images in 1px offsets from a 1000px wide original. Kinda a pain, but it looks really nice, so worth it. I'm guessing I could have used the original and moved it along a viewport or something.