7 ms·
Android Studio 4.2
- blumomo 6y agoOpen Android Studio once a week and it will each time ask you to install something new. I am not against progress and small, iterative updates. That's what agile promises us and that's how we get quick feedback from customers, especially when building an MVP. But Android and Android Studio should become mature products at some point in time. Given they are constantly changing Android APIs and requiring multiple layers of compatibility classes, Android Studio will continue to remain a powerful teenager in its puberty still for a long while.
- kllrnohj 6y agoAre you confusing AndroidX & gradle updates with Android or Android Studio updates? Android & Android Studio, the core platform, doesn't update very often at all. Gradle does update regularly, as does AndroidX, and a typical Android app will usually have half a dozen dependencies all on their own update schedule. Plus the build tools & emulator get regular updates. All in all there's probably a dozen different individual components. But none of this is the result of "immaturity" nor does it make any sense to create a big huge monolithic update schedule.
- la_fayette 6y agoAndroid studio has a couple of minor or patch updates per month (https://androidstudio.googleblog.com https://androidstudio.googleblog.com). Every now and then when you open the IDE you are asked to update. Every Android developer knows that, it is almost a meme.
- nailer 6y agoWhy doesn’t it update itself?
- matchbok 6y agoHa, I wish. 10 years, and Android still doesn't have a good way to accomplish navigation, view models, state retention, or anything. 10 different support libraries, everything deprecated once a year, etc. The entire platform is a mess.
- cromwellian 6y agoJetpack Compose subsumes many of those and in a very elegant, coherent way, much like Swift UI, but IMHO better because it's based on pure composable functions.
- dmitrybrant 6y agoAll well and good, but only if you're just starting to build your app literally today. If your app was built more than ~6 months before the current iteration of Jetpack/AndroidX/etc, you'll never finish catching up with converting your code to the latest new patterns that they introduce.
- myko 6y agoWe regularly update our apps when these libraries update, even for projects 5+ years old. You don't need to switch to the latest "architecture" all the time. It's trivial to add Compose to mature apps, you don't need to convert the entire app immediately.
- dmitrybrant 6y agoWell sure, thankfully all these myriad ways of doing the same thing coexist without much issues, since they're all just wrappers around findViewById(). But I just wish they'd settle on a pattern that will endure for more than a single major version of the library.
- crossroadsguy 6y agoThat’s the problem. Once you’ve started adding Compose to your app and are finally midway through it there will this new shiny toy and the entire herd will be playing with it. Then what? Finish compose or leave it there and start with the new toy? While there’s always a fundamental way of doing it - you just need the damn view! But no! To avoid even writing exactly 3-4 lines of findViewById per class on an average someone decided it’s revolutionary to add Butter Knife to the project and so on.. Or maybe there’s some one who gets kicks from seeing so many annotations in the classes! Android ecosystem is really plagued by this fad culture imho. PS. Nothing could make me an iPhone user. But finally being an Android developer did that! Really that’s the reason.
- javajosh 6y ago> "Android Studio 4.2 includes all the major features and updates found in IntelliJ IDEA Community Edition 2020.2" And yet IntelliJ is at 2021.1. Does Android Studio always lag the IntelliJ releases like that?
- sa46 6y agoMight be a similar situation to the IntelliJ Bazel extension by Google which is consistently 6-12 months behind the latest release. That extension just jumped to 2020.2 as well. My guess is that the lag is a consequence of the single version policy in the monorepo. Meaning, you need to upgrade all dependencies on IntelliJ without breaking Google engineer workflows.
- broersa 6y agoDoes it work natively on Apple M1?
- jefft255 6y agoIt's based on IntelliJ IDEA Community Edition 2020.2, and M1 support was released only for the very recent version of IntelliJ. So my sort-of educated guess is that no it doesn't.
- intergalplan 6y agoThe bigger issue is the Android emulator, which AFAIK still only kind-of works on M1.
- drampelt 6y agoM1 support was just added in the latest canary version https://androidstudio.googleblog.com/2021/04/android-studio-arctic-fox-canary-15.html https://androidstudio.googleblog.com/2021/04/android-studio-...
- crossroadsguy 6y agoPlease don’t use that. I am in the process of returning my M1 and asking for a 32GB previous Pro model from my IT team. Knowing Google it’d take more than months to fix their shit.
- TrianguloY 6y agoAn empty hello world project (a simple TextView with a string resource) created from the new project dialog still creates an apk of more that 1MB size. And 99.99% (more or less) of all the data inside are unnecessary Google libraries and assets.
- andybak 6y agoIsn't that badly configured defaults rather than a reflection on anything significant (i'm not saying there aren't real issues - just that "size of the default project" might not be a good heuristic)
- mrtksn 6y agoHow does the Android Studio compares with Xcode? On Xcode, it comes with SwiftUI and UIKit libraries for interface building. Does Android Studio comes with a standart UI library? Does it support design tools to help you with building the IU through these libraries or is it code-first? How straightforward is the environment setup? On Xcode, building your first app is as complicated as creating your first CV on Microsoft Word. i.e, click new, choose a template and build from there or deep dive from scratch if you know what you are doing. Click run and in runs in the simulator, if you put your developer account you can run it on the real iDevice. Pretty hassle-free. Did Android Studio achieve similar level of hassle-free development? Xcode comes with some asset management tools where you can build libraries of images, colours etc. that will automatically adapt to things like device color theme, language or size(In your code, you refer to a resource in the asset manager and the correct asset is used depending to the parameters you set there). What is the situation with Android Studio? On Xcode, the default language is Swift and comes with all kind of other libraries that are targeting the latest iOS/MacOS releases. What is the state of art for Android development in therms of the language and OS support? Is everyone building on the native libraries that Google provides using Kotlin? iDevice simulators run with acceptable performance even on 5 years old Macbook Air. Last time I tried a to run the "hello world" app through Android Studio many years ago on the simulator, the performance was miserable. Is the performance at acceptable levels now? Thanks!
- jayd16 6y agoAndroid Studio is way nicer. It has all the same WYSIWYG features with the added support of a polished Java IDE at its core. There's much less signing, archiving, provisioning madness to deal with and there are no magic "fix this?" buttons that need to be found and pressed. You can have your own opinions about Android vs iOS dev but IMO the Android Studio is less confusing and frustrating than xcode.
- kitsunesoba 6y agoVery YMMV in my experience. Coming from an iOS codebase that had eschewed XIBs and storyboards entirely in favor of pure code views, I was disappointed to find that it's very difficult to write pure code UIs with Android Framework. Everything is geared toward XML layouts with many things being impossible or impractical to access from Java/Kotlin, which is extremely frustrating. And in place of code signing troubles, Android brings new challenges with things dependency management and ProGuard silently snipping out big pieces of required code if you don't tell it exactly what to do.
- erdo 6y agoQuite impressed with the level of scepticism and experience of the android devs on hacker news. In my experience it's not the norm - the android world seems to have more than it's fair share of cool juice drinking newbies that hang on Google's every word (with disastrous results). Present colleagues accepted of course. Ahem.
- halotrope 6y agoI recently had to do a quick proof of concept in Android. To my very surprise there does not seem any „right“ way to do anything. Especially overlapping and competing concepts everywhere. „Activitiy“ vs „Fragment“, Camera, camera2, camerax, kotlon, java, rxjava… The official android architecture repo illustrates this perfectly. https://github.com/android/architecture-samples https://github.com/android/architecture-samples
- taeric 6y agoIt is ridiculous how frustrating this aspect is. The pattern of deprecating stuff doesn't help. :(
- izacus 6y agoThere's no "right way" of doing things on the web either - but there's plenty of ways to choose that fit your organization and the way you work. Why is that a problem? That is - why do you need Google to tell you how to do your job well? (You also listed a bunch of orthogonal concepts and even 3rd party libraries. Are you seriously criticising the ecosystem for having good 3rd party libraries?)
- crossroadsguy 6y agoEvery single release of this abomination makes me hate it more and more. So much that I stopped being excited about it. And every Android SDK/OS release changes everything in your face. I think there are people at Google who need something to do so they go around changing APIs for the kicks and because they can. Then there are “the followers” in the Android developer world who would amplify every new fad and follow it like an excellent herd. Unfortunately transitioning to backend seems quite difficult. Design, whiteboard rounds all go well, “but you don’t know about that backend specific library” :(
- lokedhs 6y agoI haven't done Android development in years, but I do use IntelliJ Idea Ultimate edition for a bunch of Java and Kotlin stuff. If I want to do Android stuff, is there any reason to use Android Studio in favour of IDEA? It seems AS is based off of an older version of IDEA, so why not use use IDEA?
- izacus 6y ago> If I want to do Android stuff, is there any reason to use Android Studio in favour of IDEA? It seems AS is based off of an older version of IDEA, so why not use use IDEA? Mostly because IDEA is far behind on Android features and it takes awhile for it to merge in Google patches. You'll have issues with most cutting edge support like UI editors, Compose, new Gradle features, etc.