Mobiconf is a conference dealing with mobile technologies. It was launched in 2013, which makes this year the 5th edition. This means that the event is established and is beginning to attract better and better speakers. 2018 was the first time when mobile engineers of BinarApps decided to show up. We gathered a bold group of six and went on an adventure in Kraków on October 4-5. This article is a record from the perspective of Android and iOS engineers.

It was a stormy afternoon somewhere in Poland. In the town center, amid heavy rain, one could see a single window with a light on. In that room was a young programmer Peter, on the verge of exhaustion. He was working on fixes for a pull request after a code review.

Working with a software house is a guarantee of cooperation with experts in all areas, that make up the success. A single developer can rarely provide it.

I found, that developers like quick and simple solutions when it comes to deploying applications. One of them is Sidekiq integration for Capistrano called capistrano-sidekiq.

BinarApps for New Marketing, December 2017

While developing React application you will most likely need to fetch some data from API. If you're using class components a common place to do this is componentDidMount lifecycle method. But then you might be wondering how to properly write unit tests for it? In this blog post I will show basic examples how to write tests for HTTP calls inside class methods.

Pair programming with Docker, SSH and TMUX aka. distributed pair programming Pair programming is a well known practice in agile development. The principles here are simple: sit next to your colleague, let them write the code (the driver) while you will be planing/reviewing/instructing (the navigator). This practice separates the thinking processes of implementation and strategy from each other. It helps to focus on one particular aspect at the moment. Programmers all over the world are pairing to gain experience, increase productivity, solve complex problems, debug, refactor, etc.

You’re starting to develop your app: you’ve got an idea, you have thought through the business model, you are doing pretty well. And now the moment comes: the choice of technology. It seems like a really simple matter, but it can also wreak havoc on your business. So how to drown your startup? Just read this anti-guide.

In Android Marshmallow Google introduced new permissions system - now we request permissions in runtime. This approach is safer for the user, but for developers it is more code to write. We need to check if user willingly grants access and, if not, ask for it. Of course, old <uses-permission> in app manifest stays the same as before. Now there are two places serving nearly the same purpose. Next, call requestPermission() method (it’s required in our Activity class) and write callback with the results. Don’t forget about request code, same for defined methods! What if out app requires a really big amount of permissions? Activities can be overloaded with that logic and this causes a mess. Don’t worry - community comes with help.