Beyond what you need from VSCode specifically above, like doing remote pairing for example, you’d better use Android Studio for the rest. A way of adding capabilities that you need that is not available on it natively. This surely not meant to actually replace Android Studio as your main IDE but to complement it instead. As like Live Share extension mentioned above, you can also make use of some other interesting extensions like GitLens where you have rich git-related annotations right on the editor or Todo+ which is quite fun and geeky way to track your ever-growing task while you code with nothing but text file. Like, getting access to rich VSCode extension ecosystem. There are some other benefits that also interesting to look at. ![]() That just some major ones of the reason you might want to set it up. On the later case, VSCode has much all you need without being as resource-demanding and you can launch and work more conveniently. However, there is a case, like where you are mostly working with more internal and logic code with less need of UI matter, you need only very common tooling related to unit-test, code, refactor cycle. That is fine if you are in the development mode where you need many of all its integrated capability. ![]() Android Studio, with IntelliJ being its base, is notoriously heavy. So, being able to work with your project in VSCode automatically give you that capability. On the other hand, VSCode has a great support for it through Live Share Extension. This is something you cannot do (yet) with Android Studio. ![]() To do realtime remote pair-programming session with actual collaborative-editing and shared build/test. Using Visual Studio Code for Android Developmentįirst, why do you event want to do this when Android Studio is already a fully capable IDE available on all platforms.
0 Comments
Leave a Reply. |