Android architecture

Feb 23, 20200 likes108 views

The document discusses SOLID principles and architecture patterns in Android development. It describes the five SOLID principles - single responsibility, open/closed, Liskov substitution, interface segregation, and dependency inversion. It then explains popular architecture patterns like MVC, MVP, and MVVM and compares their advantages and disadvantages. The goal of SOLID and these patterns is to make code more reusable, maintainable, flexible and suitable for team development.

SOLID Principles
&
Architecture in Android

SOLID Design Pattern
! Reduces tight coupling between classes.
! Loose coupled classes minimise change in code.
! Helps in making code more reusable, maintainable,
flexible, stable and suitable to work in a team.
! SOLID represents 5 design principles.

SOLID- 5 Design Principles
! S - Single Reasonability Principle
! O - Open - Closed Principle
! L - Liskov Substitution Principle
! I - Interface Segregation Principle
! D - Dependency Inversion Principle

Single Reasonability Principle (SRP)
It says that there should be not more than one reason for a class
to change and has only one responsibility.

Open - Closed Principle (OCP)
• Open - Software entities should be open for extension.
• Closed - Closed for modiﬁcation.

Liskov Substitution Principle (LSP)
It states that Derived or child classes must be substitutable for
their base or parent classes.

Interface Segregation Principle (ISP)
• It state that do not force any client to implement an interface
which is irrelevant to them.
• Avoid Interface Pollution.

Dependency Inversion Principle (DIP)
• Talks about Coupling between two modules.
• High-Level Modules shouldn’t depend on low level modules.
Both should depend on abstraction.
• It focuses on the approach where the higher classes are not
dependent on the lower classes instead depend upon the
abstraction of the lower classes.

Architecture Pattern
! Software Architecture pattern promotes organised
programming.
! Separates application functionality which is easy to test
and provide low cost maintenance.
! MVC, MVP, MVVM are some popular design pattern.

MVC (Model View Controller)
Controller
(Activity/Fragment)
View
(Rendering UI)
Model
(Data State + Business
Logic)
Trigger request
Process
the
request
Update
response
N
otifies
Sometimes interact with View

Advantage
! It keep business logic separate in the model.
! Support asynchronous techniques
! Modification does not affect the entire model
! Faster development process
Problem
! Due to large code controller is unmanageable.
! Hinders the Unit testing
! Increased Complexity

MVP (Model View Presenter)
Presenter
(Intermediate)
View
(XML/Activity/Fragment)
Model
(Data State + Business
Logic)
Inform
user action
Process
the
request
Update
response
Save
&
N
otifies

Advantage
! Code is more readable and maintainable
! Easy testing as business logic separated from UI
! Reusable of View and Presenter
Problem
! Tight coupling between View and Presenter
! Huge amount of interfaces for interaction between layers.
! Code size is quite excessive.

MVVM
(Model View ViewModel)
ViewModel
(Intermediate/
RxJava/ LiveData)
View
(XML)
Repository
Local
(DataSource)
Remote
(DataSource)
Model
UI Event Observe
Response
Observe model, change callbacks
Send request
Send response
Receives
data
Receivesdata
Send
response

Advantage
! No tight coupling between view and view model
! No interfaces between view and model.
! Easy to unit testing and code is event driven.
Problem
! You have to create observables for each UI component.

More Cents
https://blog.mindorks.com/user/proﬁle/id/17193
https://github.com/vandanasri

Tha󰇳󰈬 󰈘󰈢󰇼!
@ask_vandana
https://www.linkedin.com/in/androidexpertvandana

The document discusses the SOLID principles of object-oriented design, which are a set of five design principles intended to make software designs more understandable, flexible and maintainable. It defines each principle: single responsibility, open/closed, Liskov substitution, interface segregation, and dependency inversion. Following these principles helps produce code that is less complex, more readable, extensible, maintainable and reusable with looser coupling between modules and better testability compared to code not following these principles.

Dependency Injection, Design Principles and PatternsJuan Lopez

This document provides an overview of dependency injection, including definitions, design principles and patterns. It defines dependency injection as a set of object-oriented principles and patterns that implement inversion of control and allow following the dependency inversion principle. The document discusses SOLID principles, design patterns like adapter and bridge that support loose coupling, and how dependency injection enables code that is extensible and maintainable through loose coupling.

