[Android Advanced] Topic #2 - Architecture

Android Academy Minsk

A good software architecture allows the system to be easy to understand, to develop, to maintain and to implement. The most important principle to follow is <A CLASS="external" HREF="https://en.wikipedia.org/wiki/Separation_of_concerns" TARGET="_blank" DATA-MSYS-CLICKTRACK="0" REL="nofollow noopener noreferrer">separation of concerns</A>. It's a common mistake to write all your code in an <A HREF="https://developer.android.com/reference/android/app/Activity.html" TARGET="_blank" DATA-MSYS-CLICKTRACK="0" REL="nofollow noopener noreferrer">Activity</A> or a <A HREF="https://developer.android.com/reference/android/app/Fragment.html" TARGET="_blank" DATA-MSYS-CLICKTRACK="0" REL="nofollow noopener noreferrer">Fragment</A>. These UI-based classes should only contain logic that handles UI and operating system interactions. By keeping these classes as lean as possible, you can avoid many lifecycle-related problems. Together with you at a lecture, we will consider: 
<OL>
<LI>
Introduction to Architecture as meaning
</LI>
<UL>
<LI>
History
</LI>
<LI>
What problems we have in app development
</LI>
<LI>
Architecture matters
</LI>
<LI>
Solutions
</LI>
</UL>
<LI>
Main principles
</LI>
<UL>
<LI>
Create app (maybe our own app for fundamentals) which violates good architecture
</LI>
<LI>
Introduce SOLID (A brief overview)
</LI>
<LI>
Introduce KISS, DRY, YAGNI (Optional)
</LI>
<LI>
Fix app with those principles
</LI>
</UL>
<LI>
Clean Architecture overview
</LI>
<UL>
<LI>
Explain main points 
</LI>
<OL>
<LI>
History and author of approach
</LI>
<LI>
Basic principles 
</LI>
<LI>
Mention original structure and linear structure
</LI>
</OL>
<LI>
Layers and dependencies (how dependency go from one layer to another)
</LI>
<OL>
<LI>
Layers and Dependency Rule
</LI>
<LI>
Transfer to linear structure
</LI>
<LI>
Description about layers and entities
</LI>
<LI>
Description of Domain layer (UseCase/Interactor, Entities)
</LI>
<LI>
Description of Data layer (Repository Impl, Gateaway)
</LI>
<LI>
Description of Presentation layer (Presenter/ViewModel, UI)
</LI>
</OL>
<LI>
Start rework app to separate on layers and introduce it one by one by putting all logic in different classes and ui logic leave in ui
</LI>
<LI>
Introduce MVVM as a relationship between UI and logic
</LI>
<LI>
New business requirement
</LI>
<LI>
Develop new requirement
</LI>
<LI>
Show design code, how to include it into current architecture
</LI>
</UL>
</OL>
 
<DIV>
<DIV CLASS="gtx-trans-icon">
BTW, we create a <A HREF="https://t.me/androidacademyminsk" TARGET="_blank" DATA-MSYS-CLICKTRACK="0" REL="nofollow noopener noreferrer">telegram chat</A> for the discussions! 
See you soon!
Android Academy team.
Great thanks to our partners below!
 
<IMG SRC="https://cdn.evbuc.com/eventlogos/261394383/logo.png">
</DIV>
</DIV>
<DIV>
<DIV CLASS="gtx-trans-icon"> Info partner <IMG SRC="https://cdn.evbuc.com/eventlogos/261394383/devlogobrand-2.png"> </DIV>
<DIV CLASS="gtx-trans-icon"> </DIV>
</DIV>
<DIV>
<DIV CLASS="gtx-trans-icon"><IMG SRC="https://cdn.evbuc.com/eventlogos/261394383/androidbroadcastlogowithlabel300-1.png"></DIV>
 
</DIV>
<DIV>
<DIV CLASS="gtx-trans-icon"></DIV>
</DIV>

SPACE

Our {communityGuidelinesLink} describe the sort of content we prohibit on Eventbrite. If you suspect an event may be in violation, you can report it to us so we can investigate.

To report other categories of prohibited or illegal content, submit {link}

[Android Advanced] Topic #2 - Architecture

More events from Android Academy Minsk

Discover more events from Android Academy Minsk, from Science & Tech to other experiences you might love.

[Android Advanced] Topic #2 - Architecture

More events from Android Academy Minsk

Discover more events from Android Academy Minsk, from Science & Tech to other experiences you might love.

You might also like...

Browse more events with different dates, prices, and formats to find your next great experience.