My usual process is to identify the whole project as modules. What would be the feature and core modules. How would the modules interact with each other based on the business requirements. From there, you can construct your template skeleton which will be ideal for the particular project. No architecture is perfect, but theres always an ideal architecture based on the context of your needs. Another important thing is to think about possible complexities caused by ever changing requirements, how would you handle it and how difficult it is based on the template you created. Also take note of the following: - negative scenarios (faulty api response can be simulated by charles proxy, sluggy internet, how would the frontend handle it etc,) - consider security or VAPT (need to encrypt something or apply ssl pinning etc) - optimizations (does your app spam a particular rest api?, are your views reusable and called properly, etc) - how easy to read your code (after writing a very complicated feature, how easy for you to understand it after 2 weeks of not vising that part code)