MicroservicesĐức Giang Nguyễn

The document discusses microservices architecture compared to a monolithic application architecture. It describes how a monolithic application is built as a single unit, which makes it difficult to scale. Microservices break an application into smaller, independently deployable services that communicate over a network. This allows each part to be developed and scaled independently using different technologies. While microservices require more initial work, they provide benefits like fault tolerance, easy testing and deployment, and allowing services to scale independently. The document provides references for further information on microservices patterns and antipatterns.

Solidsavithaks2211

This document discusses SOLID principles for object oriented design. It begins with an introduction of the author and overview of topics to be covered. It then reviews basic OOP concepts and code smells to refactor. The main section defines the five SOLID principles: single responsibility, open/closed, Liskov substitution, interface segregation and dependency inversion. For each, it provides a definition, examples of conforming and non-conforming code, and discusses how it improves design. It closes with other agile/OOP principles and inviting questions.

Daniel leon design principles in the functional worldCodecamp Romania

This document discusses design principles in functional programming. It defines the differences between principles and patterns, with principles being more abstract rules and patterns being concrete examples. It outlines common object-oriented design principles like single responsibility, open/closed, and Liskov substitution and discusses how they can also apply to functional programming by focusing on functions instead of classes. The document concludes that principles are more abstract than patterns and that an over reliance on patterns can show a lack of underlying principle implementation in a language.

Why Automation is Required in Software Testing - OSSCamp 2014OSSCube

The document presents an automation testing solution and discusses challenges with the Selenium IDE. It proposes using the Selenium WebDriver as it supports various browsers and languages. The document also discusses different testing frameworks - modular, data-driven, keyword-driven, and a hybrid approach. The hybrid approach combines benefits of the other frameworks like reusable keywords and separation of test data from scripts.

Key principle of software architectureLilian Codreanu

This document discusses several key principles of software architecture: - Separation of concerns breaks applications into distinct features that overlap functionality as little as possible to optimize individual features independently. - The single responsibility principle assigns each component a specific feature to make components cohesive and easier to optimize if features change. - The principle of least knowledge states components should not know internal details of other components to make them cohesive and easier to optimize if features change. - The DRY principle avoids duplicating functionality across components to simplify changes and prevent inconsistencies. - Avoiding big upfront design allows for agile evolution if requirements are unclear.

Code Craftsmanship ChecklistRyan Polk

The document provides a checklist of topics for a code quality training agenda, including: TDD/automated tests, continuous delivery, refactoring, design patterns, emergent design, SOLID principles, SOA, paired programming, UML/object modeling, and miscellaneous code craftsmanship best practices. It notes that the list is not comprehensive and the goal is to help organizations determine which topics would be most valuable for their teams. Descriptions are provided for some of the highlighted topics.

DesignPrinciples-and-DesignPatternsBasavaraj Patil

The document discusses design principles, patterns, and GRASP patterns. It provides explanations of key principles such as SOLID principles, composite reuse principle, law of demeter, and others. It also explains important design patterns and GRASP patterns. Some key points: - Design principles like SOLID principles help avoid bad designs and guide developers to create designs that are flexible, understandable, and resilient to change. - GRASP patterns provide guidelines for assigning responsibilities to classes based on concepts like information expert, creator, and controller. - Design patterns are proven solutions to common programming problems that can be reused in different situations. Some patterns discussed are creational, structural, and behavioral patterns. - Applying the right

OO Design PrinciplesAnju Kanjirathingal

Object Oriented Design SOLID Principlesrainynovember12

This document discusses object-oriented design principles and patterns. It introduces the SOLID principles: single responsibility, open-closed, Liskov substitution, interface segregation, and dependency inversion. These principles aim to create flexible, reusable, and extensible code. Other principles discussed include composition over inheritance and least knowledge. Common design patterns are inspired by these principles to provide solutions for recurring problems. The document emphasizes that applying object-oriented principles leads to software that can easily adapt to changing requirements.

Solid design principlesMahmoud Asadi

