Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "kitkat"
-
I have been a mobile developer working with Android for about 6 years now. In that time, I have endured countless annoyances in the Android development space. I will endure them no more.
My complaints are:
1. Ridiculous build times. In what universe is it acceptable for us to wait 30 seconds for a build to complete. Yes, I've done all the optimisations mentioned on this page and then some. Don't even mention hot reload as it doesn't work fast enough or just does not work at all. Also, buying better hardware should not be a requirement to build a simple Android app, Xcode builds in 2 seconds with a 8GB Macbook Air. A Macbook Air!
2. IDE. Android Studio is a memory hog even if you throw 32GB of RAM at it. The visual editors are janky as hell. If you use Eclipse, you may as well just chop off your fingers right now because you will have no use for them after you try and build an app from afresh. I mean, just look at some of the posts in this subreddit where the common response is to invalidate caches and restart. That should only be used as a last resort, but it's thrown about like as if it solves everything. Truth be told, it's Gradle's fault. Gradle is so annoying I've dedicated the next point to it.
3. Gradle. I am convinced that Gradle causes 50% of an Android developer's pain. From the build times to the integration into various IDEs to its insane package management system. Why do I need to manually exclude dependencies from other dependencies, the build tool should just handle it for me. C'mon it's 2019. Gradle is so bad that it requires approx 54GB of RAM to work out that I have removed a dependency from the list of dependencies. Also I cannot work out what properties I need to put in what block.
4. API. Android API is over-bloated and hellish. How do I schedule a recurring notification? Oh use an AlarmManager. Yes you heard right, an AlarmManager... Not a NotificationManager because that would be too easy. Also has anyone ever tried running a long running task? Or done an asynchronous task? Or dealt with closing/opening a keyboard? Or handling clicks from a RecyclerView? Yes, I know Android Jetpack aims to solve these issues but over the years I have become so jaded by things that have meant to solve other broken things, that there isn't much hope for Jetpack in my mind 😤
5. API 2. A non-insignificant number of Android users are still on Jelly Bean or KitKat! That means we, as developers, have to support some of your shitty API decisions (Fragments, Activities, ListView) from all the way back then!
6. Not reactive enough. Android has support for Databinding recently but this kind of stuff should have been introduced from the very start. Look at React or Flutter as to how easy it is to make shit happen without any effort.
7. Layouts. What the actual hell is going on here. MDPI, XHDPI, XXHDPI, mipmap, drawable. Fuck it, just chuck it all in the drawable folder. Seriously, Android should handle this for me. If I am designing for a larger screen then it should be responsive. I don't want to deal with 50 different layouts spread over 6 different folders.
8. Permission system. Why was this not included from the very start? Rogue apps have abused this and abused your user's privacy and security. Yet you ban us and not them from the Play Store. What's going on? We need answers.
9. In Android, building an app took me 3 months and I had a lot of work left to do but I got so sick of Android dev I dropped it in favour of Flutter. I built the same app in Flutter and it took me around a month and I completed it all.
10. XML.
If you're a new dev, for the love of all that is good in this world, do NOT get into Android development. Start with Flutter or even iOS. On Flutter and build times are insanely fast and the hot reload is under 500ms constantly. It's a breath of fresh air and will save you a lot of headaches AND it builds for iOS flawlessly.
To the people who build Android, advocate it and work on it, sorry to swear, but fuck you! You have created a mess that we have to work with on a day-to-day basis only for us to get banned from the app store! You have sold us a lie that Android development is amazing with all the sweet treat names and conferences that look bubbly and fun. You have allowed to get it so bad that we can't target an API higher than 18 because some Android users are still using devices that support that!
End this misery. End our pain. End our suffering. Throw this abomination away like you do with some of your other projects and migrate your efforts over to Flutter. Please!
#NoToGoogleIO #AndroidSummitBoycott #FlutterDev #ReactNative16 -
Alpha
Beta
Cupcake
Donut
Eclair
Froyo
Gingerbread
Honeycomb
Ice cream sandwich
Jelly bean
Kitkat
Lollipop
Marshmallow
Nougat
Oreo
Pie
Q ?
R ?
S ?
T ?
U ?
V ?
W ?
X ?
Y ?
Z ?
And then?17 -
Food and Programmers life:
Spaghetti —> My Code
Pizza —> We are spending the night working in the office
Power Drinks —> delivery date is tomorrow morning
Candy —> extra task
Coffee —> bug massage
Water —> wash your face, we have meetings in five minutes
Truffle —> fu** BlockChain
KitKat —> upgrade your phone please
Lollipop —> one more time please
Marshmallow —> do you like some Nougat?7 -
Sony.
I don’t *hate* them, but I had really high hopes for Xperia smartphones back then, five years ago.
So I saved up and bought one. That’s what I got:
1. It was getting slower and slower
2. Micro usb broke just months after I got the smartphone
3. Sticky fragile screen with absolutely no oleophobic coating
4. NO UPDATES TO KITKAT AND LOLLIPOP! They just left us behind!
5. The main reason.
I catch moments with my camera. For me, camera is a vital feature, the most significant factor.
I once needed it really urgent and it just said “Camera is unavailable”. And that’s all. Camera is gone forever, broken. Factory reset haven’t fixed it.
You, alongside with Meizu, turned me away from android irreversibly and forever. When I heard about no update, I literally felt abused. Just like a girl whom random fuckboy made a proposal to, fucked and then left just months later.
With that level of customer support, basic respect to me as a user and buyer and that level of quality control, fuck you and your sloppy bricks you call smartphones. Maybe things are changing now, but I don’t care anymore and hardly ever will.
P.S. it heats up as hell, fucking pocket stoverant xperia abandonware android xperia tx hate abandoned wk130 android update customer support updates sony3 -
Just discovered Chocolatey and how it installs stuff through a command line. FINALLY AN EASIER WAY TO INSTALL JDK, ANDROID SDK AND ALL THAT!!!1
-
Had a task of service discovery, went through following phases:
1. UDP broadcast
2. Wait why not Bonjour?
3. JmDNS for desktop works great
4. Android NSD on Lollipop, this is easy
5. Kitkat WTF..!! Why did you put it there when it's so buggy.
6. Replaced Android NSD with JmDNS and it's great
7. Network switching on Android... done
8. Wait how are others doing it.. JmmDNS.. awesome.. fuck not working...
9. Read mDNSJava is much faster... replace JmDNS.. why haven't they uploaded parent pom on repo
10. mDNSJava freezing my Android device... revert to JmDNS
11. Let's see if it works with Wifi Direct.... Come on why aren't you working...
12. UDP broadcast it is 😢2 -
Getting a file input to work in an Android webview was an unnecessarily complicated process.
Cheers Google...2 -
Just trying to set up my girlfriends Kodi box and found this in the manual. It's running android KitKat too. I feel ill.5
-
Googled for about 2 hours now and can't get this shit working. Trying to launch the Android Wear Emulator through Android Studio using KitKat 4.4 API. I created a new device within the device manager using 512 MB RAM and 128 MB VM. Square Display.
I am running on osx 10.11 El Capitan on Software Acceleration (because hardware doesnt even boot to the android logo). I get the following error when running using ./emulator:
Error while connecting to socket '127.0.0.1:1970': 61 -> Connection refused
emulator: ASC 127.0.0.1:1970: Retrying connection. Connector FD = 25
What does it mean? I couldnt find an asnwer on the net.2 -
What are the different ways by which an Android can play an audio?
I was recently doing a research on Android audio. And i wanted to know which libraries are responsible for audio/video play.
As far as i know media player and exo player are the two libraries which can be used to play user variety of audio/video files, application's raw/asset files and online stream files. Are there any other sounds beside system sounds which i forgot or other libraries which are also used for media playing?
And also what about these system files? Can we access system ringtones and notifications/ alarm tunes in a normal, non-rooted phone? I remember that my previous phone's music player (android kitkat maybe) was able to pick some system ringtones. Is it still possible now(android lollipop nd above) ?
Although i guess music in Android assets or raw files of some other app won't be accessable to my app, unless i am having screen record permissions? -
Why do I always get attached to dead/dying platforms 😖😫😭
I mean, I got the PSP Go a mere year before devs dropped support. (Still awesome for emulation because of the physical buttons)
I was really interested in windows phone for a while that I almost bit the bullet and bought it.(you obviously know what happened to the beloved windows phone platform)
And now suddenly a blackberry passport video pops up on my YouTube recommended feed and now I really want one.
The problem is the lack of apps, I was hopeful because it supported android runtime.
Then my hopes were crushed after I knew that its based off KitKat.
Which means one of my favorite apps doesn't work there (my beloved termux, I get a boner whenever I think about using it with an actual keyboard 😂)
Should i just bite the bullet? I'm too broke and that 200$ is kinda of a major purchase for me (I'm 17 in a third world country, so the piggy bank is empty AF)
God, why do I always get introduced to platforms too late...6 -
yesterday, I just swapped my sim card for some time with another. Placed it back....and voila! I can't enable data connection. I lost all my apn settings. To add to this, neither is it auto fetching the apns, nor i can manually change it! It shows some fucking error "apn settings not available for this user". I have another phone with same android version (lollipop) and everything works smoothly on it. These guys just broke everything after giving an upgrade from kitkat. Auto brightness stops working after a few hours, random reboots.... This is it... bye bye stock rom!
-
Are native Android apps easier to write now than like back in KitKat days?
I need a app that gets root permissions and reads a db file of another app (Yes my phone is rooted).
Anyone can give a gist, I forget do I need to create a Service background worker to do the DB reads... Or just need to send the op to a bg thread with a UI callback sorta like Node...
I did try writing a ReactNative app maybe last year just to try it out but can't seem to easily get root access... And the SQLite package is buggy, couldn't npm install on Win10...14