i am at the very beginning stages of developing a hybrid project, and am at a bit of a loss when it comes to deciding what kind of structural method to use. all of the advice I’ve read on the subject basically states that there is no one size fits all, and what matters most is your app’s core functionality and team’s need.
that being said, i don’t even know what kind of questions i should be asking myself as i go through this decision making process. as an architect outlines the needs of their project, or the major functionalities, what concepts should they be defining and how important is UI to this part of the process? how do i know what responsibilities to assign to an interface? and how would i gauge whether or not I’ve distinguished the layers clearly enough to avoid over complication? obviously i want to facilitate easy maintenance and testing, but i want the app to be as seamless and visually appealing as possible. i’m not sure how to support that or what i should be prioritizing. pls help.
coldramen22 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.