Apple is enforcing a stronger encryption that applications need to use when connecting to their backends. Is your server secure enough to meet Apple’s standards? Being HTTPS doesn’t necessarily imply that it’s good enough.
Apple’s latest operating system updates – iOS 9 and OS X El Capitan – are enforcing stronger network encryption. This is wonderful for users – however it could mean extra work for developers and system administrators.
In short, applications are strongly encouraged to use HTTPS, TLS 1.2 and perfect forward secrecy. You might be saying to yourself, “We’re already serving through HTTPS, so we’re good.” As it turns out, it may not be that simple. It isn’t for Microsoft and you could be affected as well. Yes, at least one of Microsoft’s web services isn’t yet up to Apple’s security standards as of this writing.
Are you yearning for Flurry Analytics or Google Mobile Analytics for your Mac OS X application? Seek no more as your day is saved!
Why trusting the lean startup methodology can cause false negatives for your otherwise bright ideas. See the pitfalls of running lean and how you can walk past through them.
Cocoa stores cookies on its own and this makes it hard to implement a web client that appears as more than one user at the same time to the web server. To do this you’ll need to make your own cookie storage and this article teaches you how.
Cocoa’s document architecture envisions that a window should only handle one document. However library-type applications may need one window to handle multiple documents so that the user can easily switch between libraries without restarting the application. Here’s how you can hack AppKit so that a single window handle multiple documents.