yes so the main development tool we will be using a slendroid studio so where we will be using the emulators to test all the scenarios and we will be creating multiple emulators for different Android versions because for each versions there may be a chance of functionality change like a compatibility change so we have to test with various versions and similarly different sizes so we will be creating an emulators with different resolutions and sizes to check the user interface related things whether it's working fine for all the different sizes and so Android studio will be helpful in various ways such as they'll be having a layout inspector so if like we can able to see or we can able to inspect our UI and so recently like the Jetpack compose will be we are able to we can able to see the number of compositions in the layout inspector so if we didn't code it properly there might be a chance of so many recompositions which may end up in a UI lag or issue in a performance of the mobile app similarly we have data inspector where like we can able to see all our databases like if you are implement if you have if you have implemented the database using room we can able to see all the tables and a structure of table and what data has stored in our application when we are connecting to the mobile app in a debuggable way and and so yeah so and we have network inspector tab in our Android studio which we can able to view all the network request which will happen in our mobile application we can track it on what is the request what is the response we got we can able to see all the request body what's the header parameters we are sending using network inspector and the main thing is like profiling which we it's there in the Android studio which will be helpful when we are debugging and seeing the performance oriented things like if there is any memory leaks or if there is in a performance lag we'll be using profiling tool to get to see whether any object is taking so much time or it's not deallocated it's not garbage collected we can able to see all those things in profiling regarding the gradle so we'll so we'll be adding all the dependencies in the gradle file like if there is any third-party library we have to add everything and so we have in build.gradle and app.gradle we have to add all those dependency and we have gradle w comments which we have to which we can use to build an application and so regarding ADB comments that third one so we'll be using ADB comments to run the application in physical device like we can make the system and the device in the same network we can use the ADB comments such as ADB connect with the like we can provide the IP to which the system has to get connected if you provide the IP the system will get provided get an connection to the physical device we can pair our physical device using ADB comments and if you give ADB devices it will just list down all the devices which is connected to the Android studio