SOLID is a popular set of five design principles for object-oriented software development. The principles are: Single Responsibility Principle, which states that a class should have one responsibility; Open/Closed Principle, which states that code should be open for extension but closed for modification; Liskov Substitution Principle, which states that subclasses should not break the functionality of parent classes; Interface Segregation Principle, which states that clients should not depend on interfaces they do not use; and Dependency Inversion Principle, which states that high-level modules should not depend on low-level modules and abstractions should not depend on details.

SOLID Design Principles for Test AutomaionKnoldus Inc.

The document summarizes the SOLID design principles for test automation. It begins by introducing the five SOLID principles - Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion. Each principle is then defined individually and examples are provided for how they could be applied to test automation. The benefits of applying each SOLID principle to test automation are discussed, including improved testability, lower coupling, organization, code maintenance, reusability, and overall architectural stability and flexibility.

Entity Framework: To the Unit of Work Design Pattern and BeyondSteve Westgarth

The document discusses issues with traditional ASP.NET application architectures and how the introduction of MVC helped address some problems. It then describes how the presenter implemented the Unit of Work pattern to help with testing and database consistency in their application. However, this implementation violated SOLID principles. The presenter improved the design by separating concerns into distinct layers and implementing generic repositories. This made the code more testable and decoupled from Entity Framework while better adhering to object-oriented design principles. In the end, the presenter advocates evaluating design patterns critically and continuously challenging accepted approaches.

SOLID Principles in OOPS ooooooooo.pptxbanjaaring

This presentation provides a comprehensive overview of the SOLID principles—five key design principles that help developers create more maintainable, flexible, and scalable object-oriented software. Each principle is broken down with clear explanations, real-world analogies, and practical code examples to aid understanding. Whether you're a beginner or an experienced developer, this presentation will strengthen your grasp of clean code practices and object-oriented programming design patterns.

SOLID principles-PresentQuang Nguyen

This document outlines the SOLID principles of object-oriented design, including Single Responsibility Principle, Open-Closed Principle, Liskov Substitution Principle, Interface Segregation Principle, and Dependency Inversion Principle. It defines each principle, provides examples, and discusses the benefits, such as increasing reusability, making code more extensible and flexible, and reducing coupling between modules. Applying these principles helps create software that is well-designed and able to easily handle changes, improving developer and customer satisfaction.

Software Architecture Taxonomies - modularityJose Emilio Labra Gayo

The document discusses software architecture and modularity. It describes a "Big Ball of Mud" architecture with no constraints that can be quick to develop but leads to high maintenance costs. Modular decomposition is recommended, with modules having well-defined interfaces and responsibilities. Key recommendations for modular design include high cohesion, low coupling between modules, and following principles like single responsibility, open/closed, and dependency inversion.

Software design principles - jinal desaijinaldesailive

"Up-Down Development & DSL-first approach", Владимир Мельник, DataArtDataArt

The document discusses Up-Down Development and a DSL-first approach to software architecture. It describes splitting an application into layers, with the presentation layer at the top interacting with users, an application layer in the middle coordinating tasks, a domain layer storing business logic, and an infrastructure layer handling lower-level functions. Tests start at the presentation layer and make the UI dynamic by adding mocked lower layers. A DSL-first approach treats the DSL implementation as the system and code in the DSL as system rules, allowing great abstraction and splitting concerns. An example refactors a system using this approach.

Mobile App Architectures & Coding guidelinesQamar Abbas

This document discusses various app architectures and coding best practices. It covers design patterns like MVC, MVP, MVVM and architectural concepts like dependency injection. It provides examples of these patterns and concepts for Android development. It also lists some important Android libraries and recommends focusing on app architecture for benefits like scalability, maintainability and testability.

Inversion of ControlShuhab Tariq

Solid principlesKumaresh Chandra Baruri

SOLID_Principles_Explained_Presentation.pptxSahanaRV2

Spring pptMumbai Academisc

Spring tutorial for beginners - Learn Java Spring Framework version 3.1.0 starting from environment setup, inversion of control (IoC), dependency injection, bean scopes, bean life cycle, inner beans, autowiring, different modules, aspect oriented programming (AOP), database access (JDBC), Transaction Management, Web MVC framework, Web Flow, Exception handling, EJB integration and Sending email etc.

