Read on Twitter
Going all in with projects that seem abandoned for a long time with not up to date dependencies, uncharted business with magic numbers flying around is.... an opportunity! An opportunity full of excitement awaiting to be taken!
Some tips to start
Some tips to start
Start from the build.gradle files to have a birdâs eye view 
of the tech stack used. You can gain so much insight just from these files like does the project use retrofit? Is it using androidx or itâs quite old? Does it target the latest apiâs? What is the minimum supported?
of the tech stack used. You can gain so much insight just from these files like does the project use retrofit? Is it using androidx or itâs quite old? Does it target the latest apiâs? What is the minimum supported?
Next should be the Android Manifest. You can dive in to see which activity is the main launcher. Does the project include other activities? Maybe services? Take a look around and when you are ready navigate to the main launcher to dig deeper 
Another thing to keep in mind is the packaging and the layering. Does it use modules other than app? Does it rely in packages instead 
? Are they grouped by layer, by feature or even by type ie activities, adapters ( please do not do this 
)?
? Are they grouped by layer, by feature or even by type ie activities, adapters ( please do not do this )?
After the initial overview start small and by keeping notes. What seems daunting at first is actually quite easy when itâs broken down into small steps 
Final tip search for tests and if they do not exist, you can try add some before touching the old code
Final tip search for tests and if they do not exist, you can try add some before touching the old code
Always leave the project better than it was even by margins! Itâs all about being professional and true to your work at the end of the day! 
