Methodology for planning a mobile app

Question

Background:

I was thinking of starting a mobile app project alone, but not to be something tiresome and with no prospect of ending, I thought of organizing the activities in the method Kanban, after prioritizing the important aspects of the app, I noticed that reading the activities still had difficulty to abstract and visualize the final product.
I would like to avoid leaving the details vague as much as possible, because I know that everything must be defined before being developed, avoiding changes of direction in the middle of the project and so its extension, so I thought that an appropriate methodology for the style of mobile development could be adopted.
When searching on the subject, I could not find a solid methodology, only some articles suggesting adopting some positions on development, so I was left with some doubts as:

• Is there any methodology for this type of development that I did not find?
• Use an agile methodology of common software such as Scrum is something viable?
• Is there anything outside the Kanban that helps in the organization of the project and results in faster development?
• [Offtopic] Using a class diagram to better abstract the program is necessary and I will only be the responsible developer?

Answer 1

Thinking about Mobile App development can be seen equally as developing any software.

• You can find some methods that might have been created by focusing exactly on mobile development. Personally, I don’t know any particular one. But I believe your Organization and focus will be paramount in the final quality of the solution delivery.
• The use of agile methodologies has more to do with the size of your project than with the type of software you are developing. From an ERP to an App can be used techniques such as Scrum. In the end what determines the need is its objective of organizing development activities. For more extensive projects really would be a good way to organize and maintain the schedule of all the activities of a TEAM.
• I also do not know anything that can meet this requirement mentioned in the third topic. But in your scenario the initial planning you have done will most likely be enough for the project to be developed properly within your time. The speed of delivery will depend only on you.
• Whenever possible I like to use class diagrams to develop my projects, so I advise you to do as well, precisely so that you can better predict everything that will be created and already filter possible flaws in the implementation before even the code has been written.