Android + Kotlin + Hilt + MVVM: Taking app architecture to its best.
Publicado por Diego (1 intervención) el 08/10/2022 16:10:01
I'm attempting to take my multi-module app -developed using MVVM architectural pattern- to its possible best in terms of architecture and decoupling.
My app currently lays out a layer -module- (including dependencies) architecture as follows:
And I'd like any software architecture guy might be around here helps me determine if this structure could be improved in any way or if it is quite correct as it is.
My app currently lays out a layer -module- (including dependencies) architecture as follows:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
|- app -> All UI related stuff.
| |- DTO
| |- Common
| |- Background
| |- Core
| |- Services
||- Background -> Holds a class in charge of getting all the app data from the cloud in the background (initial process).
| |- Common
| |- DTO
| |- Core
||- Common -> Extension functions common to all modules (date/string/locale helpers, etc).
| |- DTO
||- Core -> Model plus services interfaces plus repository interfaces.
| |- DTO
||- DTO -> Only data transfer objects.
||- Repository -> Database operations (SQLite and AWS).
| |- Core
| |- Common
| |- DTO
||- Services -> Communication between UI and repo.
| |- Repository
| |- Core
| |- DTO
| |- Common
And I'd like any software architecture guy might be around here helps me determine if this structure could be improved in any way or if it is quite correct as it is.
Valora esta pregunta
0