Is MVC viable and recommended in Android projects?

Asked

Viewed 436 times

2

I am working on a mobile project where it is necessary to migrate a legacy application, which was developed to Windows Mobile 6.1 (handheld), to the Android.

This application has been developed using C#, with architecture in 3 layers, divided into groups of classes of View, Business and Data (winForms, BLL and DAL).

When migrating to the Android, is feasible, or recommended to use this type of architecture as well, or could there be problems? Or is there any architecture standard better recommended for large applications, on android?

1 answer

2


Hello! It all depends on your project. You can adopt on Android the architecture you want to develop your app, and there is no officially recommended for Android apps, as these are just concepts that can be applied in any language. In the case of a large application, a good option is to apply a concept that separates well the business rule, the interface and the data model (MVC) so that future maintenance is easy. If the architecture you mentioned does this, I see no problems or greater difficulties in applying it in an Android app.

  • 1

    Cool, the architecture I mentioned already does that. My doubt was in question to Android even, if I had any better recommended, as I’m starting on Android, I had no knowledge about.

  • 1

    using the MVC model makes code maintenance much easier

Browser other questions tagged

You are not signed in. Login or sign up in order to post.