Release iOS app on the App Store in 175 countries or regions?

The title of the post is the message shown when you are about to release a new version of an iOS app on the App Store Connect.

Release iOS app on the App Store in 175 countries or regions?

This confirmation request always lets me hesitate - am I really ready to release a new version of Little Go into the big, wide world? Such an imperfect app that has a confusing user interface (as a recent App Store reviewer put it) and that is probably full of undiscovered bugs. How dare I !?

This time it took me only two days to work up sufficient courage to finally press that fateful “Release” button. So let it be known that the newest version 2.1.0 of Little Go has been published today, 8 May 2026, and is now ready for download on the App Store. As usual, the release notes are available in the App Store update notes or on the GitHub release page.

Almost to the day 2 years after the previous release, this new version of the app adds time-based play to its list of major features. This was something I had planned to do for a long time, but it always got postponed because of one reason or another. Now the feature is finally here, closing the last major gap that Little Go has to most other Go applications.

The other two new features are geared towards allowing users to create game records with a rich set of metadata: The app now supports recording a game result, as well as entering 18 different so-called “Game Info” items. These are pieces of information that describe various aspects of the game being played, such as the dates when the game was played, player names, player ranks, the location where the game was played, and so on and so forth.

Besides being interesting user features, support for timed play and “Game Info” items also contributes substantially to the project’s secondary goal of providing near-complete support of the SGF specification. As of version 2.1.0, only 9 out of 67 properties remain unsupported. Of those 9, support for 3 will probably be added at some point, and 6 will likely remain unsupported indefinitely.

For the rest of the new stuff that version 2.1.0 brings, please refer to the GitHub release page linked to at the top of this post.