In an android project, I don't see how the following architecture can be considered MVC.
The team said:
- Android apps are fundamentally MVC
- the Controller is the Android Activity.
- the MVC View is the Android View.
This does not look like a correct MVC architecture to me,
so I disagreed because:
- they handle input events in their android view and act on the model directly
- then again some inputs are handled in the Activity...
- which means the Activity and Android View are cluttered with the MVC Controller / View responsibilities
- the Android View does not only draw / display the model but contains logic and is therefore not easily interchangeable
- there are several reasons for each of the classes to change
Did I totally misunderstand the MVC Architecture? The only thing I see here is that they definitely have a Model. But that's everything I can agree upon.
off topic: I recently started as a working student and I'm at the beginning of my CS studies as well and need some reassurance because I'm an effin noob. Everything I learned seems to be ignored in this company. No daily builds or unit testing, no comments, no documentation. When I talk to the supervisor, they don't need any of this.