Search Results for "unity sample project"

Android Clean Architecture Kotlin is a sample Android project that applies Clean Architecture principles using Kotlin. It explores how Kotlin features and functional programming ideas can improve a layered mobile architecture. The project separates responsibilities across UI, domain, and data concerns to reduce coupling between framework code and business logic. Its UI layer follows an MVVM approach, while repositories organize access to application data.

Android MVVM Architecture is a Java sample application that demonstrates the Model-View-ViewModel pattern for Android development. Its interface layer connects views with ViewModels so presentation state and behavior remain separate from activities and fragments. The data package centralizes access and manipulation, while Dagger 2 supplies dependencies throughout the project.

Android MVP Architecture is a detailed Android sample project that demonstrates the Model-View-Presenter pattern in a structured application. It separates interface code from presentation logic by pairing views with dedicated presenters. A data layer handles access and manipulation, while a service layer contains application services. Dagger 2 supplies dependencies, GreenDAO provides local persistence, and RxJava coordinates asynchronous work.

An asynchronous, callback-based Http client for Android built on top of Apache's HttpClient libraries. Make asynchronous HTTP requests, handle responses in anonymous callbacks. Requests use a thread pool to cap concurrent resource usage. Multipart file uploads with no additional third-party libraries. Tiny size overhead to your application, only 60kb for everything. Automatic smart request retries optimized for spotty mobile connections. Automatic gzip response decoding support for...

Android Clean Architecture is a sample Android application demonstrating Robert C. Martin's Clean Architecture principles in a mobile project. The codebase separates responsibilities into presentation, domain, and data layers. This organization demonstrates how business rules can remain independent from Android-specific interface and persistence concerns. The project accompanies a series of articles explaining the architectural decisions and their evolution.