0 views collected around this technical thread.
This article explains how to introduce the ViewModel concept into a Flutter project and use Riverpod 2.0’s NotifierProvider to achieve a clean separation of UI and business logic, illustrated with a complete login‑page example and reusable code snippets.
This article explains the MVVM (Model-View-ViewModel) architecture for modern Android development, detailing its three core components, their responsibilities, and provides a step‑by‑step example with Jetpack components, including LiveData, ViewModel, View Binding, and complete code snippets to build a simple user list UI.
This article introduces the ViewModel concept and demonstrates how to use Riverpod 2.0's NotifierProvider in Flutter to separate UI from business logic, providing step‑by‑step code examples, including model, ViewModel, view, and a complete login page implementation.
UseCase objects, placed in the Domain layer of modern Android architecture, encapsulate complex business logic that was previously crammed into ViewModels, thereby enforcing clean separation of concerns, adhering to the Single Responsibility Principle, and making the codebase clearer, more maintainable, and scalable.
The article guides Android developers through evolving UI architectures—from MVC to MVI—showing how to transition Jetpack Compose projects from MVVM to MVI, tackle hybrid navigation and WebView integration, and apply refactoring, performance tuning, and best‑practice code examples.
The team evaluated cross‑platform options, piloted both Flutter and an H5 offline‑Hybrid approach, found Flutter’s self‑rendering engine delivered superior performance and consistency, and consequently adopted Flutter as the primary framework, dramatically improving development efficiency and UI parity across Android and iOS.
The article describes a modular iOS photo‑album solution that isolates the album as an independent, reusable SDK through a three‑layer architecture—interface, view‑customization, and logic management—implementing reading and change chains, handling iOS 14 privacy, iCloud assets, and multithreaded PhotoKit operations to reduce coupling and maintenance costs.
This tutorial walks through building a minimal MVP for the Linkworld iOS app by applying the MVVM pattern, creating a ViewModel, fetching JSON data with URLSession, and adding, editing, and deleting identity cards using SwiftUI state management and context menus.
The article dissects Bilibili’s live‑room architecture, showing how dozens of independent MVVM‑based Views act as business units, explains the coupling problems caused by improper LiveData and cross‑ViewModel references, outlines a service‑driven data‑flow and zone‑based lifecycle model, and proposes systematic refactoring to reduce technical debt and foster shared architectural ownership.
This article explains how to reduce UI complexity in Android by layering architecture, tracing the evolution from MVC through MVP and MVVM to MVI, and demonstrates a searchable interface built with Jetpack Navigation and Kotlin DSL, highlighting pitfalls of monolithic initView methods and proposing more reusable abstractions.
This article traces jQuery’s emergence as the de‑facto library that simplified DOM manipulation and cross‑browser compatibility during the Web 2.0 era, examines its widespread adoption and subsequent performance gains from removal, and explains why modern standards, HTML5 and MVVM frameworks have reduced its relevance today.
This article traces jQuery’s rise as the go‑to library during Web 2.0, examines recent moves by major sites to drop it, explains its original technical advantages, and analyzes how HTML5, MVVM frameworks and modern frontend stacks have reduced its relevance while it still powers a large share of the web.
GongSolutions.WPF.DragDrop is an open‑source .NET library that simplifies implementing drag‑and‑drop interactions in WPF applications, offering MVVM‑friendly APIs, multi‑selection, reordering, cross‑control data transfer, visual decorators, and extensive default settings, while supporting .NET Framework 4.6.2+, .NET Core 3.1, .NET 5/6 on Windows.
When observing LiveData in Android MVVM, developers may be misled by log deduplication, Java‑8 lambda optimizations that reuse a single Observer, automatic replay of the latest value to new observers, and shared ViewModel navigation bugs, but using an Event wrapper, reflection to reset version counters, or switching to Kotlin Flow/SharedFlow can safely avoid these pitfalls.
This article reviews classic Android architectural patterns—MVC, MVP, and MVVM—highlights their limitations, introduces the MVI pattern as a more streamlined alternative, and provides a detailed Kotlin implementation with ViewState, ViewEvent, and unidirectional data flow examples.
This article explains two Kotlin‑based network request wrappers for Android that reduce boilerplate by using LiveData, Retrofit, OkHttp and coroutines, compares their design trade‑offs, provides complete Activity, ViewModel, Repository and BaseRepository code samples, and shows how to handle loading, success, error and multiple data sources in a clean MVVM architecture.
This article explores software architecture concepts by drawing parallels with building design, explains the goals of architectural design such as scalability and maintainability, and demonstrates a practical Android MVVM implementation using WanAndroid with clean‑architecture patterns, Kotlin, and modular project structure.
This article explains how to integrate Retrofit with Kotlin coroutines following Google’s Android architecture guidelines, covering coroutine basics, OkHttp and Retrofit setup, generic response handling, repository abstraction, ViewModel usage, and lifecycle‑aware coroutine scopes to achieve clean, asynchronous network calls.
To tame the growing complexity of QQ Music’s Android playback page, the team replaced the monolithic MVC/SubController design with a clean, layered architecture that uses lightweight, lifecycle‑aware ViewDelegates and LiveData, enabling on‑demand module loading, clear separation of concerns, reduced memory usage, and reusable UI components.
This article provides a comprehensive guide to the MVC and MVVM architectural patterns for iOS, explaining their components, interactions, KVO usage, and includes complete Objective‑C code examples that demonstrate how to implement both patterns in a real‑world news‑list app.