General question, what are the process of making i...

# getting-started

[UnAn]

General question, what are the process of making in concrete the app? I have my documentation on what the app does, its functionalities and then?
Do i start with the database? Then make the layout? Then logic? And then the "front-end"? What is the correct process?

[Adam Powell]

there is no "correct" process, only an infinite number of strongly held opinions about it 🙂

[Adam Powell]

if someone tells you they know the "correct" process they are probably selling books, training courses or conference talks about it

[Adam Powell]

imho, start from some code that runs; a basic hello world or test, and grow it from there based on what you need

[tddmonkey]

“Incrementally” 😄

[Cicero]

I would look for an architecture first, this can really help your mind understand better how to lay your cards.
I like to work balancing the level of mental stress of the tasks.
Some days I do dumb work that must be done and no one wants to do, some days I do nice work that everyone wants to.

The biggest secret is find the balance to keep your brain motivated and the rest comes naturally.

[Cicero]

For example, I regret that I didn’t use Interactor/UseCase earlier. Or that I didn’t used repository architecture in the beginning just because I didn;t needed it yet, this stuff comes easier when you do it, as our comrade said, “incrementally”

[Adam Powell]

on the flip side, I've never seen self-inflicted code messes as profound as those created by people who adopted one software architecture or another before understanding what specific challenges it addresses. Don't go architecture shopping until you understand your requirements 🙂

[Cicero]

True that, but then if you don’t understand fully which challenges wait you in the future you don’t have “documentation on what the app does and its functionalities”.

If you have a blueprint of the app you can already decide if you are going to need Repositories.

I don’t see UseCase/Interactor as optionals anymore as they make the code way more readable/testable/portable(recently made my path to Kotlin Multiplatform very easy).

And MVVM is standard.

Looking for an architecture meant: Know the basic rules of android development.

:)

[tddmonkey]

lol @ “architecture shopping”

[tddmonkey]

If you’re relatively new to designing apps, just go in with a mindset that you’re gonna make a ton of mistakes. Learn from them and do the next one better.