Pet project using Clean Architecture + MVVM + Reactive Extensions + Android Architecture Components.
The data is fetched from LondonTheatreDirect API.
*Data from London Theatre Direct
**UI inspired by Yaroslav Zubko's design
Uses concepts of the notorious Uncle Bob's architecture called Clean Architecture.
The software produced by this architecture is going to be:
- Independent of Frameworks.
- Testable.
- Independent of UI.
- Independent of Database.
The overriding rule of this architecture says that the source code dependencies always point inwards.
The outer tiers can only dependent of inner tiers. Therefore, the inner tiers know nothing about the outer tiers.
The more further you go through the concentric circles, the higher level the software becomes. Which means that the level of abstraction increases.
An entity is a set of data structures. These entities are the business objects of the application and encapsulate the most general and high-level rules, such as Event or Rating.
They are the operations of the application and may contain specific business rules.
This layer is isolated from database, UI, or any of the common frameworks.
All use case classes extends UseCase abstract class that sets up the schedulers of Reactive Extensions.
It is a set of adapters that convert data from the format most convenient for the use cases and entities, to the format most convenient for some external agency such as the UI or Database.
It is this layer that will wholly contain the ViewModels of MVVM architectural pattern.
The models are likely just data structures that are passed from the view to the use cases, and vice versa.
Similarly, data is converted, in this layer, from the form most convenient for entities and use cases, into the form most convenient for whatever persistence framework is being used.
The outermost layer is composed of frameworks and tools such as the Database and the Android Framework.
The Repository pattern is used to encapsulate the details about caching mechanism.
In order to not violate the Dependency Rule, the Dependency Inversion principle must be used whenever complex data needs to be passed across a boundary to an inward layer. Instead of expecting and directly referencing a low-level component (e.g. as a function parameter), the high-level layer provides and references an interface that must be implemented and inherited from by the caller. This way, the conventional dependency relationship is inverted and the high-level layer is decoupled from the low-level component.
To make the application more testable and avoid having to deal with object instantiations in many points, the Dependency Injection technique is used.
Dependency injection is one form of the broader technique of inversion of control. As with other forms of inversion of control, dependency injection supports the dependency inversion principle.
Dagger is the tool used for managing and injection of our dependencies.
The LondonTheatreDirect API groups the data into:
- System API: Obtain information about enum data types.
Since the data is basically static, a Repository with database caching is used by Gateway.
- Inventory API: Obtain realtime information about events on sale, venues, prices and availability.
Due the data volatility, it is used a Repository that caches in memory.
Register your account here to get your developer key and put it into gradle.properties file
- Android Clean Architecture Sample app that is part of a series of blog posts about how to architect an android application using Uncle Bob's clean architecture approach.
- Android Architecture Blueprints Demonstrate possible ways to help with testing, maintaining and extending of an Android app using different architectural concepts and tools.
- Android Support Library Provides additional convenience classes and features not available in the standard Framework API for easier development and support across more devices.
- Data Binding Write declarative layouts and minimize the glue code necessary to bind application logic and layouts.
- Android KTX A set of Kotlin extensions for Android app development.
- Android Architecture Components A collection of libraries that help you design robust, testable, and maintainable apps. Start with classes for managing your UI component lifecycle and handling data persistence.
- Dagger A fully static, compile-time dependency injection framework for both Java and Android.
- RX Java A library for composing asynchronous and event-based programs using observable sequences for the Java VM.
- RX Kotlin RxJava bindings for Kotlin.
- RX Android RxJava bindings for Android.
- ConstraintLayout Allows you to create large and complex layouts with a flat view hierarchy (no nested view groups).
- RecyclerView A flexible view for providing a limited window into a large data set.
- Glide An image loading and caching library for Android focused on smooth scrolling
- Retrofit A type-safe HTTP client for Android and Java.
- OkHttp An HTTP & HTTP/2 client for Android and Java applications.
- Moshi A modern JSON library for Android and Java.
- Room The Room persistence library provides an abstraction layer over SQLite to allow fluent database access while harnessing the full power of SQLite.
- Stetho A debug bridge for Android applications.
- Explain more about the architecture diagrams in README file.
- Improve and add more unit tests
- Add pagging on event list
Contributions are always welcome!
Issues: Fell free to open a new issue. Follow the ISSUE_TEMPLATE.MD
Follow the "fork-and-pull" Git workflow.
- Fork the repo on GitHub
- Clone the project to your own machine
- Commit changes to your own branch
- Merge with current development branch
- Push your work back up to your fork
- Submit a Pull request your changes can be reviewed (please refere the issue if reported)
Prevent code-style related changes. Format the code before commiting.
Copyright 2018 André Mion
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.