title: iOS - How do apps like Path optimize their table cells where every cell is (almost) different?
body: <p>So here's the issue i'm currently running into. </p>
  
  <p>I have an app that shows a Facebook/Path like feed with a UITableView. Let's say that my datasource has about 200 items and not all cells have the same content and cell height. Some have images and some don't. I was able to overcome the scrolling performance issue by initializing my cells with a reusable identifier in the following format: [NSString stringWithFormat:"entry_%d", some_id]. Things were going really well up until I started using the UIImagePickerViewController. As you can imagine I've been receiving a lot of memory warnings due to my large datasource/table. </p>
  
  <p>When playing with the Path's app and trying to load as many data into a single view; they do a really good job at both the scrolling performance and memory management. Their app also doesn't crash whenever I go into the camera mode.</p>
  
  <p>Any thoughts or theories?</p>
  
  <p>Thanks! :)</p>