How convenient is it to work in a large (Android) project?

Question

I created an Android app some time ago and uploaded it to Google Play. I am very happy because users like my application and requests updates and improvements.

My project is getting bigger and bigger, and it has reached such an extent that I am afraid to make a difference because I can break something else. I also sometimes reflect on all parts of the program. Honestly, this underlines me a little. I like to do small projects, and it's convenient for me to write code. I would like to be relaxed while working on something big.

I work with Android Studio, by the way.

So, how convenient is it to work with large projects and not think about all parts of the program?

Thanks.

Answer 1

Dear user 3054843, The main thing is that this question and answer both can be said perfectly, because

• it differs from developer to developer
• & project for project,

large projects are not always difficult to manage and manage, sometimes they can be covered in less time and less effort.

sometimes small projects with unique and additional functionality can be difficult to handle due to the large amount of R&D.

Whatever it is, but at least deal with it to handle the project efficiently:

• divide the complete project requirements into modules.

• Create packages by function or packages by structure. (function packages are better).

• Try using separate classes and methods to avoid code complexity and easy to understand.
• If you need more functionality, use an open source library, if available, and according to your requirements.
• Do everything step by step and solve the problem, not skip it.
• Work hard.

thanks

Answer 2

First of all, I do not mean any tool or any specific method for processing large projects. But I can give you some recommendations that I try to apply in my daily life. First of all, write good code, well organized in accordance with the java rules (good class and variable names, packages, etc.). Secondly, avoid code repetition. Third, if you have a huge amount of code that does a certain job, create a library. This method reduces the size of your visible code. These 3 methods that I use to reduce the size of my projects (if necessary)

Answer 3

I guess one of the things you should have in the beginning is some kind of version control - git, svn, etc. Although version control is not limited to large projects, it will help eliminate the fear of changing something because you are afraid that you might break it. If you follow good branching techniques for managing new features and creating snapshots that you can use as breakpoints, then you have a way to manage deployment versions.

Some other obvious aspects have been mentioned - use proper OOP, keep your code relatively simple and modular so that you don’t get into a mess of nested statements / methods and the like. Focus on developing one function at a time, preferably using version control - use branching and other functions that you can merge into the main branch after it's completed. Correct your mistakes when you receive them, and try to understand why this gives you this error. I saw how people tried to “convince” their way of correction by writing more and more code that does not help at all.

Another thing that comes to mind is to look at some projects on github or elsewhere to find out how people manage their code. There are also podcasts and videos - ruby ​​presentations / podcasts come to mind - this can help with information on how to manage large codebases.

It is difficult to work and think about why your current workflow makes it difficult for you to develop, and then change some of the habits that you have. Good luck.