Soild principlesAvidnyat Chiddarwar

Solid OO & Clean Coding is essential to successful Agile developmentSimon Gould

Object Oriented Concepts and Principlesdeonpmeyer

This document discusses object-oriented design principles including encapsulation, abstraction, inheritance, polymorphism, and decoupling. It then introduces the SOLID principles of object-oriented design: single responsibility principle, open/closed principle, Liskov substitution principle, interface segregation principle, and dependency inversion principle. Code examples are provided to demonstrate how to apply these principles and improve code maintainability, reusability, and testability.

Design principle vs design patternsPrabhakar Sharma

TrsLabs - Fintech Product & Business ConsultingTrs Labs

Hybrid Growth Mandate Model with TrsLabs Strategic Investments, Inorganic Growth, Business Model Pivoting are critical activities that business don't do/change everyday. In cases like this, it may benefit your business to choose a temporary external consultant. An unbiased plan driven by clearcut deliverables, market dynamics and without the influence of your internal office equations empower business leaders to make right choices. Getting things done within a budget within a timeframe is key to Growing Business - No matter whether you are a start-up or a big company Talk to us & Unlock the competitive advantage

Big Data Analytics Quick Research Guide by Arthur MorganArthur Morgan

This is a Quick Research Guide (QRG). QRGs include the following: - A brief, high-level overview of the QRG topic. - A milestone timeline for the QRG topic. - Links to various free online resource materials to provide a deeper dive into the QRG topic. - Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic. QRGs planned for the series: - Artificial Intelligence QRG - Quantum Computing QRG - Big Data Analytics QRG - Spacecraft Guidance, Navigation & Control QRG (coming 2026) - UK Home Computing & The Birth of ARM QRG (coming 2027) Any questions or comments? - Please contact Arthur Morgan at [email protected]. 100% human made.

More Related Content

Similar to Android architecture (20)

DesignPrinciples-and-DesignPatternsBasavaraj Patil

OO Design PrinciplesAnju Kanjirathingal

Object Oriented Design SOLID Principlesrainynovember12

Solid design principlesMahmoud Asadi

SOLID Design Principles for Test AutomaionKnoldus Inc.

Entity Framework: To the Unit of Work Design Pattern and BeyondSteve Westgarth

SOLID Principles in OOPS ooooooooo.pptxbanjaaring

SOLID principles-PresentQuang Nguyen

Software Architecture Taxonomies - modularityJose Emilio Labra Gayo

Software design principles - jinal desaijinaldesailive

"Up-Down Development & DSL-first approach", Владимир Мельник, DataArtDataArt

Mobile App Architectures & Coding guidelinesQamar Abbas

Inversion of ControlShuhab Tariq

Solid principlesKumaresh Chandra Baruri

SOLID_Principles_Explained_Presentation.pptxSahanaRV2

Spring pptMumbai Academisc

Soild principlesAvidnyat Chiddarwar

Solid OO & Clean Coding is essential to successful Agile developmentSimon Gould

Object Oriented Concepts and Principlesdeonpmeyer

Design principle vs design patternsPrabhakar Sharma

DesignPrinciples-and-DesignPatternsBasavaraj Patil

OO Design PrinciplesAnju Kanjirathingal

Object Oriented Design SOLID Principlesrainynovember12

Solid design principlesMahmoud Asadi

SOLID Design Principles for Test AutomaionKnoldus Inc.

Entity Framework: To the Unit of Work Design Pattern and BeyondSteve Westgarth

SOLID Principles in OOPS ooooooooo.pptxbanjaaring

SOLID principles-PresentQuang Nguyen

Software Architecture Taxonomies - modularityJose Emilio Labra Gayo

Software design principles - jinal desaijinaldesailive

"Up-Down Development & DSL-first approach", Владимир Мельник, DataArtDataArt

Mobile App Architectures & Coding guidelinesQamar Abbas

Inversion of ControlShuhab Tariq

Solid principlesKumaresh Chandra Baruri

SOLID_Principles_Explained_Presentation.pptxSahanaRV2

Spring pptMumbai Academisc

Soild principlesAvidnyat Chiddarwar

Solid OO & Clean Coding is essential to successful Agile developmentSimon Gould

