Hey guys, first rant,

At the moment I'm developing a very big and complex app. We are almost done and decided to deliver a test version to our customer. After he received our test he called us and said there is a problem with a function, he just said it's not working and wasn't very specific.

So I decided to check his problem, because an colleague couldn't figure it out.
I started the app via android studio and had a similar problem, there was a huge delay at the automatic recording function of Bluetooth messages, I thought yeah this is his problem.
I showed it my colleague and he said that he doesn't have this problem, we have different Bluetooth simulators so we thought that there must be a problem with the Bluetooth communication or the simulators are broken.
I checked if there is some kind of timing or buffer problem and logged the shit out of the simulator and found nothing, 3 hours were lost🏁.

My colleague checked his last changes because he had changed a lot at the App Api do to new conditions and those customer wishes💀 he couldn't found anything. So we thought maybe it's my device and the device of the customer. We switched the devices and tada no problem with my devices if the app is builded at the pc of my colleague.

I thought ok maybe it's because I turned some ndk features off. Turned it back on, nothing happened. So we exchanged our Android Studio Settings but no difference. So I said yeah whatever my mashine is just fucked. I restarted my mashine for the third time and started android fucking studio. Some little popup showed up "new updates"... the solution came to my mind ... Do to an update of android studio I excidently turned on Instant Run.....🌋 . I checked it, it was activated, these fucking instant run, great idea but not working... Turned it off, everything worked.
I called the customer because he can't have a problem and he said, this time not angry, oh yeah it was just a notification if I want to turn on my Bluetooth and I decided no and the Bluetooth recording is not recording, this is a problem... -😠NO FUCKING COMMENT😤-

More like a sub company/department inside a company: Android.

I still use it as my main driver, but every time I try to get back into development with it(did it professionally for 2 years nearing on 3 and was a lead Android dev, mind you not necessarily by merit....) I end up hating everything about it.

The tooling is meh, the API is hideous and even with the addition of Kotlin, which I do find a nicer language over Java I still dislike it. The ammount of shit needed to make something as simple as store data, manage fragments, integrate with the NDK, make JSON API calls or even shake motions is just ludicrous and counter intuitive. I can see why people would hate Java based on Android, a language that I generally love and defend.
I firmly believe that people extend frameworks or tooling for 2 reasons only:

1 the stack is so awesome that you just want to create packages and libraries to extend the functionality of a powerful environment, like gems for Ruby, python packages, Node packages, php composer, nuget etc

2 the stack is so fucking hideous that people need to fix shit: the entire android square utility framework, butterknife, flutter, react native, codenameone, etc etc

The case with Android is the second. I have not met a professional Android developer that completely likes everything about Android, but will seldom find people that HATE other frameworks or environments.

Android it is for me. Still my daily driver and I love every Android phone I have ever owned. It just makes me feel lots of more compassion for fellow Android devs.

You know you're fucked when the official advice is to use some experimental build tool

So I was watching Your Lie in April while waiting for Android to build

Let's just say that wasn't a pleasant experience after NDK OOM'ed the exact time the saddest part happened

IM NOT CRYING YOU'RE CRYING ;_;

Not quite sure what to rant about, but it sucks:
- Why the FUCK is Windows taking bloody TWO MINUTES to delete Android NDK?
- Why the FUCK does it take ANOTHER two braindead minutes to delete that from the waste bin?
- Why the FUCK is Android NDK so bloated to begin with?
- Why the FUCK have I still not come around to equip my 8 year old PC with an SSD?

Error in while using android ndk. Error message just contains the CPU registries. Fuck

At my first professional experience, just coming out of university and with no experience on Android. And the company put me doing a port of a VoIP lib of a Desktop application in C++, to be used as a mobile lib for Android app. At that time C++ wasn't supported by the Android ndk.
So my work was learning about android ndk, learn about jni, find out a solution for the non supported C++ in the ndk and learn about a proprietary lib for VoIP.
3 months later and with a lot of help I was able to put it to working (forget about performance). Still they told me my work wasn't good enough and I should have done a better job. For a noob developer that was hard to take.

started to try out xamarin. a ideal way to write it once and use it in 3 apps. on windows all was fine. android sdk adn ndk installed everything ok. starts to looked at ios hmm, you need mac to build project, simulate. oh wait even the UI designer you need mac pc.

WTF is going on here, are you serious apple. come to think of it, now i get how apple sales numbers are high. when developers and companies need to by apple pc in order to make a fucking app for them. but that's not all you need to pay 100euro a year to publish the app.

Has anyone tried kivy for android on a mac using the newest android sdk and ndk?

If the answer is no, god bless you and your unhurt soul.

Spent the weekend to configure my pc to be able to build Love2D to Android. Had problems with NDK, but it turns out that I need to install an old version of it (release 9 to be exact). Productive weekend ftw!