I'm working on a mobile project where you need to migrate a legacy application that was developed for Windows Mobile 6.1 , Android strong>.
This application was developed using C # , with 3-tier architecture, divided into View , Business and Data (winemms), BLL, and DAL ).
When migrating to Android , is it feasible, or recommended to use this type of architecture as well, or can there be problems? Or is there some better recommended architectural pattern for large applications in android?
Hello! It all depends on your design. You can adopt the architecture you want Android to develop your app, and there is no one officially recommended for Android applications, as these are just concepts that can be applied in any language. In the case of a large application, a good choice is to apply a concept that separates the business rule, interface, and data model (MVC) well to make future maintenance easy. If the architecture you mentioned does this, I do not see problems or greater difficulties in applying it to an Android application.
