In his last post, Mateusz presented our first step to making our office a little bit smarter. We developed and implemented a solution that allows us to open the front gate without leaving our desks, simply by pressing button in a desktop app. After simplifying the process of admitting guests to the premises, we decided that it’s high time to focus on making our own arrival at the office more convenient and geeky. Without further ado, let me introduce the Gate Key project.
In order to fully take advantage of the fact that an application is available worldwide, one must first localize it properly. Depending on the application, the region, and a host of other factors, the process of localization itself may change and require different amounts of resources.
Apple provides iOS developers with a number of different tools and utilities that significantly reduce the burden cost of localization. Using the
NSLocalizedString macro together with
.strings files is (and rightly so) considered a standard nowadays, but relying solely on the two can sometimes lead to suboptimal solutions. In this post I would like to demonstrate a way to handling localized strings that have to deal with plural forms.
Here at Macoscope, we believe in supporting other developers and we try to give back to the dev community whenever we can. You can follow our GitHub repositories, we support local Swift meet-ups and regularly share our know-how on this blog and in our newsletter. Since following blogs can be too time-consuming nowadays, I decided to gather the tech-centered blog posts you may have missed that we published over the course of the last quarter in one place. Most have already garnered acclaim of developers around the globe, but in case you missed them, here are all eight, listed and linked for your reading pleasure (definitely try to make time for them, there’s some true gems inside).
It seems that in almost every iOS project, one of the first questions developers ask themselves is:
It’s always hard to answer it because preferences tend to vary even among members of the most closely-knit teams. However, enforcing a consistent approach to the way UI flow is handled within an app almost always results in higher quality of the project.
Every decision of this magnitude requires the team to take a closer look at the pros and cons (or tradeoffs 🙅) of all available solutions. This article discusses the majority of the known (and popular) ways of dealing with UI flow management to help you choose the one that fits your or your team’s goals the best.
A while ago, Arek wrote an excellent blogpost about integrating fastlane with Travis in which he described how to set up Travis CI to build an app and send it to HockeyApp. One way of pulling that off involved storing the signing certificate in the repository; this way, Travis was able to easily access the certificate and the private key, decrypt them, and sign the application. It wasn’t the perfect solution: it required us to store the certificate and key in every project’s repo, and to update them every time the signing id changes. Luckily for us, there’s another fastlane tool that can help us out with our perpetual need to simplify the process of building stuff. Without further ado, let us introduce fastlane match.