Object Oriented Concepts and Principlesdeonpmeyer

Design principle vs design patternsPrabhakar Sharma

Recently uploaded (20)

TrsLabs - Fintech Product & Business ConsultingTrs Labs

Big Data Analytics Quick Research Guide by Arthur MorganArthur Morgan

Mobile App Development Company in Saudi ArabiaSteve Jonas

EmizenTech is a globally recognized software development company, proudly serving businesses since 2013. With over 11+ years of industry experience and a team of 200+ skilled professionals, we have successfully delivered 1200+ projects across various sectors. As a leading Mobile App Development Company In Saudi Arabia we offer end-to-end solutions for iOS, Android, and cross-platform applications. Our apps are known for their user-friendly interfaces, scalability, high performance, and strong security features. We tailor each mobile application to meet the unique needs of different industries, ensuring a seamless user experience. EmizenTech is committed to turning your vision into a powerful digital product that drives growth, innovation, and long-term success in the competitive mobile landscape of Saudi Arabia.

tecnologias de las primeras civilizaciones.pdffjgm517

Build Your Own Copilot & Agents For DevsBrian McKeiver

Procurement Insights Cost To Value Guide.pptxJon Hansen

ThousandEyes Partner Innovation Updates for May 2025ThousandEyes

Dev Dives: Automate and orchestrate your processes with UiPath MaestroUiPathCommunity

This session is designed to equip developers with the skills needed to build mission-critical, end-to-end processes that seamlessly orchestrate agents, people, and robots. 📕 Here's what you can expect: - Modeling: Build end-to-end processes using BPMN. - Implementing: Integrate agentic tasks, RPA, APIs, and advanced decisioning into processes. - Operating: Control process instances with rewind, replay, pause, and stop functions. - Monitoring: Use dashboards and embedded analytics for real-time insights into process instances. This webinar is a must-attend for developers looking to enhance their agentic automation skills and orchestrate robust, mission-critical processes. 👨‍🏫 Speaker: Andrei Vintila, Principal Product Manager @UiPath This session streamed live on April 29, 2025, 16:00 CET. Check out all our upcoming Dev Dives sessions at https://community.uipath.com/dev-dives-automation-developer-2025/.

Linux Professional Institute LPIC-1 Exam.pdfRHCSA Guru

SAP Modernization: Maximizing the Value of Your SAP S/4HANA Migration.pdfPrecisely

Linux Support for SMARC: How Toradex Empowers Embedded DevelopersToradex

Toradex brings robust Linux support to SMARC (Smart Mobility Architecture), ensuring high performance and long-term reliability for embedded applications. Here’s how: • Optimized Torizon OS & Yocto Support – Toradex provides Torizon OS, a Debian-based easy-to-use platform, and Yocto BSPs for customized Linux images on SMARC modules. • Seamless Integration with i.MX 8M Plus and i.MX 95 – Toradex SMARC solutions leverage NXP’s i.MX 8 M Plus and i.MX 95 SoCs, delivering power efficiency and AI-ready performance. • Secure and Reliable – With Secure Boot, over-the-air (OTA) updates, and LTS kernel support, Toradex ensures industrial-grade security and longevity. • Containerized Workflows for AI & IoT – Support for Docker, ROS, and real-time Linux enables scalable AI, ML, and IoT applications. • Strong Ecosystem & Developer Support – Toradex offers comprehensive documentation, developer tools, and dedicated support, accelerating time-to-market. With Toradex’s Linux support for SMARC, developers get a scalable, secure, and high-performance solution for industrial, medical, and AI-driven applications. Do you have a specific project or application in mind where you're considering SMARC? We can help with Free Compatibility Check and help you with quick time-to-market For more information: https://www.toradex.com/computer-on-modules/smarc-arm-family

Technology Trends in 2025: AI and Big Data AnalyticsInData Labs

At InData Labs, we have been keeping an ear to the ground, looking out for AI-enabled digital transformation trends coming our way in 2025. Our report will provide a look into the technology landscape of the future, including: -Artificial Intelligence Market Overview -Strategies for AI Adoption in 2025 -Anticipated drivers of AI adoption and transformative technologies -Benefits of AI and Big data for your business -Tips on how to prepare your business for innovation -AI and data privacy: Strategies for securing data privacy in AI models, etc. Download your free copy nowand implement the key findings to improve your business.

