8 Tech-Related Blog Posts You May Have Missed in Q1 on the Macoscope Blog

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).


  1. Grand Central Board for the Apple TV – Oktawian is a frequent contributor to the dev community (with GitHub Awards to prove it) and spares no effort to try and master new stuff and improve his skills. This January, he was selected to participate in the Apple TV Tech Talks, which in turn, inspired him to make a board for the new Apple TV. This really creative and inspiring project is also Open Source and you can read all about it here.

  2. Using SpriteKit for Simple Data Visualization – Working with Oktawian on Grand Central Board, Krzysiek aspired to make a live visualization for the internal bonus system we use at Macoscope. SpriteKit seemed to be the perfect fit for his needs, as it provides graphics rendering, animation infrastructure, physics simulation, and sound playback. It’s used primarily in game development but we wanted to give it a spin in a simple data visualization app. Read more about using SpriteKit for simple data visualization here.

  3. Automate Testing & Build Delivery with fastlane and Travis CI – Continuous Integration (CI) and Continuous Delivery (CD) are both relatively fresh practices in iOS developers’ toolkits. This is mostly because we didn’t really have good tools to facilitate their proper deployment until recently. Gone are the days of breaking the build or tests without even noticing. Forget about archiving and sending builds manually to your testers or clients. Build servers are here to save us from this mundane toil. Read more on automating testing & build delivery with fastlane and Travis in Arek’s post here.

  4. How (Not) to Create a Spell Server for Mac OS X – A while ago, our developer Michal was asked to figure out how to implement a custom spell-checking service for Mac OS X. The service was commissioned by the people behind Remember, a remarkable project intended to prevent further use of the incorrect phrase “Polish death camps” by journalists and the general public. Read the full story on this spell server on our blog.

  5. Model-View-Presenter Architecture in Android Applications – Recently, clean architecture has been a hot subject in the Android development world. As developers, our responsibility is not only limited to delivering apps with a bunch of features, we also need easily maintainable code with clear separation between presentation and business logic. In the post, our Android developers illustrate the usage of the Model-View-Presenter architectural pattern as a method for developing Android apps with a clean architecture approach. Read all about it here.

  6. Summer at the Q Branch – Solving the Problems of Our Special Agents – We don’t offer internships all that often, but when we do, we always make sure they are as meaningful for both the team and the interns as possible. Last year, our summer interns worked on an app we use internally that allows us to order lunches from a small catering company we work with. See what they learned along the way.

  7. Simplify your Life with fastlane match – Fastlane match helps you by storing your certificate, private key, and provisioning profiles in a git repo. Read how you can simplify your life with fastlane match in Michal’s post.

  8. Storyboards and Their (Better) Alternatives – It seems that in almost every iOS project, one of the first questions developers ask themselves is: “Should we use storyboards, XIBs or write the whole UI in code?” 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. Find out more in Arek’s post.

Using SonarQube with Jenkins Continuous Integration and GitHub to Improve Code Review
How to Extend the OS X Color Panel with a Custom Color Picker?