Tables are everywhere. We've used them in most of our apps, Projects 2 to 7, and also Projects 9 to 10. These can be styled nearly to the point where they're not recognizable as a table, but essentially any repeatable content is a table. So a list of tweets, list of e-mails, or a contact list is a table.
Tables should provide information in a reasonably succinct form. Important text should stand out, while supplementary information should be in a lighter color or smaller font. If an image is provided, be sure that it is large enough to be useful, and that the text wraps nicely around it. Think carefully about the position of the image; the position might convey important information (for example, in a messaging app images on the left might refer to messages being sent to you, while your image on the right might refer to messages that you sent out).
For those platforms that support disclosure icons (arrows, checkmarks, and so on), be sure to put them in the correct place for your platform. If tapping them does something other than the action that would occur by tapping the row, be sure to give enough of a tappable area for the user to target.
Some apps have added lots of gestures to table rows. TweetBot is a good example where swiping one direction will do one action, while swiping another direction will do another. Generally this is pretty novel, and users aren't going to do a lot of swiping on table rows, except if it looks like the content is deletable. In this case, they might swipe right-to-left to attempt to delete a row. (If the row is in fact something that can be deleted, then the appearance of a Delete button would be appropriate.) An example of this is shown in the following screenshot:
