The best part about being a developer to me is the ability to create something from nothing (and share it with the world).
Mobile development has been (and still is?) one of the most interesting roads you can take having this thought in mind, which is why I’ve been working as an Android mobile developer for the past 7 years. In that time, like everything in nature, a lot of things have changed, evolved for the better or dead-ended somewhere on the mount improbable.
One thing that also evolved trough time, understandably so, are the Google Play Console Policies. Sarting…
It’s quarantine days and everybody is doing something useful. I’m no different than the super cool people out there: I made the best tutorial for learning python on the Internet(s). The best part? It takes you 90 seconds to complete and after it you’ll be fluent in python!
Intrigued? Let’s go then: pythonin90sec.com
Yes, it’s a joke. Till next time.
This is going to be a long one. Also it can be found here.
This blog post (originally titled “Late for the Kotlin party”) has been in the file cabinet since spring and the “see the light of the optical cable” moment was postponed, because of, reasons. By now the original title has become outdated, but I kept most of the original structure and I think that the advises and notes in the post will work well for newcomers, so let it be.
It all started with the question — how do meaningless, basic, and some — just plain stupid apps become viral on App Store/Google Play? At least one of these downloads is yours — Crack your screen (10,000,000+), Windows XP error (1,000,000+), Yo (1,000,000+), Paper Racing (5,000,000+), right? Is there a way this seemingly stochastic process be predicted? There are many studies on the subject of virality, obviously it’s a great interest of many parties in fields ranging from economics to mathematics.
My approach is to take insights from human nature and evolutionary psychology — is there any roots into why…
Have you ever tried to loop sounds in Android? And how did it go?
Easy, right? Just call setLooping(true) on your instance of MediaPlayer and it’s done. There’s one small detail, though. When you set the .setLooping value to true and hear the result, if you don’t mind the silence gap between the loop, then you’re done. If, on the other hand, you need to do perfect loop with no gaps, well this is the blog post for you.
Writing automated tests before releasing an app should be part of the development process of reliable mobile application (and any other kind of piece of software for that matter). When it comes down to UI test and Android - Espresso seems to be the way to go. I’ll presume that you agree with me on both of those statements and move one with what this article is about.
Namely, if you have somewhat complex UI that involves AnimationDrawables and one way to find out whether some interaction pull trough as expected is to see whether an animation (animationdrawable resource) has…
Inspect Element. Enter short bio.