BEYOND LAYER - Exploring DIFFERENT APPROACHES to android project ARCHITECTURE | Droidcon Italy 2023

🎟️ 2024 ticket SPECIAL PRICE: https://ticket.synesthesia.it/events/...
More information: https://it.droidcon.com/2024/

⏩ Chapter:
00:00 intro
03:47 Model View Presenter
04:45 Architecture Components
08:11 Repositories
09:57 And now Domain Layer
11:04 The Clean Architecture
13:09 Different approach Ui Layers
17:15 Different Features API
21:05 GOOGLE recommendations
22:38 What to USE
23:40 Problems in app with many screens
26:58 Multiple teams
28:56 Maintenance
31:05 Documentation
32:07 Communication
33:03 Library
34:22 Business strategy
36:45 It DEPENDS…

🛠 Over the years there have been lots of architectural approaches - until Google released its guidelines. The first ones were released in 2017, and enhanced in 2021.

✏️ After publishing its new architecture guideline in 2021 Google still left a lot of questions open regarding the finer details of how to structure your architecture:
Should every feature within the application be divided into these three layers? Or Is the global application divided into three layers?
Is there any difference in the structure of the code if:
The application has few or many screens
There is more than one user role in the application (fe user and admin role)
The app is built by one person, a few people, one team or multiple teams.
You are building the library, or whole application itself

💥 The two presenters of this talk, after many years of experience in creating and maintaining Android applications, have a divided opinion on the above-mentioned topic, and through this talk, they want to show the advantages and disadvantages of their visions of the Android project architecture.

👨🏻‍💻 Petar advocates that the whole project should be divided into three layers, therefore, into the three modules: UI, domain and data. In his opinion a feature is something that represents a value to the user, therefore is strictly related to the UI layer.

👨🏻‍💻 Wolfram advocates that each feature should be divided into these layers - and thus they might contain different domain models and multiple data modules, for example. As with microservices you use the same DDD principles here. Thus each feature might have its own language and information.
🎤 PETAR LJUBIC, Android developer, Troido
🎤 WOLFRAM RITTMEYER, Android developer, Openminds

📍Droidcon Italy was hosted in Turin, 12-13 October. Attended by 600+ participants and broadcast to an additional 100+ participants across the globe. The event was highly interactive with excellent presentations, high value networking and lots of engagement between the participants.
🎉 This year we will be in Milan, more Developers, more Speakers... we are waiting for you 📣

✅ Tweet:   / droidconit  
✅ Connect:   / droidcon-italy  
✅ Read: https://t.me/s/Droidconit

#droidconItaly23 #AndroidDevelopment #ProjectArchitecture #BeyondLayer #AndroidTips #CleanArchitecture #UIUXDesign #MobileDevelopment #TechTalks #DeveloperLife #AppDevelopment