80
eeee
6y

They might just as well rename Android Studio to Build Progress Bar Simulator 3000.

Comments
  • 3
    Haha I have the exact same plugin for my phpstorm πŸ˜‚ Nyan loading ftw
  • 0
    I don't get these Gradle build times. How big are your Apps?
  • 2
  • 1
    @polaroidkidd ..or what hardware is used? I believe hardware plays a big role. For example just the fact that you need certain intel CPU's for virtual testing in AS.
  • 0
    I'm on a MBP mid 2014. While connected to a secondary monitor (at work desk always the case), the performance degrades noticeably.

    Yesterday in particular I was building most of the time: I'm updating a library for my company's apps. That means I have to make changes, publish the library (one build), adapt to the changes in the apps, and then the fun part begins: the library behaves differently on different Android API levels. Yay. Loads of testing combinations to try. The apps require each other and our servers. Yay. Loads of manual testing, because we mock nothing since I started working on this and it's too much hassle to mock all the things. Not to mention back/forward compatibility...

    Yesterday I built so many times, I'm sure I've been looking at Nyan cat for at least 3 hours. One build is between 30–300 seconds.

    My next project: step back from making actual features, fixing bugs and regular maintenance; I will make all our stuff mockable so we can test stuff quickly.
  • 0
    I know it's a meme but if your iterative build time is longer than 5 mins then you are doing something wrong, even for big projects.
  • 0
    @PAKA it's less than 5 minutes, but try building 3 things simultaneously once every 15 minutes. If those three simultaneous builds take 5 minutes in total, then that's 20% of your time 😭
  • 0
    It's crazy how slow Grade is when building for Android compared a non-android project.

    Grade for Android: a lot of time
    Grade for my rather big Spring project (in Kotlin) maximum 20 seconds ~(Λ˜β–ΎΛ˜)~
Add Comment