Role of Data Annotation Services in AI-Powered ManufacturingAndrew Leo

#StandardsGoals for 2025: Standards & certification roundup - Tech Forum 2025BookNet Canada

Book industry standards are evolving rapidly. In the first part of this session, we’ll share an overview of key developments from 2024 and the early months of 2025. Then, BookNet’s resident standards expert, Tom Richardson, and CEO, Lauren Stewart, have a forward-looking conversation about what’s next. Link to recording, transcript, and accompanying resource: https://bnctechforum.ca/sessions/standardsgoals-for-2025-standards-certification-roundup/ Presented by BookNet Canada on May 6, 2025 with support from the Department of Canadian Heritage.

Generative Artificial Intelligence (GenAI) in BusinessDr. Tathagat Varma

2025-05-Q4-2024-Investor-Presentation.pptxSamuele Fogagnolo

TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc

Most consumers believe they’re making informed decisions about their personal data—adjusting privacy settings, blocking trackers, and opting out where they can. However, our new research reveals that while awareness is high, taking meaningful action is still lacking. On the corporate side, many organizations report strong policies for managing third-party data and consumer consent yet fall short when it comes to consistency, accountability and transparency. This session will explore the research findings from TrustArc’s Privacy Pulse Survey, examining consumer attitudes toward personal data collection and practical suggestions for corporate practices around purchasing third-party data. Attendees will learn: - Consumer awareness around data brokers and what consumers are doing to limit data collection - How businesses assess third-party vendors and their consent management operations - Where business preparedness needs improvement - What these trends mean for the future of privacy governance and public trust This discussion is essential for privacy, risk, and compliance professionals who want to ground their strategies in current data and prepare for what’s next in the privacy landscape.

Cyber Awareness overview for 2025 month of securityriccardosl1

Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove

AI Changes Everything – Talk at Cardiff Metropolitan University, 29th April 2...Alan Dix

Talk at the final event of Data Fusion Dynamics: A Collaborative UK-Saudi Initiative in Cybersecurity and Artificial Intelligence funded by the British Council UK-Saudi Challenge Fund 2024, Cardiff Metropolitan University, 29th April 2025 https://alandix.com/academic/talks/CMet2025-AI-Changes-Everything/ Is AI just another technology, or does it fundamentally change the way we live and think? Every technology has a direct impact with micro-ethical consequences, some good, some bad. However more profound are the ways in which some technologies reshape the very fabric of society with macro-ethical impacts. The invention of the stirrup revolutionised mounted combat, but as a side effect gave rise to the feudal system, which still shapes politics today. The internal combustion engine offers personal freedom and creates pollution, but has also transformed the nature of urban planning and international trade. When we look at AI the micro-ethical issues, such as bias, are most obvious, but the macro-ethical challenges may be greater. At a micro-ethical level AI has the potential to deepen social, ethnic and gender bias, issues I have warned about since the early 1990s! It is also being used increasingly on the battlefield. However, it also offers amazing opportunities in health and educations, as the recent Nobel prizes for the developers of AlphaFold illustrate. More radically, the need to encode ethics acts as a mirror to surface essential ethical problems and conflicts. At the macro-ethical level, by the early 2000s digital technology had already begun to undermine sovereignty (e.g. gambling), market economics (through network effects and emergent monopolies), and the very meaning of money. Modern AI is the child of big data, big computation and ultimately big business, intensifying the inherent tendency of digital technology to concentrate power. AI is already unravelling the fundamentals of the social, political and economic world around us, but this is a world that needs radical reimagining to overcome the global environmental and human challenges that confront us. Our challenge is whether to let the threads fall as they may, or to use them to weave a better future.

TrsLabs - Fintech Product & Business ConsultingTrs Labs

Big Data Analytics Quick Research Guide by Arthur MorganArthur Morgan

Mobile App Development Company in Saudi ArabiaSteve Jonas

tecnologias de las primeras civilizaciones.pdffjgm517

Build Your Own Copilot & Agents For DevsBrian McKeiver

Procurement Insights Cost To Value Guide.pptxJon Hansen

