As it turns out, many young developers have never created applications in the iOS Developer Center. Showing how to do it seems like a good idea, so I decided to prepare presentation about CloudKit and kill two birds with one stone.
When bringing to the smartphone market iPhone 6s and iPhone 6s Plus, Apple presented to the world 3D Touch. Thanks to the option of checking touch pressure, this function facilitates diversification of interaction of users with their phones at the moment of contact. This allows, for example, implementing application behaviours varying on how you touch a screen.
Sooner or later every programmer encounters the problem of synchronous execution of certain actions. For example: get user information from the API, parse server response, save data to the database, update the view, and many others. To make it even more, at some of these stages you still need to deal with error handling. The first thing that comes to mind and that seems to be the most reasonable and popular solution is using blocks. What could such code look like?
Swift 2.2 is the first official release of this programming language since the time it was made open source. This time the decision was made to introduce amendments authored by 212 contributors unrelated to Apple. Swift 2.2 is to be a transitional stage before the release of version 3.0. On one hand, there are a few updates interesting to users. On the other hand, the creators decided to withdraw some previously used solutions.
Swift language introduced a significant improvement of structures, and thus in many cases made them an interesting alternative to classes. Quite many functionalities of classes and structures are similar, but there are a few differences and because of them it is a good idea to consider which of these forms is more useful in what situation.
We encounter applications running in real time pretty much everywhere. Any chat or a game uses this technology. Creating communication that is based on the assumption that what is happening in reality should be immediately reflected in the application, it is unfortunately neither easy nor cheap. However for small applications we don't need to spend huge money on dedicated infrastructure. PubNub can help us.