API for selecting a contact in iOS seems unnecessarily difficult, it becomes a nightmare when you have to use it again and again at different places in your project. I think the idea of delegates is over-used in iOS, and they could have made things much simpler by relying on blocks instead.
Continue reading An Easy Way To Use Contact Picker
While some people argue against these functions, I think they are pretty good tools for rapid prototyping. And I really missed them in iOS, so I created similar functions in my iOS projects. Here is how they can be used:
Among many other things, scrolling is one that we take for granted when developing web apps. As soon as content grows beyond visible screen, good browsers themselves add scrollbars to the screen. Try making it work on an iOS app screen, you’ll be surprised how tricky this thing can get.
Continue reading How to make scrolling work on an iOS app screen?
There are a few things in iOS development which are surprisingly difficult, UIAlertView is one of them. If your UIAlertView contains only one button, which cancels the dialog, things will be easy. But as soon as you’ll think of adding more buttons to it, you’ll realize that you’ll need to create a delegate class and assign the delegate to the UIAlertView instance. This is ridiculous, because given the frequency of use of UIAlertView, you’ll end up creating unnecessary delegate classes.
Continue reading Taming UIAlertView
Recently I had to create this flow in one of my projects:
- Let the user select an image from the gallery.
- Store the image reference to Core Data.
- Later, load the image from the gallery using the saved reference and show image again to the user.
Here is how I did the job:
Continue reading How To Extract String Reference To An Image In iOS And Then Load The Image Later?