If you are an iOS / MacOS developer who makes use of the snippets facility in Xcode you may occasionally find yourself caught out when working on a different Mac. This used to happen to me a lot in my contracting days. I have 10 years worth of snippets with auto completion keystrokes but on a Mac that doesn't belong to me they are worth nothing. There is a really simple solution that makes use of Apple's cloud infrastructure which allows the sharing of Xcode snippets between as many machines as you like. Here's how it's done. We will use the relatively low tech but insanely useful Symbolic Link approach, essentially moving our snippets to our own personal iCloud account, then creating a link, or signpost if you like, that Xcode will follow with no complaint, maintenance free once configured. The steps are easy to follow. be aware that Apple from time to time move where things live. So the snippets home today may not be where they live in 5 years from now, but I'm su...
Good User Interface / User eXperience practices are important. Hours of resources and research is dedicated to these subjects but sometimes the developer discovers an anomaly that has been missed in the planning. I came across this situation recently and contacted the relevant people to explain. They agreed with my suggestion and I implemented the change. Part of my development cycle is to test, test, and test again. And I tested my new code and all plausible possible situations. Tested for various targets. Tested on as many devices as possible. Released to UAT to test and got a code review from my line mentor. After all this the release build had a bug. In a nutshell when working with threading, be aware that there is a subtle difference between devices iPhone4 and iPhone4S. When creating an email on the device, if the process requires threading, do not create and display the MFMailComposeViewController object from within the thread. In the simulator set to all iOS ve...