How can you systematize the application development process?

Question

Android

I imagine what I want in the application, I even roughly understand how it will look like. But it's all in the head, the thoughts in which run faster than anything else. You think about one thing, a bunch of new thoughts immediately come up, you forget where you started. Perhaps, of course, the whole thing is in poor concentration, inattention, etc. reasons, but we will leave this question for another resource.
Here I want to ask about something else. How can you systematize the process of developing (at the moment the simplest) application. Or even like this: how to systematize the thoughts in your head about the future application? Maybe draw some kind of flowchart, or something else? Interested in the experience of independent work on the development.

Answer 1

12 stages of program development that change the planet
1. An idea arises
2. Write down an idea
3. Answer the questions:
a) why
b) to whom
c) is it necessary
d) is the development time worth the significance of the program
4. Draw the main algorithm
5. Draw parts of the algorithm thoroughly
6. Write a formula for counting and logic, define the main variables
7. Write down the variables on a notepad sheet
8. Determine the language, platform for the project
9. Draw the design
10. Program according to p.p. 5, 6 using step 7
11. Test
12. Release
You can also add paragraph 8a. Calculate the amount of time and the number of performers for the implementation of the project.

Answer 2

If possible, decompose the task into parts so as to minimize the links between them. Get started by writing the interfaces of the main classes. Drawing flowcharts seems like a thankless job to me. They are no more descriptive and much more time consuming than good pseudocode. Sometimes it is convenient to draw a hierarchy of classes, their interaction.

Answer 3

For my project, I simply write down the idea in the task list.
That is, the thought arose - I opened a notebook, more often paper and at night, wrote down the key words and continued to sleep.
I woke up in the morning, thought it over with a fresh mind, coded it, tested it, and put the prototype into production.
Actually, I write home accounting in this way.

Answer 4

1. @Reexel , +1 : read wiki for general understanding: Flowchart
2. Take MS Visio (diagrams) and build logic. (WEB alternative: draw.io )