Not so long ago, a good friend of mine suggested that I could make a mobile application that could allow him, as well as other less experienced football scouts, to be able to collect and store analytical information on football players, to provide reports to clubs or agencies and also to communicate with more advanced scouts.

How can it be useful?

At the moment, there is no analogue to similar applications in the Russian segment. This is because there is no great need for it. Clubs don't want to spend money on it, and agencies don't have such resources. Moreover, the implementation takes too much time. And scouts are used to working according to their own schemes and storing information in notebooks and so on. However, it does not mean that such an application cannot be useful for young scouts. It would teach you how to make reports correctly, focus on the data that football clubs and agencies are interested in, and would also allow you to select those scouts who would have potential.

By that time, I had already worked enough in mobile development to make such an application. However, the right approach for the implementation was required, in order to understand what this product should represent as a result, and also design.

By a lucky coincidence, the last question disappeared by itself because my friend's girlfriend was just finishing her design studies at Yekaterinburg University, so her graduation project became our design.

Hello there! Recently, I had very cool experience at my work. I needed to set tableView with a dynamic header. The information in the header was complete in the initial state, and when the user was scrolling the table, some part in the header was smoothly hiding and the main part remained on the top. Cool, right?

Recently I wrote an article What is Reactive Programming? iOS Edition where in a simple way I described how to build your own Reactive Framework, and helped you to understand that no-one should be scared by the reactive approach. The previous article could now be named How to cook reactive programming. Part 0., since this is a continuation. I would recommend reading the previous article if you are not familiar with the reactive programming concepts.

Instruments for Apple's Xcode is a tool for performance analysis of an iOS application. In 2018 Apple introduced Custom Instruments — an opportunity to expand the standard set of instruments for application profiling. When existing tools are not enough, you can create new ones yourself — it will collect, analyze and display the data the way you need.

Preface

This article is an example of how we can do research into Swift Standard Library functions behavior building our knowledge not only on the Library documentation but also on its source code.

Unrecoverable Errors

All events which programmers call "errors" can be separated into two types.

• Events caused by external factors such as a network connection failure.
• Events caused by a programmer's mistake such as reaching a switch operator case which should be unreachable.

Swift 5 for Xcode 10.2 beta

Swift

Apple Swift version 5.0 (swiftlang-1001.0.45.7 clang-1001.0.37.7)
Target: x86_64-apple-darwin18.2.0
ABI version: 0.6

Swift apps no longer include dynamically linked libraries for the Swift standard library and Swift SDK overlays in build variants for devices running iOS 12.2, watchOS 5.2, and tvOS 12.2. As a result, Swift apps can be smaller when deployed for testing using TestFlight, or when thinning an app archive for local development distribution.