# business logic Published articles for business logic. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Enterprises are sweating legacy IT assets as AI investment grows DevFeed: [Enterprises are sweating legacy IT assets as AI investment grows]() Original publisher: [Read original article]() Author: Dan Robinson Published: 2026-09-16T16:15:00Z Content type: article Language: en Sources: [www.theregister.com - Articles]() Topics: [legacy](), [Hardware](), [mainframes](), [data](), [business logic](), [Artificial Intelligence]() Tags: [ai](), [artificial-intelligence](), [business-logic](), [data](), [ensono](), [hardware](), [it-modernization](), [legacy](), [legacy-systems](), [mainframes](), [systems]() ### AI overview The article examines how enterprises are dealing with legacy IT assets as AI investment grows. It reports that mainframes and other hardware may contain the data and business logic needed to build AI services. ### Source excerpt Hardware such as mainframes found to hold the data and business logic needed to build those AI services ## Our Transition to React Native DevFeed: [Our Transition to React Native]() Original publisher: [Read original article]() Author: Khan Academy Published: 2020-07-09T22:00:00Z Content type: opinion Language: en Sources: [Khan Academy]() Topics: [React Native](), [Android](), [iOS](), [Mobile](), [React]() Tags: [android](), [android-apps](), [architectures](), [backend](), [bridge](), [business-logic](), [change](), [code](), [engineering](), [ios](), [mobile](), [news](), [react-native]() ### AI overview Khan Academy describes completing its transition to React Native for its iOS and Android apps. The article explains why the team moved away from separate platform codebases and outlines the transition's exploration, straddling, and extinction phases. ### Source excerpt In 2017, Khan Academy started using React Native in our iOS and Android apps. As of this year, we've reached a big milestone: our transition to React Native is complete! Every screen in the app is rendered in React Native. ## Code Smell 321 - Getter Piggybacking DevFeed: [Code Smell 321 - Getter Piggybacking]() Original publisher: [Read original article]() Author: Maxi Contieri Published: 2026-08-20T02:51:49Z Content type: article Language: en Sources: [Maximiliano Contieri - Software Design]() Topics: [Refactoring](), [Code]() Tags: [business-logic](), [class](), [code](), [refactoring]() ### AI overview This article explains a code smell in which an existing getter is reused to implement business logic outside the object that owns the value. It describes the resulting duplicated rules, broken encapsulation, scattered comparisons, and fragile refactoring, and recommends adding behavior methods, keeping comparisons inside the object, passing collaborators instead of primitives, and using getters mainly for rendering. ### Source excerpt TL;DR: Don't reuse an existing getter to bolt on new business logic from outside the object. Problems 😔 Duplicated business rules Broken encapsulation Scattered comparison logic Hidden domain kn ## Test & Set DevFeed: [Test & Set]() Original publisher: [Read original article]() Author: Jesse Wilson Published: 2026-07-13T22:22:27Z Content type: tutorial Language: en Sources: [Public Object]() Topics: [Concurrency](), [Concurrent Programming](), [Code](), [function](), [business logic]() Tags: [business-logic](), [code](), [concurrency](), [flaky-tests](), [function](), [programming](), [tests](), [threads]() ### AI overview An article about managing concurrency in threaded programs. It discusses the limits of simple and stress tests, describes a trusted concurrency pattern, and presents a helper function that separates business logic from concurrency logic while retrying after a lost race. ### Source excerpt Working with threads always feels hazardous to me. Non-determinism limits how much we can exercise with simple tests. Stress tests can shake out some bugs, but they're slow and potentially flaky. I don't like flaky tests. So I have a few concurrency patterns that I trust, and I ## Your Architecture Doesn't Rot Overnight DevFeed: [Your Architecture Doesn't Rot Overnight]() Original publisher: [Read original article]() Author: Valentina Jemuović Published: 2026-07-07T06:00:37Z Content type: opinion Language: en Sources: [Optivem Journal]() Topics: [legacy](), [systems](), [Software](), [Test-driven development]() Tags: [architecture](), [business-logic](), [code](), [dependency](), [legacy](), [refactor](), [requirements]() ### AI overview The article explains how repeated convenience-driven decisions gradually weaken boundaries between business logic and infrastructure. It argues that architectural decay often remains hidden while the application works and tests pass, eventually making seemingly simple changes difficult to locate and implement. ### Source excerpt As deadlines become tighter, convenience starts winning. ## AI RPG Migration Can Compile and Still Break Business Logic DevFeed: [AI RPG Migration Can Compile and Still Break Business Logic]() Original publisher: [Read original article]() Author: Federico Tomassetti Published: 2026-06-30T08:00:00Z Content type: opinion Language: en Sources: [Federico Tomassetti]() Topics: [migration](), [AI-assisted coding](), [Benchmark](), [Code]() Tags: [ai](), [benchmarks](), [business-logic](), [compilation](), [legacy-modernization](), [migration](), [rpg](), [tests]() ### AI overview The article argues that AI-assisted RPG migration tools should be evaluated on behavioral equivalence, not only compilation and generated test-pass rates. It cites the AgentModernize study, where the best reported result reached 19.4% behavioral equivalence, and describes gaps between extracting business rules and implementing them faithfully. ### Source excerpt AI-assisted RPG migration tools report high compilation success rates while silently failing on behavioral equivalence -- packed decimal truncation, activation group persistence, and cycle logic. The benchmarks show why, and what a real accuracy test looks like. The post AI RPG Migration Can Compile and Still Break Business Logic appeared first on Federico Tomassetti. ## A Practical CQRS Split for Read and Write Paths in a Node.js Service DevFeed: [A Practical CQRS Split for Read and Write Paths in a Node.js Service]() Original publisher: [Read original article]() Author: The T-Shaped Dev Published: 2026-06-21T12:19:52Z Content type: tutorial Language: en Sources: [The T-Shaped Dev]() Topics: [backends](), [Code]() Tags: [architecture](), [business-logic]() ### AI overview This tutorial presents a lightweight CQRS approach for a Node.js service: separate business-heavy write operations from read operations that serve screens, without requiring event sourcing or a second database. ### Source excerpt You don't need event sourcing or a second database. Just split reads from writes, and finally fix the 20-method service nobody wants to open. ## How Monk migrated 100+ workflows from Inngest to Temporal DevFeed: [How Monk migrated 100+ workflows from Inngest to Temporal]() Original publisher: [Read original article]() Author: Francesco Coacci Published: 2026-06-16T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [migration](), [Orchestration](), [business logic](), [test-coverage]() Tags: [async](), [automation](), [business-logic](), [community](), [coverage](), [migration](), [orchestration](), [pull-request](), [workflows]() ### AI overview Monk describes migrating more than 100 live workflows from Inngest to Temporal incrementally, using reversible pull requests, parallel runtimes, feature-flagged cutovers, and no migration freeze. The article explains how this approach kept each workflow coherent and recoverable during the transition. ### Source excerpt Monk migrated 100+ live workflows from Inngest to Temporal with one reversible PR at a time all while avoiding freezes and rewrites. Here's how. ## Track customer loyalty points with durable workflows DevFeed: [Track customer loyalty points with durable workflows]() Original publisher: [Read original article]() Author: Cecil Phillip Published: 2026-06-03T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [account](), [business logic](), [Database](), [real-time](), [locking](), [retry](), [service](), [upgrade](), [Mobile]() Tags: [account](), [business-logic](), [customer](), [database](), [locking](), [loyalty](), [loyalty-points](), [mobile](), [process](), [query](), [real-time](), [retry](), [service](), [temporal](), [temporal-concepts](), [upgrades](), [workflows]() ### AI overview This article explains how to track customer loyalty points with durable Entity Workflows in Temporal. Each customer has a persistent workflow that maintains points, tier status, and activity history, while Signals handle accruals, Updates validate redemptions, and Queries read current balances. ### Source excerpt Track loyalty points with durable Entity Workflows in Temporal. See how to handle accruals, tier upgrades, and redemptions for each customer. ## How Agentic AI Can Bypass the Application Layer's Database Protections DevFeed: [How Agentic AI Can Bypass the Application Layer's Database Protections]() Original publisher: [Read original article]() Author: flashdba Published: 2026-05-11T11:06:56Z Content type: opinion Language: en Sources: [flashdba]() Topics: [Architecture & Design](), [Artificial Intelligence](), [Database]() Tags: [agentic](), [agentic-ai](), [ai](), [ai-agents](), [architecture](), [business-logic](), [cloud](), [database](), [databases](), [databases-and-agentic-ai](), [inferencing](), [performance](), [rate-limiting]() ### AI overview The article argues that application layers unintentionally protect databases through query abstraction, input validation, rate limiting, and human-oriented traffic patterns. Direct database access by agent frameworks can bypass these protections, allowing unconstrained queries and exposing the database to unfamiliar load and access patterns. ### Source excerpt The application layer was never designed as a database security boundary - but it acted as one. Agentic AI removes that protection, via bypass or overwhelm, and the database is left exposed. ## Construct with Collaborators, Call with Work DevFeed: [Construct with Collaborators, Call with Work]() Original publisher: [Read original article]() Author: Google Testing Bloggers (noreply@blogger.com) Published: 2026-05-05T12:28:00Z Content type: tutorial Language: en Sources: [Google Testing Blog]() Topics: [Code](), [business logic]() Tags: [business-logic](), [code](), [shahar-roth](), [tott]() ### AI overview A coding guideline explains that long-lived dependencies should be supplied through a constructor, while inputs that vary for each operation should be passed to methods. A ReportGenerator example separates its database and formatter collaborators from a per-call date range. ### Source excerpt This article was adapted from a Google Tech on the Toilet (TotT) episode. You can download a printer-friendly version of this TotT episode and post it in your office. By Shahar Roth Classes require various objects and parameters to function. The "Construct with Collaborators, Call with Work" guideline can help you construct effective inputs: Use the constructor for collaborators--the dependencies that establish the object's identity. Collaborators stay with the object for its lifetime to enable it to fulfill its ongoing duties. Pass work--the parameters that change with each interaction--to methods. Unique to each call, these inputs provide the specific data needed for an operation such as a file path or database query. Consider a ReportGenerator that needs a database, a formatter, and a date range to generate a report. The database and formatter, as collaborators, are injected via the constructor, while dateRange, which varies per report generation, is passed as a method parameter to the generate method: class ReportGenerator { private final Database database; private final Formatter formatter; // database and formatter are passed as collaborators. ReportGenerator(Database database, Formatter formatter) { this.database = database; this.formatter = formatter; } // dateRange is passed as a parameter. Report generate(Range dateRange) { return formatter.format(database.getRecords(dateRange)); } } A single ReportGenerator object can generate multiple reports with different date ranges: ReportGenerator generator = new ReportGenerator(database, formatter); Report report1 = generator.generate(dateRange1); Report report2 = generator.generate(dateRange2); Following the "Construct with Collaborators, Call with Work" guideline promotes: Reusability: Enables instances to be used for multiple, distinct operations. Testability: Separates dependency setup from business logic. Cleaner code: Hides implementation dependencies from the object's users. Predictable behavior: Locks ## How Project Conventions Help AI Agents Write Go Backend Code DevFeed: [How Project Conventions Help AI Agents Write Go Backend Code]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-02-23T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [Go Language](), [Framework](), [Artificial Intelligence]() Tags: [ai-agents](), [apis](), [architecture](), [backend](), [business-logic](), [go](), [infrastructure]() ### AI overview The article argues that AI agents produce more consistent Go backend code when a project already provides conventions for service structure, typed APIs, and declared infrastructure. Without those conventions, agents must choose routers, middleware, connection handling, file layouts, error handling, and testing approaches, producing varied but valid architectures. ### Source excerpt And what happens when you actually let them. ## How Vinted Standardizes Large-Scale Decentralized Data Pipelines DevFeed: [How Vinted Standardizes Large-Scale Decentralized Data Pipelines]() Original publisher: [Read original article]() Author: Oscar Ligthart Published: 2025-12-29T00:00:00Z Content type: article Language: en Sources: [Vinted]() Topics: [Data Infrastructure](), [Orchestration](), [airflow](), [Cloud]() Tags: [airflow](), [business-logic](), [cloud](), [data](), [dependencies](), [domain](), [gcp](), [infrastructure](), [orchestration](), [pipelines](), [scale]() ### AI overview Vinted describes its migration to cloud-based data infrastructure and the challenges of coordinating dependencies across decentralized teams and domains. The article explains why relying on teams to hand-craft Airflow DAGs would add unnecessary complexity, and discusses adapting the conventional dbt-with-Airflow approach to Vinted's scale and cost constraints. ### Source excerpt TL;DR: How Vinted standardizes large-scale decentralized data pipelines. ## Simplify Your Code: Functional Core, Imperative Shell DevFeed: [Simplify Your Code: Functional Core, Imperative Shell]() Original publisher: [Read original article]() Author: Google Testing Bloggers (noreply@blogger.com) Published: 2025-10-20T13:53:00Z Content type: tutorial Language: en Sources: [Google Testing Blog]() Topics: [Code](), [IO]() Tags: [arham-jain](), [business-logic](), [code](), [database](), [email](), [function](), [functional](), [map](), [mutation](), [network](), [state](), [test](), [tott]() ### AI overview This tutorial explains the functional core, imperative shell pattern: keep pure, testable business logic separate from side effects such as database calls, network requests, email delivery, and external state mutation. It demonstrates the pattern by refactoring expiration-notification code. ### Source excerpt This article was adapted from a Google Tech on the Toilet (TotT) episode. You can download a printer-friendly version of this TotT episode and post it in your office. By Arham Jain Is your code a tangled mess of business logic and side effects? Mixing database calls, network requests, and other external interactions directly with your core logic can lead to code that's difficult to test, reuse, and understand. Instead, consider writing a functional core that's called from an imperative shell. Separating your code into functional cores and imperative shells makes it more testable, maintainable, and adaptable. The core logic can be tested in isolation, and the imperative shell can be swapped out or modified as needed. Here's some messy example code that mixes logic and side effects to send expiration notification emails to users: // Bad: Logic and side effects are mixed function sendUserExpiryEmail(): void { for (const user of db.getUsers()) { if (user.subscriptionEndDate > Date.now()) continue; if (user.isFreeTrial) continue; email.send(user.email, "Your account has expired " + user.name + "."); } } A functional core should contain pure, testable business logic, which is free of side effects (such as I/O or external state mutation). It operates only on the data it is given. An imperative shell is responsible for side effects, like database calls and sending emails. It uses the functions in your functional core to perform the business logic. Rewriting the above code to follow the functional core / imperative shell pattern might look like: Functional core function getExpiredUsers(users: User[], cutoff: Date): User[] { return users.filter(user => user.subscriptionEndDate <= cutoff && !user.isFreeTrial); } function generateExpiryEmails(users: User[]): Array<[string, string]> { return users.map(user => ([user.email, "Your account has expired " + user.name + "."]) ); } Imperative shell email.bulkSend(generateExpiryEmails(getExpiredUsers(db.getUsers(), Date.now()))); No ## Building Your First Kotlin Multiplatform App: From Setup to iOS App Store with Compose Multiplatform (2025 Guide) DevFeed: [Building Your First Kotlin Multiplatform App: From Setup to iOS App Store with Compose Multiplatform (2025 Guide)]() Original publisher: [Read original article]() Published: 2025-07-28T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [compose-multiplatform](), [Kotlin Multiplatform](), [Tutorial](), [cross-platform](), [iOS](), [Kotlin](), [Android](), [Jetpack Compose](), [Mobile](), [Deployment](), [Databases]() Tags: [2025](), [android](), [android-studio](), [app-store](), [architecture](), [build](), [business-logic](), [clean-architecture](), [compose-multiplatform](), [cross-platform](), [deployment](), [development](), [guide](), [implementation](), [ios](), [ios-development](), [kotlin](), [kotlin-multiplatform](), [multiplatform](), [setup](), [workshop-learning-programming]() ### AI overview A tutorial for building Kyklos, a Kotlin Multiplatform subscription-tracking app with shared Compose Multiplatform UI and business logic for Android and iOS. It covers project setup, Clean Architecture, SQLDelight database integration, Material Design 3, testing, and deployment. ### Source excerpt A comprehensive guide to building your first Kotlin Multiplatform app using Compose Multiplatform, covering setup, development, and deployment ## Announcing new Temporal training courses for .NET developers DevFeed: [Announcing new Temporal training courses for .NET developers]() Original publisher: [Read original article]() Author: Angela Zhou Published: 2025-02-19T00:00:00Z Content type: release Language: en Sources: [Temporal Blog]() Topics: [.NET](), [SDK](), [Error Handling](), [Tooling]() Tags: [announcements](), [business-logic](), [consistency](), [debug](), [deploy](), [developers](), [durability](), [error-handling](), [free](), [how-to](), [net](), [training]() ### AI overview Temporal announces that its Temporal 101, Temporal 102, and Crafting an Error Handling Strategy courses are now available for .NET developers. The free, self-paced courses cover durable execution, core concepts, architecture, production practices, debugging, deployment, durability, and error-handling strategies. ### Source excerpt Our Temporal 101, 102, and Crafting an Error Handling Strategy are now available in .NET. Take one of our free, self-paced, hand-on courses to learn everything you need to know about Temporal. ## Building resilient event-driven architecture for finance with Temporal DevFeed: [Building resilient event-driven architecture for finance with Temporal]() Original publisher: [Read original article]() Author: Tim Imkin Published: 2025-01-23T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [event driven](), [Architecture & Design](), [Orchestration](), [reliability](), [Scalability](), [Microservice](), [distributed-systems]() Tags: [business-logic](), [coupling](), [crashes](), [databases](), [distributed-systems](), [error-handling](), [event-driven-architecture](), [microservices](), [orchestration](), [reliability](), [retries](), [scalability](), [temporal-concepts]() ### AI overview This article examines the complexity of choreography-based event-driven architecture in financial services, including fragmented business logic, design-level coupling, decentralized error handling, and limited observability. It presents Temporal's durable execution and workflow orchestration as a centralized approach for building more resilient and maintainable systems. ### Source excerpt Discover how Temporal simplifies event-driven systems, replacing complexity with scalability, reliability, and centralized workflows. ## Enforce Flexible Governance in GraphOS using Custom Checks DevFeed: [Enforce Flexible Governance in GraphOS using Custom Checks]() Original publisher: [Read original article]() Author: Samuel Collard Published: 2024-11-26T12:00:00Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [GraphOS](), [API Governance](), [API Platform]() Tags: [api-governance](), [api-platform](), [business-logic](), [continuous-integration](), [graphos](), [graphql](), [schema](), [security-policies]() ### AI overview Apollo GraphOS supports custom schema checks that let organizations add business logic, security policies, and company-specific rules to the existing schema check workflow. The article introduces the governance use case and begins describing how to configure a custom check through an HTTPS endpoint. ### Source excerpt Apollo GraphOS now supports custom schema checks, a new feature that addresses API platform teams' demand for enhanced schema governance capabilities. This functionality allows organizations to integrate their own business logic, security policies, and rules into Apollo's existing schema check workflow, ensuring that every schema change adheres to company-specific standards. ## Automating Power BI Measure and Column Descriptions with a Tabular Editor Script DevFeed: [Automating Power BI Measure and Column Descriptions with a Tabular Editor Script]() Original publisher: [Read original article]() Published: 2024-08-09T00:00:00Z Content type: tutorial Language: en Sources: [Mutt0-ds Notes]() Topics: [Development](), [Script](), [Documentation](), [business logic](), [DevOps]() Tags: [business-logic](), [code](), [dev](), [devops](), [documentation](), [script](), [tutorial]() ### AI overview This tutorial presents a Tabular Editor script in C# that copies DAX code into the Description field for Power BI measures and calculated columns. It also discusses adding comments and ticket IDs for context, and describes a possible TMDL and DevOps pipeline alternative. ### Source excerpt "How does this MEASURE/COLUMN work?" This is one of the most frequent requests I was receiving. And it's easy to see why. In complex Power... ## How to Use User Location in Applications and Assess Its Limitations DevFeed: [How to Use User Location in Applications and Assess Its Limitations]() Original publisher: [Read original article]() Author: Austin Published: 2024-07-25T14:10:28Z Content type: article Language: en Sources: [Back End - Austin Gil]() Topics: [Programming](), [App]() Tags: [app](), [back-end](), [business-logic](), [coding](), [compliance](), [development](), [edge-compute](), [front-end](), [geolocation](), [html](), [ip](), [javascript](), [js](), [location](), [location-based](), [privacy](), [programming](), [software](), [web-development]() ### AI overview This article examines location-based programming, including use cases such as regional language, currency, store locators, weather data, and geofencing. It distinguishes user-experience, application-logic, and policy or compliance concerns, then discusses four ways to obtain location: user reporting, device heuristics, IP address, and edge compute. ### Source excerpt A post discussing the nuances around location-based programming. Various ways to access user location, how they can fail, and what to do about it. ## Effective Kotlin Item 20: Do not repeat common algorithms DevFeed: [Effective Kotlin Item 20: Do not repeat common algorithms]() Original publisher: [Read original article]() Published: 2024-01-29T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Programming](), [Algorithms](), [functions](), [Kotlin]() Tags: [algorithms](), [business-logic](), [functions](), [kotlin](), [optimization](), [sorting](), [standard-library](), [workshop-learning-programming]() ### AI overview This Effective Kotlin article explains why developers should extract common, non-project-specific algorithms into named utility functions or libraries. It argues that reuse improves programming speed, readability, maintenance, and consistency, while reducing noise and repeated implementation. The article recommends learning and using standard-library functions where appropriate. ### Source excerpt Why extracting utility functions is so important for our programs. ## Effective Kotlin Item 19: Do not repeat knowledge DevFeed: [Effective Kotlin Item 19: Do not repeat knowledge]() Original publisher: [Read original article]() Published: 2024-01-08T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Programming](), [data](), [Algorithm](), [business logic]() Tags: [algorithm](), [business-logic](), [code](), [programming](), [repeat](), [workshop-learning-programming]() ### AI overview This article explains why repeated knowledge in a programming project can be problematic. It connects copy-paste, DRY, WET, and Single Source of Truth practices, then distinguishes program logic from common algorithms based on how often they change. ### Source excerpt Why knowledge repetition is so problematic and how it relates to the single responsibility principle. ## Crash course on the Android UI layer | Part 2 DevFeed: [Crash course on the Android UI layer | Part 2]() Original publisher: [Read original article]() Author: Manuel Vivo Published: 2023-12-19T15:58:45Z Content type: tutorial Language: en Sources: [Bumble Tech]() Topics: [Android](), [ui](), [business logic](), [implementation](), [configuration](), [navigation](), [data](), [Requirements]() Tags: [android](), [android-app-development](), [apis](), [architecture](), [best-practices](), [business-logic](), [configuration](), [implementation](), [navigation](), [requirements](), [ui](), [viewmodel]() ### AI overview Part 2 of a series on the Android UI layer explains state holders, saving UI state, state hoisting, and the distinction between business logic and UI logic. It describes how these types of logic should respond to configuration changes. ### Source excerpt Crash Course on the Android UI Layer | Part 2State Holders and Saving 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. In part 1, we covered the UI and the UI state. You should already know the different entities present on the UI layer, and how to think about the UI and UI state effectively. Crash course on the Android UI layer | Part 1 Now it's time for Part 2! We'll cover state holders and other UI layer-related topics such as where to hoist state and save UI 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! State holders State holders simplify the UI by handling logic and/or exposing UI state. In this section, we'll see how to implement state holders and the implementation details to consider. To determine the implementation details, we first need to identify the types of logic commonly found in an Android app. Types of logic We have already discussed that business logic involves implementing the product requirements that specify how application data is created, stored, and modified. When business logic is present in the UI layer, it's recommended to manage this logic at the screen level. We'll see more of this later. Another type of logic is the UI logic. UI logic determines how to display state changes on the screen. While business logic dictates what to do with data, UI logic determines how to visually display it. The UI logic is dependent on the UI configuration. For instance, in a typical app, displaying a d ## Crash Course on the Android UI Layer | Part 2 DevFeed: [Crash Course on the Android UI Layer | Part 2]() Original publisher: [Read original article]() Author: Manuel Vivo Published: 2023-12-19T00:00:00Z Content type: article Language: en Sources: [Manuel Vivo .dev]() Topics: [Android](), [ui](), [saving](), [business logic](), [screen]() Tags: [android](), [architecture](), [best-practices](), [blog-post](), [business-logic](), [saving](), [screen](), [state](), [ui]() ### AI overview Part 2 of a series on the Android UI layer explains state holders, state hoisting, saving UI state, and the distinction between business logic and UI logic. It also discusses how UI logic responds to different device configurations, such as phones and tablets. ### Source excerpt Part 2 - State Holders and Saving State [Next page]()