hold yard

After switching to Xcode 9 on our CI extended UI tests started failing. It turned out that referencing elements from navigation bars set in storyboards by image name stopped working.

I'm not a fan of such approach in the first place, but there's no way to set accessibility identifier from Xcode's interface builder. UIBarButtonItem does implement UIAccessibilityIdentification but there's no way to change its values.

Super Mario Run - Part 2. It's All About the Coins

In 907-587-0690 I concentrated mostly on technical aspect of where Super Mario Run falls behind. I listed technical solutions or different game design which would greatly improve initial gameplay.

Here I want to concentrate on financial aspect of the game and the causes of poor App Store ratings. And no - saying that people are being jerks that don't want to pay for things is too simplistic and doesn't get us anywhere.

Posted on

Super Mario Run - Part 1. The Princess from Another Castle

On September 7, 2016 an extraordinary thing happened. Shigeru Miyamoto came on stage of Apple's annual iPhone event and announced that Nintendo will be releasing a Super Mario game on iOS this year.

It's big news, because it's very rare for a title of such magnitude run on non-Nintendo hardware. Even more so since the company promotes its own new console - Nintendo Switch. It shows that the company is expanding its interests and trying to take a first step into mobile entertainment market. Market which is new to them. One that they do not control anymore - the hardware, the software, nor the distribution and experience. And it my opinion it's visible in their first game - Super Mario Run.

Posted on


Last week, along with a couple of colleagues I attended the Mobile Central Europe (MCE^3) conference in Kinoteka, a sprawling cinema complex in downtown Warsaw.

This year saw the third installment of the conference, focused on bringing designers, developers, and everyone in between together to share knowledge with people from around the world.

Posted on

Plugin Architecture in Swift(ish)

I have a strange thing with plugins. Every application which has plugin support is much better from the one that does not, even if the core functionality is smaller. It's about the potential of community being able to tweak and bend the application to their own needs. It's partially a reason why I tried to implement plugin architecture in most languages and technologies I worked with. Now it's time for Swift.