I have an iOS 5.1 application that made use of CoreData in iCloud.
The user can take pictures and save it on iCloud too.
At the moment I am only saving an attribute picture YES or NO in an entity which should represent the event of taking picture, let say it's a kind of diary.

When YES I can calculate the path and retrieve the images. Actually there are three jpg images saved, a small to be used in UITableCell, a medium size for iPhone and a big size for iPad.
The maximum size can be at its maximum roughly 100kb.

Everything works fine, but I had to put some heavy logic into the app, for example to decide whether or not the images goes to iCloud, and in case of deletion if the images can be deleted too or moved locally.

In my development life I have never choosed to save images or binary in a DB, but this time I was thinking if the CoreData synchronization happening in the background could make my app more solid, and let me remove some lines of code. The idea is to add three attributes to the entity or probably for lazy issues, in another entity to be loaded as needed.

thanks