# state-management Published articles for state-management. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Explicit Task State Enables Incremental Updates in Long Analysis Pipelines DevFeed: [Explicit Task State Enables Incremental Updates in Long Analysis Pipelines]() Original publisher: [Read original article]() Author: Avi Chawla Published: 2026-08-28T21:11:08Z Content type: article Language: en Sources: [Daily Dose of Data Science]() Topics: [Artificial Intelligence](), [Code](), [Open Source](), [Command-line interface](), [Text-based user interface](), [systems]() Tags: [ai](), [code](), [command-line](), [open-source](), [state](), [state-management](), [systems]() ### AI overview The article explains how explicit task state can make long analysis pipelines responsive to changing requirements. By tracking plans, completed steps, artifacts, dependencies, and exceptions outside the conversation, a system can preserve valid work and replan only affected downstream steps. It describes Apodex 1.1, Deep Discover, and the open-source FrontierAgent runtime as examples of this approach. ### Source excerpt Full guide with code. ## Angular Forms, Web AI, and Architecture Community Features DevFeed: [Angular Forms, Web AI, and Architecture Community Features]() Original publisher: [Read original article]() Author: Angular Published: 2026-08-14T13:01:03Z Content type: article Language: en Sources: [Angular]() Topics: [Angular](), [Forms](), [Artificial Intelligence](), [Web](), [reactive](), [Development](), [Tooling]() Tags: [ai](), [angular](), [angular-newsletter](), [angular-weekly](), [coding](), [forms](), [state](), [state-management](), [tooling](), [tutorials](), [web]() ### AI overview This Angular community roundup covers the evolution of form state management from template-driven approaches to the reactive Signal Forms API, client-side machine learning in browsers, Angular v21 architecture, pragmatic AI use, developer tooling, and coding challenges involving Signal Forms and form arrays. ### Source excerpt The Angular ecosystem continues to push forward with deeper AI integration and modern form architectures. This week, our community experts track the complete evolution of form handling, explore client-side AI, and dive into tactical discussions about developer craftsmanship in the age of AI. Catch up with these incredible community features! From Template-Driven to Signal-Driven Angular Forms Sonu Kapoor @SonuKapoor1978 charts the complete architectural evolution of forms in Angular. Learn how form state management has progressed from legacy template-driven approaches all the way to the highly reactive, modern Signal Forms API. Read the full article: https://www.codemag.com/Article/264041/From-Template-Driven-to-Signal-Driven-The-Complete-Evolution-of-Angular-Forms What's New in Web AI? Christian Liebel (@christianliebel) l breaks down the latest advancements in client-side machine learning. Discover how you can leverage powerful Web AI capabilities directly inside browser environments to build faster, privacy-focused web experiences. Watch the conference talk: https://www.youtube.com/watch?v=jFd8FomARsw The Dev Life Podcast: Angular v21 Architecture, Pragmatic AI, and Tooling Lessons Brooke Avery @JediBravery and Matthew Christiansen drop three stellar episodes of The Dev Life podcast covering architecture and real-world AI strategies. First, they host Sander Elias to map out v21 vision and velocity from an architect's lens. Next, legendary author Dave Thomas drops by to discuss developer craftsmanship as a "Pragmatic Agent." Finally, Alfredo Perez joins the show to share favorite tools and hard-earned lessons from using AI in the trenches. Listen to Ep. 11 (Modern Angular Architecture): https://www.youtube.com/watch?v=r0bKFy96UMM Listen to Ep. 13 (The Pragmatic Agent): https://www.youtube.com/watch?v=-rGMJdbH-yA Listen to Ep. 16 (AI in the Trenches): https://www.youtube.com/watch?v=bg38uSYpM8c Hands-On Code Challenges: Signal Forms and Form Arrays Ready to practic ## Where I'm Writing Now: The Complete 14-Part BlocSignal Series on DEV.to DevFeed: [Where I'm Writing Now: The Complete 14-Part BlocSignal Series on DEV.to]() Original publisher: [Read original article]() Author: Randal L. Schwartz Published: 2026-08-10T16:00:59Z Content type: opinion Language: en Sources: [Flutter Community - Medium]() Topics: [Flutter](), [Dart](), [reactive](), [Dependency injection](), [OpenTelemetry](), [Web Development]() Tags: [bloc](), [blocsignal](), [dart](), [dependency](), [dev](), [developer-community](), [development](), [flutter](), [series](), [signal](), [state-management](), [tracing](), [writing]() ### AI overview The author announces that DEV.to and the Google Developer Experts organization on DEV.to are now the primary publishing hubs for new technical writing. The article presents a 14-part BlocSignal series covering Dart and Flutter state management, architecture, interoperability, dependency injection, tracing, and web development. ### Source excerpt If you've been following my articles here on Medium over the years, thank you! I wanted to share a quick update on where I'm primarily publishing my new technical deep dives, architectural guides, and Flutter/Dart tutorials. Going forward, my primary writing hub is DEV.to (@randalschwartz) and the official Google Developer Experts (GDE) organization on DEV.to. DEV.to provides a vibrant developer community, native Dart syntax highlighting, and a built-in Series feature that links connected articles into structured, multi-part curricula. 🚀 The New Series: BlocSignal Architecture & Practice Over the last month, my team and I launched BlocSignal -- a production-grade state management framework for Dart and Flutter that bridges BLoC's enterprise discipline with Signals' 0ms synchronous reactivity. We've published a comprehensive 14-part series on DEV.to covering everything from core state machine philosophy and Riverpod/Provider interop to dependency injection, OpenTelemetry tracing, and Jaspr web development. Here is the complete roadmap of all 14 articles available to read right now on DEV.to: 🏛 1. Core Architecture & Philosophy Introducing BlocSignal: Unidirectional Data Flow Meets Reactive Signals The origin story: bridging BLoC semantics with Rody Davis's signals v7 primitives for 0ms microtask queue latency. BLoC meets Signals: How to Pitch BlocSignal to Your Dev Leads How to navigate technical team reviews and explain the enterprise value of synchronous signal graphs. How We Achieved Full BLoC API & Protocol Parity in BlocSignal 0.2.0 A deep dive into BlocProvider, BlocBuilder, BlocListener, BlocConsumer, and context.select parity. Beyond ProviderNotFound: How BlocSignal Rethinks State Location and Synchronous Propagation Solving scope lookups and understanding why synchronous signal updates prevent frame tearing. From Raw Signals to BlocSignal: Taming Reactivity for Enterprise Scale How encapsulating signals inside Cubit/Bloc containers stops global signal "spagh ## Why "state management" is a misleading term in React DevFeed: [Why "state management" is a misleading term in React]() Original publisher: [Read original article]() Author: Alex Russell Published: 2026-07-23T00:00:00Z Content type: opinion Language: en Sources: [Alex Russell]() Topics: [React](), [JavaScript](), [GraphQL]() Tags: [alternatives](), [frameworkism](), [javascript](), [library](), [react](), [redux](), [state-management](), [webdev]() ### AI overview This opinion article argues that "state management" is an imprecise label for React and the surrounding ecosystem. It surveys libraries including Redux, Zustand, Apollo, and others, and contends that they primarily encapsulate state or propagate notifications about state changes rather than manage state themselves. ### Source excerpt It is by no means the gravest linguistic crime of the React epoch,1 but "state management" grates like nails on chalkboard. A Socratic dialogue I keep having about it goes something like this: me: This UI is far too heavyweight for what it does, have you considered not using React? them: But how will we do state management without React? me: What do you mean? are reactive. them: React manages state in our app. me: It does? Then what are for? them: Oh, those manage state. me: The libraries that trigger this "Who's on First?" routine include: MobX, which promises "simple, scalable state management." Satchel, apparently, "is characterized by exposing an observable state that makes view updates painless and efficient" Recoil, billed as "a state management library for React" Jotai, which pledges "primitive and flexible state management for React" XState, a "state management and orchestration solution for JavaScript and TypeScript apps" Apollo, promising "a comprehensive GraphQL state management library for JavaScript" Redux, tagline: "a predictable state container for JavaScript apps." TanStack Store, "a framework-agnostic state primitive for immutable updates" Zustand, described as the "🐻 bear necessities for state management in React" Contrasts sharp enough to cut softened butter.2 Suffice it to say, the ecosystem has not picked a winner. Indeed, I regularly see several of these libraries on a single page. But even one would seem too many, given that we're adding a second "state management" system to a framework that spills considerable documentation ink chest-beating about its state management facilities. One of the following must be true: React is a state management system and someone has smuggled in a duplicative dependency we can jettison. React is an inadequate state management system and we should stop trusting it with an ill-defined subset of the "state management" problem. React is not a state management system and we should s ## Building a Testable Network Layer and Three-Tier State Management in Flutter DevFeed: [Building a Testable Network Layer and Three-Tier State Management in Flutter]() Original publisher: [Read original article]() Author: Veli Bacık Published: 2026-07-08T15:56:52Z Content type: tutorial Language: en Sources: [Flutter Community - Medium]() Topics: [Flutter](), [Network](), [API](), [HTTP](), [Refactoring](), [Error Handling](), [JSON](), [ui](), [App]() Tags: [api](), [backend](), [building](), [code](), [dart](), [error-handling](), [flutter](), [how-to](), [http](), [implementation](), [integration](), [json](), [masterclass](), [network](), [refactoring](), [server](), [state-management]() ### AI overview This tutorial explains how to refactor a Flutter application's network and state-management architecture. It introduces a generic, testable network manager and service/model layers, then applies a three-tier state model using Cubit for business state, BlocSelector for targeted rebuilds, and ValueNotifier for widget-local UI state. ### Source excerpt How to wrap HTTP behind a generic, testable network manager with sealed results -- then drive your screens with a three-tier state model: global Cubit, page Cubit, and widget-local ValueNotifier. Flutter Refactoring Masterclass -- Part 3 GitHub - VB10/flight_booking: Flight App for refactoring real project PRs: #11, #12 📺 Video Series: Network & Service Layer https://medium.com/media/2d40d555e4d8968f1d15fb35e2e91553/hrefhttps://medium.com/media/3d8a8a32a77c98177ba10492a892aed6/href 🤖 Want to apply these changes to your project? See the AI prompt at the end. The Problem In Part 2 we split the login page into View, ViewModel, and Mixin -- but the ViewModel still new'd up a Dio() instance and hard-coded http://localhost:8080 inline. Every screen that talked to the backend did the same thing: create a fresh Dio, paste the base URL, decode JSON by hand, and copy-paste the same if (statusCode == 200) ... else ... catch (e) ladder. That pattern rots fast. A URL change means a project-wide search. A new header (auth token, API version) has to be added everywhere. Error handling drifts -- one screen returns 'Server hatası', another swallows the exception. And nothing is testable, because the network call is welded to the widget. As the video puts it: the person writing the code shouldn't be able to say "this only works with internet" -- the network is a dependency, and dependencies must be managed. There's a second rot: state. setState rebuilds the whole widget on every field change. A page with a loading flag, an error string, and a list re-renders all three even when only one changed. And there's no consistent home for "where does the loading state live" -- sometimes a ValueNotifier, sometimes a bool, sometimes buried in _PageState. This article fixes both on the same module. PR #11 builds a generic network + service + model layer. PR #12 layers a three-tier state model on top -- Cubit for business, BlocSelector for surgical rebuilds, ValueNotifier for widget-local UI. What We Change ## Choose Your Edit Prediction Provider DevFeed: [Choose Your Edit Prediction Provider]() Original publisher: [Read original article]() Author: Max Brunsfeld Published: 2026-02-04T00:00:00Z Content type: release Language: en Sources: [Zed Industries - Blog]() Topics: [Code](), [Ollama](), [Mercury](), [GitHub Copilot](), [API]() Tags: [build](), [code](), [github-copilot](), [inference](), [integration](), [ollama](), [state-management]() ### AI overview Zed introduces support for multiple edit prediction providers, including Zeta, Mercury Coder, Sweep, Ollama, Codestral, and GitHub Copilot's Next Edit Suggestions. A new pluggable provider architecture centralizes core functionality while simplifying provider-specific integrations. ### Source excerpt Zed now supports multiple edit prediction providers: Zeta, Mercury Coder, Sweep, Ollama, and GitHub Copilot Next-Edit. ## From prototype to production-ready agentic AI solution: A use case from Grid Dynamics DevFeed: [From prototype to production-ready agentic AI solution: A use case from Grid Dynamics]() Original publisher: [Read original article]() Author: Eugene Steinberg Published: 2025-09-29T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [AI Agent](), [Artificial Intelligence](), [Langgraph](), [Error Handling](), [retry](), [Redis]() Tags: [ai](), [case-study](), [community](), [error-handling](), [langgraph](), [production](), [redis](), [retry](), [state-management]() ### AI overview A Grid Dynamics case study describes building a deep research agent for a Fortune 500 manufacturer. The team used LangGraph initially, then migrated to Temporal after encountering challenges with error handling, retries, state management, caching, scaling, custom workflows, and human-in-the-loop interactions. ### Source excerpt What happens when a promising AI agent prototype hits the high stakes of a prod environment? Grid Dynamics found out the hard way. ## Case Study: Modernizing a High-Traffic Streaming Platform with the AHA Stack (HTMX & Alpine.js) DevFeed: [Case Study: Modernizing a High-Traffic Streaming Platform with the AHA Stack (HTMX & Alpine.js)]() Original publisher: [Read original article]() Author: Daniel Bencz Published: 2025-08-29T17:02:07Z Content type: article Language: en Sources: [RisingStack]() Topics: [htmx](), [Web Development](), [Streaming](), [JavaScript](), [Back end](), [Flask]() Tags: [case-study](), [flask](), [htmx](), [js](), [maintainability](), [state-management](), [streaming](), [ux](), [web]() ### AI overview This case study describes modernizing a high-traffic streaming website for responsiveness, maintainability, business continuity, and easier developer onboarding. The existing Python Flask and Jinja site used jQuery; the team retained server-rendered architecture and adopted HTMX with Alpine.js instead of introducing a single-page application. ### Source excerpt Our client, a leading company in the streaming industry, acquired a highly successful indie website with over 50 million unique visitors per month. The site had been built by a single developer who prioritized functionality over maintainability. While the features were mostly bug-free, the design was outdated, and the code relied on aging technologies. The [...] The post Case Study: Modernizing a High-Traffic Streaming Platform with the AHA Stack (HTMX & Alpine.js) appeared first on RisingStack Engineering. ## Migrating to Angular Signals DevFeed: [Migrating to Angular Signals]() Original publisher: [Read original article]() Author: Armen Vardanyan Published: 2025-08-27T10:43:56Z Content type: tutorial Language: en Sources: [Daniel Glejzner]() Topics: [Angular](), [reactive]() Tags: [angular](), [articles](), [optional](), [reactive](), [rxjs](), [state](), [state-management]() ### AI overview This tutorial examines migrating Angular applications to Signals for state management and reactivity. It explains that RxJS is expected to become optional rather than unsupported, while Signals can handle many tasks. ### Source excerpt Today, everyone, everywhere in the Angular community is talking about Signals. They are the new way to manage state and reactivity in Angular applications, promising a better way to build logic and a very much improved change detection. However, many are hesitant. And this is understandable! Not only are signals ## Build resilient Agentic AI with Temporal DevFeed: [Build resilient Agentic AI with Temporal]() Original publisher: [Read original article]() Author: Tim Imkin Published: 2025-02-25T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Artificial Intelligence](), [Orchestration](), [reliability](), [Scalability](), [retry](), [real-time](), [Processes](), [SDK](), [context]() Tags: [agentic-ai](), [agents](), [ai-agents](), [continuous](), [durability](), [metrics](), [orchestration](), [state-management](), [temporal-concepts]() ### AI overview This tutorial explains how Temporal supports durable, scalable Agentic AI workflows that can preserve state, involve humans, schedule execution, provide observability, and recover from failures through retries. ### Source excerpt Learn how Temporal powers durable, scalable Agentic AI workflows with reliable state management, human-in-the-loop, and seamless orchestration. ## Multi-agent Workflow patterns and modern use cases | Temporal DevFeed: [Multi-agent Workflow patterns and modern use cases | Temporal]() Original publisher: [Read original article]() Author: Clair Byrd Published: 2024-12-03T08:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Orchestration](), [AI Development](), [real-time]() Tags: [agent](), [autonomous-agents](), [how-to](), [multi-agent](), [orchestration](), [real-time](), [state-management](), [workflow]() ### AI overview This article explains multi-agent workflows as coordinated processes involving multiple autonomous agents. It describes their characteristics, including decentralization, communication, autonomy, interdependency, and state management, and explains how Temporal supports them through orchestration and workflow state management. ### Source excerpt Learn how Temporal powers multi-agent workflows with orchestration, state management, and real-time communication, without custom code. ## Update State Management with Pinia DevFeed: [Update State Management with Pinia]() Original publisher: [Read original article]() Author: Dusko Peric Published: 2024-03-21T14:43:21Z Content type: article Language: en Sources: [Homegate Engineering Blog - Medium]() Topics: [Vue.js](), [Development](), [web applications](), [Code]() Tags: [article](), [debugging](), [developer-experience](), [development](), [pinia](), [state-management](), [typescript](), [vue-js](), [vuejs](), [web-applications]() ### AI overview This article explains Pinia as a state-management option for Vue.js applications. It describes Pinia's component-like store structure, direct state updates within actions instead of mutations, modular stores, Option and Setup Stores, TypeScript support, Vue Devtools support, and its lightweight design. ### Source excerpt In the development and maintenance of web applications, one of the crucial factors is the proper choice of state management. When it comes to Vue.js, we have two players in the game, where in my opinion, we have a clear winner. In this article, I will go through the functionalities brought by Pinia, which represent a step forward in this field. Intuitive API One of the problems in working with state is that it can very easily become confusing and complex. With its component-like structure, Pinia allows for easier understanding of how the store functions and interacts with your application. Let's look at an example to compare a Vue component with a Pinia store. Syntax similarity between Vue component and Pinia store This familiar syntax makes it a user-friendly and efficient solution for managing state. Excluding Mutations One of the key differences between Pinia and Vuex lies in the absence of mutations. In Vuex, the distinction between actions and mutations can become less clear-cut, particularly for complex stores. This redundancy can lead to repetitive code, adding unnecessary complexity to state management. Pinia takes a more direct approach. You can simply modify the state directly within actions. Let's see a code example to illustrate this concept: Vuex Store import { createStore } from 'vuex'; export default createStore({ state: { count: 0, }, mutations: { increment(state) { state.count++; // Update state through mutation }, }, actions: { increment({ commit }) { commit('increment'); // Dispatch mutation to update state }, }, }); Pinia Store import { defineStore } from 'pinia'; export const useCounterStore = defineStore('counter', { state: () => ({ count: 0, }), actions: { increment() { this.count++; // Directly update state within action }, }, }); In essence, Pinia removes an unnecessary layer of complexity by allowing direct state updates within actions. Modular stores design Pinia allow you to create multiple stores for different parts of your application, ## Crash course on the Android UI layer | Part 1 DevFeed: [Crash course on the Android UI layer | Part 1]() Original publisher: [Read original article]() Author: Manuel Vivo Published: 2023-12-13T17:03:40Z Content type: tutorial Language: en Sources: [Bumble Tech]() Topics: [ui](), [Android](), [business logic](), [App]() Tags: [android](), [app-architecture](), [architecture](), [best-practices](), [business-logic](), [state-management](), [ui](), [viewmodel]() ### AI overview Part 1 of a series explains the Android UI layer, UI state, and the roles of the UI, data, and optional domain layers. It introduces separation of concerns, state holders, unidirectional data flow, and related best practices. ### Source excerpt Crash Course on the Android UI Layer | Part 1The UI and UI State This blog post series aims to summarise the Android Developer guidance on the UI layer. We'll explore all the entities involved in it, understand the role each part plays, and discuss best practices. By the end of this series, you will have a general understanding of what happens on the UI layer and how to best handle state and logic within it, the various APIs involved, and how to use them. Additionally, we'll provide decision trees to assist you when you're in doubt. This is part 1, where we're covering the UI and the UI state. Part 2 covers state holders and other UI layer-related topics such as where to hoist state and save state on Android. If you prefer to consume this content in video format, check out the talk I delivered at Droidcon London 2023: Peeling Back the Layers: Unmasking the UI-nknown! The UI layer in the grand scheme of things The UI layer isn't the only layer you can find in a typical app architecture. Alongside it, you can also find the data layer and sometimes, the domain layer. According to the Android Architecture documentation: The UI layer displays data on the screen. The data layer exposes application data and contains the vast majority of the business logic of the app. The domain layer is an optional layer that aims to 1) simplify and 2) reuse the potential business logic complexity of the UI layer. No less, no more. Note: The business logic is what gives value to your application. It's the implementation of product requirements that determines how your app fetches, stores, and modifies data.Architecture layers in a typical Android app: The UI, data, and domain layersEntities in the UI layer The UI layer consists of three distinct entities with clearly defined responsibilities. This distinction helps with separation of concerns, enhances testability, and promotes reusability. The UI, or UI elements, render data on the screen. The UI state describes the data to render on the ## Managing State in Vue Applications: The Composable Provider Pattern DevFeed: [Managing State in Vue Applications: The Composable Provider Pattern]() Original publisher: [Read original article]() Author: Doximity Published: 2023-07-21T07:23:00Z Content type: article Language: en Sources: [Doximity]() Topics: [Vue.js](), [Front end](), [Scalability](), [Nuxt.js]() Tags: [code-modularity](), [components](), [maintainability](), [modularity](), [reusable-code](), [reuse](), [scalability](), [state-management](), [vue]() ### AI overview This article explains the Composable Provider pattern for state management in Vue applications. The approach combines the Vue Composition API with the Provide/Inject APIs to manage complex, feature-driven state, with benefits including scalability, maintainability, reusability, and reduced code duplication. ### Source excerpt State management is a fundamental concept of front-end application design, and a critical aspect in building robust Vue applications. As Vue applications grow in complexity, managing state becomes an increasingly challenging task, especially when working with a large organization of engineers spread across various product teams. Fortunately, the Vue and Nuxt ecosystem provides a variety of state management solutions, each with its own trade-offs. In this blog post we will explore the Composable Provider pattern, which handles state management by combining the Vue Composition and Provide/Inject APIs, and why its clean and simple implementation is a powerful approach to handling complex, feature-driven state in modern Vue applications. Note: This article was originally intended as a reference for our internal engineering team, but given its potential general use among Vue application developers we are publishing it here. We hope you'll find this pattern helpful when designing your Vue application's state as we have here at Doximity! Why Efficient State Management Matters Efficient state management plays a crucial role in the development of Vue applications. As applications grow in complexity, the ways in which we manage and handle changes to state become increasingly important. Here are a few key reasons why managing state efficiently matters: Scalability: As Vue applications and the teams building them grow in size, the complexity and size of their state grow also. Efficient state management allows for better scalability by providing a structured and organized approach to handling state. It becomes easier to add new features, maintain existing functionality, and reason about the flow of data within the application. Code Maintainability: Well-managed state reduces code complexity and promotes code maintainability. When state is not encapsulated properly, it becomes challenging to understand and modify the application's behavior. By implementing sound state management ## Building a Note-Taking App in Compose DevFeed: [Building a Note-Taking App in Compose]() Original publisher: [Read original article]() Author: Doximity Published: 2023-07-05T19:47:00Z Content type: tutorial Language: en Sources: [Doximity]() Topics: [Jetpack Compose](), [App](), [Code](), [Template]() Tags: [app](), [architecture](), [build](), [building](), [class](), [clean-architecture](), [code](), [collect](), [compose](), [data-class](), [di](), [extension-function](), [flow](), [icons](), [implement](), [koin](), [list](), [state](), [state-management](), [view]() ### AI overview A case study showing how to build a note-taking app with Jetpack Compose. It models note state, renders the notes UI, collects note data through a presenter and Clean Architecture use cases, and plans events for adding, editing, checking, and deleting notes. ### Source excerpt In this case study, we will build a note-taking app that lets the user add, edit and delete notes. It uses Compose for both the view and presentation layers! Note: This is a follow up to Part 1: Simplifying State Management with Compose and assumes the reader is already familiar with Jetpack Compose. The Template I find it useful to start with the model that represents the state of the screen we're building. It will have a list of notes, with each note containing properties for the text and checkbox: data class NotesUiModel(val notes: List) : UiModel { data class Note(val text: String, val isChecked: Boolean) : UiModel } It'll be the job of the presenter to produce this model. Initially, let's implement a stub to return an empty list of notes (we'll ignore parameters for now): class NotesListPresenter : Presenter { @Composable override fun present(params: Unit): NotesUiModel { return NotesUiModel(notes = emptyList()) } } Then we can build our view to render the model that's returned by the presenter: @Composable fun NotesScreen() { val presenter: NotesListPresenter = koinInject() // we use koin for DI val uiModel = presenter.present(Unit) Column { TopAppBar(title = { Text("Notes") }) Notes(uiModel) } } } The View The views themselves are pretty self-explanatory if you're already familiar with building UIs in Compose. For the notes, we'll take in a NotesUiModel argument and create a LazyColumn with the notes property. A FAB button is used for adding new notes, although we'll skip the triggering of events and return to this part in a little bit: @Composable private fun Notes(uiModel: NotesUiModel) { Box { LazyColumn { items(uiModel.notes) { note -> Note(note) } } FloatingActionButton(onClick = { /* TODO */ }) { Icon(imageVector = Icons.Rounded.Add) } } } Then we can render each note with a checkbox, text field and delete button: @Composable private fun Note(uiModel: Note) { Row { Checkbox( checked = uiModel.isChecked, onCheckedChange = { /* T ## Simplifying State Management with Compose DevFeed: [Simplifying State Management with Compose]() Original publisher: [Read original article]() Author: Doximity Published: 2023-07-05T19:45:00Z Content type: tutorial Language: en Sources: [Doximity]() Topics: [Jetpack Compose](), [Android](), [ui](), [Development](), [interoperability]() Tags: [android](), [architecture](), [clean-architecture](), [compose](), [compose-ui](), [interoperability](), [state](), [state-management](), [xml]() ### AI overview This tutorial explains how Doximity's Android team experimented with using the Compose Runtime instead of ViewModels to manage screen state in the refreshed Amion physician scheduling tool. It describes the related presentation-layer and clean-architecture patterns, including interoperability with existing XML and Compose UI, and introduces foundations for a follow-up note-taking app. ### Source excerpt The recent release of Doximity's refreshed physician scheduling tool Amion involved a significant overhaul of the user interface (UI) layer using Jetpack Compose. As part of the development process, we decided to experiment with shifting from ViewModels to utilizing the Compose Runtime for managing screen state. This article explores the motivations behind this approach and demonstrates an overall improvement to the view layer and presentation logic using the patterns developed in Amion 6.0.0. Note: This is part one of a two-part article. In part two, we will build a note-taking app using the foundations covered here. Understanding the Presentation Layer The Android team at Doximity builds apps following the basic principles of clean architecture, which involves separating the app into layers, each with their own responsibilities. In our app, we have a view layer, responsible for rendering UI components (Compose UI, XML views, etc.), and a presentation logic layer, responsible for producing screen state. Every navigable point in the app corresponds to one or more UI components and is associated with one or more screen state producers. Inspiration and Initial Experiments The decision to leverage Compose for managing state was inspired by (at the risk of sounding like r/mAndroidDev) Jake Wharton's article The State of Managing State (with Compose). While the release of Circuit occurred midway through our development, it was deemed more of a framework that required significant buy-in, whereas we aimed to build a flexible pattern with smoother interoperability with our existing architecture, that at the time mostly utilized ViewModel with XML and Compose UI. When we think about the presentation layer in Android as developers, we have to think about: What is the state of the screen? That is, not just when the user first sees it, but what does it look like when it's loading, what happens when there is an error, how will the state of components of the screen interact, and ## Simplifying Redux in Kotlin: "mutating" immutable states with Mutekt DevFeed: [Simplifying Redux in Kotlin: "mutating" immutable states with Mutekt]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2023-03-24T13:00:39Z Content type: tutorial Language: en Sources: [Shreyas Patil's Blog]() Topics: [Kotlin](), [Redux](), [Development](), [Front end](), [multiplatform]() Tags: [android](), [developers](), [javascript](), [kotlin](), [kotlin-multiplatform](), [multiplatform](), [redux](), [state-management](), [ui]() ### AI overview This tutorial introduces Mutekt, a multiplatform Kotlin utility for simplifying immutable state updates with mutating syntax in Redux-like architectures. It begins by explaining common approaches to managing and updating Kotlin state models, including copying previous state and combining multiple states. ### Source excerpt Simplify state management in Kotlin with Mutekt. Learn how to write 'mutating' syntax for immutable states in Redux-like architectures. ## Leveraging the Snapshot Mutation Policies of Jetpack Compose DevFeed: [Leveraging the Snapshot Mutation Policies of Jetpack Compose]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2023-01-30T13:30:39Z Content type: tutorial Language: en Sources: [Shreyas Patil's Blog]() Topics: [Jetpack Compose](), [Compose](), [ui](), [Code]() Tags: [android](), [android-app-development](), [compose](), [data-class](), [jetpack-compose](), [kotlin](), [library](), [mutation](), [recompose](), [recomposition](), [standard-library](), [state](), [state-management](), [ui]() ### AI overview A tutorial on SnapshotMutationPolicy in Jetpack Compose, explaining how structural, referential, and never-equal policies determine whether state changes trigger UI recomposition. ### Source excerpt Understand Snapshot Mutation Policies in Jetpack Compose. Learn how to control when and how your UI recomposes based on state changes. ## Rethinking React components with @defer DevFeed: [Rethinking React components with @defer]() Original publisher: [Read original article]() Author: Michael Watson Published: 2023-01-17T15:29:47Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [GraphOS](), [Single-page application (SPA)](), [React](), [schema design]() Tags: [announcement](), [component](), [graphos](), [graphql](), [react](), [schema-design](), [state-management]() ### AI overview This article explains how GraphQL's @defer directive can split a query response into multiple parts, allowing faster initial responses while slower fields load later. It announces full supergraph support for @defer in GraphOS and describes using a supergraph router with an existing GraphQL API. ### Source excerpt Since the rise of the frontend framework and the framework wars of the 2010s, we've all gotten pretty used to the idea of building single-page apps that load a JavaScript bundle and then send queries to a server dynamically as a user clicks around. The move to single-page apps was driven by the need to create faster, more interactive user experiences. As with every great innovation, solving one problem just opens your eyes to the next one. ## ViewModel: for UI business, not UI operations 😮 DevFeed: [ViewModel: for UI business, not UI operations 😮]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2022-12-19T12:30:42Z Content type: opinion Language: en Sources: [Shreyas Patil's Blog]() Topics: [Android](), [ui](), [reactive](), [App]() Tags: [android](), [android-app-development](), [apis](), [applications](), [architecture](), [business-logic](), [kotlin](), [mvi](), [mvvm](), [reactive](), [state-management](), [ui](), [ux]() ### AI overview An opinionated Android development article explains that ViewModels should hold UI state and execute business logic for the UI, while avoiding responsibility for UI operations. It uses toast and bottom-sheet interaction examples to illustrate keeping UI concerns loosely coupled from ViewModels. ### Source excerpt Stop misusing ViewModels! Learn why ViewModels should handle UI business logic, not UI operations like showing toasts or navigation. ## Flutter Authorization with RLS DevFeed: [Flutter Authorization with RLS]() Original publisher: [Read original article]() Author: Tyler Shukert Published: 2022-11-22T07:00:00Z Content type: tutorial Language: en Sources: [Supabase Blog]() Topics: [Authorization](), [Flutter](), [Supabase](), [Security](), [PostgreSQL](), [cross-platform](), [real-time](), [Database](), [Code]() Tags: [app](), [authorization](), [backend](), [chat](), [code](), [cross-platform](), [database](), [flutter](), [password](), [postgresql](), [real-time](), [schema](), [security](), [state-management](), [tutorial]() ### AI overview This tutorial explains how to secure a Flutter chat application with Supabase Row Level Security (RLS). It covers authorization, one-to-one chat rooms, state management with flutter_bloc, and updates to the database schema. ### Source excerpt Learn how you can secure your Flutter app using Supabase Row Level Security. ## Using Atomic-Like State Management to Simplify Microservices DevFeed: [Using Atomic-Like State Management to Simplify Microservices]() Original publisher: [Read original article]() Author: Samar Abbas Published: 2022-11-09T19:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Microservices](), [distributed-systems](), [Architecture & Design](), [code productivity]() Tags: [architectures](), [boost-developer-productivity](), [distributed-systems](), [how-to](), [microservices](), [state-management]() ### AI overview The article discusses the operational and state-management challenges of microservices and argues that a dedicated state management platform can provide atomic-like abstractions, allowing developers to focus more on business logic. ### Source excerpt Discover how a dedicated microservices state management platform simplifies distributed systems with atomic-like abstractions to boost developer productivity. ## Effective Kotlin Item 1: Limit mutability DevFeed: [Effective Kotlin Item 1: Limit mutability]() Original publisher: [Read original article]() Published: 2022-09-28T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [Code](), [test]() Tags: [debug](), [kotlin](), [state-management](), [synchronization](), [test](), [workshop-learning-programming]() ### AI overview This Kotlin article explains why limiting mutability makes programs easier to understand, reason about, debug, synchronize, and test. It describes how mutable state can create dependencies, unintended side effects, additional possible states, and notification requirements when values change. ### Source excerpt Why it is so important to limit mutability, and how Kotlin supports it. ## Combining StateFlows and transforming it into a StateFlow DevFeed: [Combining StateFlows and transforming it into a StateFlow]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2022-06-24T12:30:00Z Content type: tutorial Language: en Sources: [Shreyas Patil's Blog]() Topics: [Kotlin]() Tags: [android](), [coroutine](), [coroutines](), [kotlin](), [multithreading](), [state-management](), [stateflow]() ### AI overview A Kotlin tutorial about combining multiple StateFlows into a derived StateFlow. It explains limitations of existing Flow-combining approaches, including conversion requirements such as a scope and separately calculated initial state. ### Source excerpt Master the art of combining multiple StateFlows into a single transformed StateFlow. Explore utilities and best practices for managing complex states in Kotlin. [Next page]()