1 year later.
March 28 2014
Very soon a year since version 1.0.0 was released. I've been working on
and off with the app (now version 1.6.4) which means there has been a
lot of updates. The app works really good and is 100% stable with exactly
no crash reports ever.
I'm still no fan of Java programming, in fact I dislike it even more now.
The biggest drawback is that one can not easily mix code written in other
languages such as C++. That's one of the strengths when programming for
iOS, mixing C++ and Objective-C is super simple. Also I really miss the
C preprocessor or something similar to make it easy to test different
code paths. But I will continue to work on the Android version, I guess
the next big thing will be 64-bit support when Android version 5 appears?
2 years later.
April 8 2015
Two years since version 1.0.0 was released. I continue to develop the
app (now version 1.9.0) and have added some new features and support for
more file types but also skipped supporting earlier Android versions than
Android 5 Lollipop is released with support for 64-bit devices and Amazing
Slow Downer of course works fine there. The current version 1.9.0 has
native support for Intel 32-bit processors, there aren't that many Intel devices yet
but I guess they will become more and more common. The next version will have native
support for ARM 64-bit devices (Nexus 9 etc) and I also plan to support
Intel 64-bit devices. Native support is important since else all DSP code
will be emulated. This makes the audio processing very slow which drains the battery very fast.
3 years later.
April 24 2016
Three years since version 1.0.0 was released. The current version is now
2.1.3 and I've added some more settings and support for AMR audio files
(anyone using that?) and fixed the last bug that could crash the app.
Crashes was very rare even before this last fix (December 2015 version
1.9.4) and since then there are exactly zero crash reports!
The biggest addition is support for Spotify playlists, which was very
tricky to implement (Android audio programming is difficult). As with
the iOS version, I wanted the player to work exactly the same regardless
if playing a Spotify song or a regular physical audio file stored on the
device. Some of the most difficult programming I've been doing so far
(mixing Java and C++ code isn't what you want to do for your every day
May 29 2017
Four years since version 1.0.0 was released. The current version is now
2.3.1 and the biggest addition is probably that the app now works on Google
Chromebooks. Other than that it's mostly minor changes that I've made
to the app. Why? Programming should be fun and Android/Java programming
is among the most boring stuff I can think of. Since C++11 arrived a couple
of years ago my feelings for C++ is stronger than ever, it's almost like
falling in love a second time. Then having to mess with Java, which is
garbage collected programming language invented for moderately gifted
programmers, is dull. I rather spend my time writing apps in C++ or painting
watercolor. Maybe I'm getting old?