ThousandEyes Partner Innovation Updates for May 2025ThousandEyes

Dev Dives: Automate and orchestrate your processes with UiPath MaestroUiPathCommunity

Linux Professional Institute LPIC-1 Exam.pdfRHCSA Guru

SAP Modernization: Maximizing the Value of Your SAP S/4HANA Migration.pdfPrecisely

Linux Support for SMARC: How Toradex Empowers Embedded DevelopersToradex

Technology Trends in 2025: AI and Big Data AnalyticsInData Labs

Role of Data Annotation Services in AI-Powered ManufacturingAndrew Leo

#StandardsGoals for 2025: Standards & certification roundup - Tech Forum 2025BookNet Canada

Generative Artificial Intelligence (GenAI) in BusinessDr. Tathagat Varma

2025-05-Q4-2024-Investor-Presentation.pptxSamuele Fogagnolo

TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc

Cyber Awareness overview for 2025 month of securityriccardosl1

Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove

AI Changes Everything – Talk at Cardiff Metropolitan University, 29th April 2...Alan Dix

Android architecture

1. SOLID Principles & Architecture in Android

2. Problem

3. SOLID Design Pattern ! Reduces tight coupling between classes. ! Loose coupled classes minimise change in code. ! Helps in making code more reusable, maintainable, flexible, stable and suitable to work in a team. ! SOLID represents 5 design principles.

4. SOLID- 5 Design Principles ! S - Single Reasonability Principle ! O - Open - Closed Principle ! L - Liskov Substitution Principle ! I - Interface Segregation Principle ! D - Dependency Inversion Principle

5. Single Reasonability Principle (SRP) It says that there should be not more than one reason for a class to change and has only one responsibility.

6. Open - Closed Principle (OCP) • Open - Software entities should be open for extension. • Closed - Closed for modiﬁcation.

8. Liskov Substitution Principle (LSP) It states that Derived or child classes must be substitutable for their base or parent classes.

9. Interface Segregation Principle (ISP) • It state that do not force any client to implement an interface which is irrelevant to them. • Avoid Interface Pollution.

10. Dependency Inversion Principle (DIP) • Talks about Coupling between two modules. • High-Level Modules shouldn’t depend on low level modules. Both should depend on abstraction. • It focuses on the approach where the higher classes are not dependent on the lower classes instead depend upon the abstraction of the lower classes.

12. Architecture Pattern ! Software Architecture pattern promotes organised programming. ! Separates application functionality which is easy to test and provide low cost maintenance. ! MVC, MVP, MVVM are some popular design pattern.

13. MVC (Model View Controller) Controller (Activity/Fragment) View (Rendering UI) Model (Data State + Business Logic) Trigger request Process the request Update response N otifies Sometimes interact with View

14. Advantage ! It keep business logic separate in the model. ! Support asynchronous techniques ! Modification does not affect the entire model ! Faster development process Problem ! Due to large code controller is unmanageable. ! Hinders the Unit testing ! Increased Complexity

15. MVP (Model View Presenter) Presenter (Intermediate) View (XML/Activity/Fragment) Model (Data State + Business Logic) Inform user action Process the request Update response Save & N otifies

16. Advantage ! Code is more readable and maintainable ! Easy testing as business logic separated from UI ! Reusable of View and Presenter Problem ! Tight coupling between View and Presenter ! Huge amount of interfaces for interaction between layers. ! Code size is quite excessive.

17. MVVM (Model View ViewModel) ViewModel (Intermediate/ RxJava/ LiveData) View (XML) Repository Local (DataSource) Remote (DataSource) Model UI Event Observe Response Observe model, change callbacks Send request Send response Receives data Receivesdata Send response

18. Advantage ! No tight coupling between view and view model ! No interfaces between view and model. ! Easy to unit testing and code is event driven. Problem ! You have to create observables for each UI component.

19. More Cents https://blog.mindorks.com/user/proﬁle/id/17193 https://github.com/vandanasri

20. Tha󰇳󰈬 󰈘󰈢󰇼! @ask_vandana https://www.linkedin.com/in/androidexpertvandana

Android architecture

Recommended

More Related Content

Similar to Android architecture (20)

Recently uploaded (20)

Android architecture