dependency Injection makes your code scalable and testable. Dagger2 is almost de-facto dependency Injection framework in Java these days, and, Its supported and used by Google which makes it first choice of all Android Developers.
Do you remember the last time you setup an Android project? How long did it take you after creating a new android project from Android Studio to customize and scaffold it before you could write the first business logic? Did you remember to setup the
iOS certificates and Provisioning profiles, most avoided topic for all iOS developer, specially for all the beginners out there. From iOS 10 onwards signing is required, even for development build and running your application on simulator and devices. So it becomes very important for us to know how to manage our Certificates and Provisioning profiles.
Dealing with NotificationCenter is daily task for all iOS developers. Either it’s a system notification such as KeyboardShow/KeyboardHide or CustomNotification to post some information app wide, we all have used Notifications.
We have been trying to include more and more reactive approach in apps that we build at moldedbits. Now that I am little more comfortable with reactive way of doing things I decided to write a blog on reactive vs imperative way of solving a problem. I will try to explain how reactive programming makes developer’s life easy by doing more in less code.
I am currently working at moldedbits, after working here for a few months as a back-end engineer, I decided to change my technical area from back-end to the front-end. I believe it is a good move for my career and it will surely add to my benefit. So basically I am drafting this to let you know about the challenges I am facing working on front-end development, after a couple of months experience.
At moldedbits, we love reactive programming. The power of reactive lies in the operators, so we have created a github repo with examples for all the different operators. We are starting a series of blog posts to accompany the samples. This is first in that series.
Over the weekend I worked on a small Android app. Since it was a small project and I was mostly working alone, I did not care to add version control. Once it was finished, I decided to push it to GitHub.
In a recent application, I needed to use the PopupWindow on a screen. Simple enough. While development, I used the Nexus 6P running Android Nougat for testing and everything worked fine and dandy. The QA, however, reported that the Popup was not visible on Android 5.0 or 4.4.2 . After much trial and error, I found the trouble making code.