In this article, I will not be discussing any particular facet of the three fundamental ingredients for any program (information stored in memory, computational logic, and control logic), but I will be discussing a principle which applies to all of the above; along with everything else. In fact, this principle is so powerful that I see it pop up regularly in just about everything I do, and have ever done.
Build a material design user interface using ConstraintLayout, and wire it up using Kotlin synthetic properties.
This course contains everything you need to get started with building and deploying Android applications using Kotlin. This means I take you from the most basic concepts and skills for using Android Studio, and we end by configuring some kind of device so that you can run your first Android App!
This article is intended to be an fairly comprehensive, but still accessible explanation of three layer architectures (emphasizing Passive View), and why you might want to try using something similar in your projects. It turns out that the why behind this question is quite important.
My best attempt at writing a generalized approach to determining the Use Cases (or Interactors if you prefer) of an Application.
I'm not sure if I'm just dumb, but I've almost never read a technical definition of a Java Interface which actually tells you where/when you might want to use them. Hopefully this tutorial will fill in some blanks for you.