# App Architecture Published articles for App Architecture. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Heroku Eventing: A Router for All Your Events DevFeed: [Heroku Eventing: A Router for All Your Events]() Original publisher: [Read original article]() Author: Kim Harrison Published: 2025-03-04T15:01:00Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [event driven](), [Publish-subscribe pattern](), [Authentication](), [API](), [Monitoring]() Tags: [api](), [app-architecture](), [architecture](), [authentication](), [event-driven](), [events](), [heroku](), [kafka](), [monitoring](), [news](), [observability](), [performance-optimization](), [product-features]() ### AI overview Heroku introduces Heroku Eventing, a pilot tool for managing, subscribing to, and publishing events across services. It provides a unified API, centralized event management, integrations with Heroku Kafka and Postgres, secure credential storage, and monitoring across connected sources. ### Source excerpt Managing event-driven architecture can be challenging. For many organizations, this includes a diverse set of eventing services and buses, often across multiple organizations. Developers must manage authentication and pub/sub services across teams and applications. We're thrilled to introduce Heroku Eventing, a powerful tool designed to help teams manage events more efficiently and securely. This new [...] The post Heroku Eventing: A Router for All Your Events appeared first on Heroku. ## Mastering API Gateway Integration: Salesforce, Heroku, and MuleSoft Anypoint Flex Gateway DevFeed: [Mastering API Gateway Integration: Salesforce, Heroku, and MuleSoft Anypoint Flex Gateway]() Original publisher: [Read original article]() Author: Julián Duque Published: 2024-07-29T18:00:00Z Content type: tutorial Language: en Sources: [Heroku]() Topics: [gateway](), [Heroku](), [API](), [Deployment](), [Security](), [Microservice](), [Cloud](), [Authentication](), [Authorization](), [Encryption](), [rate-limiting](), [Latency]() Tags: [api](), [api-gateway](), [api-security](), [apis](), [app-architecture](), [authentication](), [authorization](), [cloud](), [deployment](), [developer-tools](), [encryption](), [engineering](), [heroku](), [integration](), [integrations](), [latency](), [microservices](), [rate-limiting](), [salesforce](), [security]() ### AI overview A tutorial on deploying MuleSoft Anypoint Flex Gateway on Heroku to expose private APIs and microservices. It describes the gateway's API management, security, traffic management, rate limiting, and scalability capabilities, with possible integration with Salesforce. ### Source excerpt In today's fast-paced digital world, companies are looking for ways to expose their APIs and microservices to the internet while enhancing their overall API security. MuleSoft Anypoint Flex Gateway is a powerful solution that solves this problem. Let's walk through deploying the Anypoint Flex Gateway on Heroku in a few straightforward steps. You'll learn how [...] The post Mastering API Gateway Integration: Salesforce, Heroku, and MuleSoft Anypoint Flex Gateway appeared first on Heroku. ## Evolving the Backend Storage for Platform Metrics DevFeed: [Evolving the Backend Storage for Platform Metrics]() Original publisher: [Read original article]() Author: David Murray Published: 2024-05-09T22:00:00Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku](), [Back end](), [Time Series](), [Apache Cassandra](), [Kafka](), [stream-processing](), [autoscaling]() Tags: [apache-kafka](), [app-architecture](), [autoscaling](), [aws](), [backend](), [cassandra](), [cloud-infrastructure](), [data-analytics](), [database](), [developer-tools](), [engineering](), [heroku](), [kafka](), [metrics](), [performance-optimization](), [platform](), [platform-updates](), [stream-processing](), [time-series]() ### AI overview Heroku describes an infrastructure upgrade that migrated the storage backend for platform metrics. The article explains how MetaaS collects application observations, aggregates them into time-series statistics, and uses Kafka, stream-processing jobs, and Cassandra to support dashboard metrics, alerting, autoscaling, retention, and querying. ### Source excerpt One of our most important goals at Heroku is to be boring. Don't get us wrong, we certainly hope that you're excited about the Heroku developer experience -- as heavy users of Heroku ourselves, we certainly are! But, even more so, we hope that you don't have to spend all that much time thinking about [...] The post Evolving the Backend Storage for Platform Metrics appeared first on Heroku. ## Improved Heroku App Performance with HTTP/2 DevFeed: [Improved Heroku App Performance with HTTP/2]() Original publisher: [Read original article]() Author: Ethan Limchayseng Published: 2024-05-08T00:20:00Z Content type: release Language: en Sources: [Heroku]() Topics: [HTTP](), [Heroku](), [Latency](), [Compression](), [web applications](), [networking](), [TLS (Transport Layer Security)]() Tags: [app](), [app-architecture](), [cloud-infrastructure](), [compression](), [dynos](), [heroku](), [http](), [latency](), [networking](), [news](), [performance-optimization](), [platform](), [private-spaces](), [release](), [tls]() ### AI overview Heroku announces public beta support for HTTP/2 on Common Runtime and Private Spaces. The release uses multiplexing and header compression to reduce latency and improve web application performance, while HTTP/2 terminates at the Heroku router and traffic is forwarded to apps over HTTP/1.1. ### Source excerpt Introduction: We're excited to announce public beta support for HTTP/2 on both Heroku Common Runtime and Private Spaces. HTTP/2 support is one of the most requested and desired improvements for the Heroku platform. HTTP/2 is significantly faster than HTTP 1.1 by introducing features like multiplexing and header compression to reduce latency and therefore improve the [...] The post Improved Heroku App Performance with HTTP/2 appeared first on Heroku. ## 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 ## 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-13T00:00:00Z Content type: tutorial Language: en Sources: [Manuel Vivo .dev]() Topics: [ui](), [Android](), [App](), [business logic]() Tags: [android](), [app-architecture](), [architecture](), [save](), [ui]() ### AI overview This first part of a series explains Android's UI layer and UI state. It describes how the UI layer fits alongside the data and optional domain layers, and outlines the responsibilities of UI elements, UI state, and optional state holders. ### Source excerpt Part 1 - The UI and UI State ## Heroku's Next Chapter DevFeed: [Heroku's Next Chapter]() Original publisher: [Read original article]() Author: Bob Wise Published: 2022-08-25T19:58:00Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [GitHub](), [Buildpacks](), [Security](), [Availability](), [OAuth](), [Open Source]() Tags: [app-architecture](), [availability](), [buildpacks](), [compliance](), [customers](), [developer-experience](), [developer-tools](), [education](), [github](), [heroku](), [news](), [oauth](), [open-source](), [platform-updates](), [product-features](), [security]() ### AI overview Heroku outlines its next chapter, emphasizing support for customers, a public product roadmap on GitHub, a greater focus on mission-critical use, and continued open-source contributions. The company also announces the end of free product plans and deletion of inactive accounts, alongside planned student and nonprofit support. ### Source excerpt Back in May, I wrote about my enthusiasm to be part of the Heroku story, and I remain just as passionate today about helping write the next chapter. I've had many customer meetings over the past few months, and the theme is consistent -- you want to know where we are taking Heroku. We want [...] The post Heroku's Next Chapter appeared first on Heroku. ## Improving shared architecture for a Kotlin Multiplatform, Jetpack Compose and SwiftUI app DevFeed: [Improving shared architecture for a Kotlin Multiplatform, Jetpack Compose and SwiftUI app]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2022-06-26T00:00:00Z Content type: tutorial Language: en Sources: [Posts on Marco Gomiero]() Topics: [Kotlin Multiplatform](), [Jetpack Compose](), [SwiftUI](), [Kotlin](), [Mobile]() Tags: [android](), [android-jetpack](), [app](), [app-architecture](), [architecture](), [article](), [compose](), [coroutines](), [flow](), [ios](), [jetpack](), [jetpack-compose](), [kotlin](), [kotlin-coroutines](), [kotlin-multiplatform](), [mobile](), [multiplatform](), [mvvm](), [swiftui](), [viewmodel]() ### AI overview This tutorial explains how to improve a shared application architecture for Kotlin Multiplatform, Jetpack Compose, and SwiftUI. It replaces duplicated suspendable and non-suspendable methods plus platform-specific callbacks with Kotlin and Swift wrapper code that allows Swift to consume Kotlin Flow, enabling a single UseCase method that returns a Flow. ### Source excerpt A couple of years ago I started working on a pet project to manage personal finances, named MoneyFlow. This project soon became a personal playground for a Kotlin Multiplatform mobile app and in a previous article, I journaled all the steps that lead me to a satisfying (at least for that time) shared app architecture. Choosing the right architecture for a [new] Kotlin Multiplatform, Jetpack Compose and SwiftUI app ## VESIT: Building Apps For Android in Kotlin DevFeed: [VESIT: Building Apps For Android in Kotlin]() Original publisher: [Read original article]() Author: Siddhesh Patil Published: 2020-08-07T19:41:44Z Content type: article Language: en Sources: [Sid Patil - Android Engineer and Kotlin Advocate]() Topics: [LineageOS](), [Kotlin](), [Android Studio](), [android-development](), [Jetpack](), [Gradle](), [ui]() Tags: [android](), [android-development](), [android-studio](), [app-architecture](), [architecture](), [computer-science](), [developers](), [first-android-app-with-kotlin](), [gradle](), [how-to-build-apps-using-kotin-for-android](), [kotlin](), [siddhesh-patil-talks](), [talks-on-kotlin](), [tech-workshops-in-mumbai](), [ui](), [vesit](), [vesit-cmpn](), [workshop](), [xml]() ### AI overview A live Google Meet workshop at VESIT introduced computer engineering students to Android development with Kotlin. Participants used Android Studio to build a small app and learned about app architecture, views, data preparation, Gradle, Jetpack libraries, RecyclerViews, and debugging with logcat. ### Source excerpt Continuing our two-day session on kickstarting your journey to become Android developers, budding computer engineering students learn to build their very first app for Android using Kotlin. ## Introduction to Dependency Injection with Dagger for Java and Android DevFeed: [Introduction to Dependency Injection with Dagger for Java and Android]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2020-03-15T07:54:11Z Content type: tutorial Language: en Sources: [Shreyas Patil's Blog]() Topics: [Dagger](), [Dependency injection](), [Android](), [Code](), [Java](), [Framework]() Tags: [android](), [app-architecture](), [architecture](), [class](), [classes](), [code](), [component](), [constructor](), [dagger](), [dependencies](), [dependency-injection](), [di](), [getting-started](), [java](), [learn](), [object](), [others](), [parameter]() ### AI overview This tutorial introduces Dependency Injection and Dagger, explaining how Dagger is a static, compile-time framework for Java and Android. It uses a life-needs analogy and a sequence of dependent classes to demonstrate constructor injection and dependency creation. ### Source excerpt Demystifying Dependency Injection with Dagger. Learn DI concepts through real-life analogies and simplify your Android app architecture. ## Managing Massive View Controllers in iOS MVC Applications DevFeed: [Managing Massive View Controllers in iOS MVC Applications]() Original publisher: [Read original article]() Published: 2020-02-20T18:00:00Z Content type: opinion Language: en Sources: [Rambo Codes]() Topics: [mvc](), [iOS](), [iOS development](), [SwiftUI](), [Testing]() Tags: [app-architecture](), [apple](), [ios](), [ios-development](), [mvc](), [swiftui](), [testing](), [unit-tests]() ### AI overview The article discusses problems that arise when iOS MVC applications develop massive view controllers, tightly coupled screens, and difficult-to-write unit tests. It considers how to split view controllers while supporting older iOS versions and UIKit alongside SwiftUI. ### Source excerpt Gui Rambo writes about his coding and reverse engineering adventures. ## Encapsulating View State DevFeed: [Encapsulating View State]() Original publisher: [Read original article]() Published: 2019-07-19T16:00:00Z Content type: tutorial Language: en Sources: [Blogs on Ryan Harter]() Topics: [Android](), [business logic](), [Testing](), [App](), [Code]() Tags: [android](), [app](), [app-architecture](), [business-logic](), [code](), [error](), [livedata](), [messages](), [testing](), [viewmodel]() ### AI overview This article presents an approach to encapsulating view state in Android applications with AndroidX ViewModel. It explains how putting business logic and decision-making code in ViewModels can simplify Activities and Fragments and make the valuable code easier to test. ### Source excerpt The AndroidX ViewModel has become a central component in many modern Android apps. They offer a relatively simple abstraction to encapsulate business logic and decision making code which separates it from the platform frameworks, which are often difficult to test. Since ViewModels are easier to test than Framework classes like Activity and Fragment due to their simple lifecycles and lack of external dependencies, it makes sense to try to put as much logic, the complex decision-making code that should be tested, in ViewModels as possible. Ideally we'll be left with a view layer, either Activities, Fragments, or something else, which is so simple that it's not worth testing. ## MVVM with architecture components: a step by step guideline for MVP lovers DevFeed: [MVVM with architecture components: a step by step guideline for MVP lovers]() Original publisher: [Read original article]() Published: 2018-12-12T00:00:00Z Content type: tutorial Language: en Sources: [Antonio Leiva]() Topics: [Android](), [App]() Tags: [android](), [app-architecture](), [architecture](), [architecture-components](), [guide](), [mvvm](), [opinion]() ### AI overview This Android article explains MVVM to readers familiar with MVP, comparing how presenters and ViewModels communicate with views. It argues that MVP remains valid, MVVM is not necessarily better, immediate refactoring is unnecessary, and Android architecture components can generally still be used with MVP. ### Source excerpt Everything Android, Kotlin and other random topics ## Caviar iOS: Migrating from AdvancedCollectionView to PJFDataSource DevFeed: [Caviar iOS: Migrating from AdvancedCollectionView to PJFDataSource]() Original publisher: [Read original article]() Author: Square Engineering Published: 2016-06-13T16:11:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [iOS](), [Library](), [Framework](), [Code]() Tags: [app-architecture](), [architecture](), [engineering](), [ios](), [library](), [open-source](), [reuse]() ### AI overview This article explains how the Caviar iOS app moved from Apple's AdvancedCollectionView sample architecture to PJFDataSource. The team created an external library that retained the useful data-source patterns while reducing unnecessary complexity, then open-sourced it. ### Source excerpt Behind-the-scenes look at the evolution of PJFDataSource in our Caviar iOS app. ## Android Architecture: Introducing Dynamo DevFeed: [Android Architecture: Introducing Dynamo]() Original publisher: [Read original article]() Author: SystemDotRun Published: 2015-04-03T00:00:00Z Content type: article Language: en Sources: [SystemDotRun]() Topics: [Dynamo](), [Library](), [Development](), [Code]() Tags: [android](), [android-architecture](), [app-architecture](), [asynchronous](), [code](), [dynamo](), [libraries](), [lifecycle]() ### AI overview This introductory post presents Dynamo, a small library and wiki for Android application architecture. It focuses on managing application state and asynchronous code, including their interaction with the Android lifecycle, and aims to decouple UI behavior from core application logic. ### Source excerpt Dynamo has been superseded by Pilot Welcome, welcome. Come in, it looks mighty cold out there. The code is laying heavy across the hills, disorder rules the day and the nights are long. We yearn for a day where the suns shines forth once more. This is post #2 of my very short Android Architecture series (can two be a series?). Post #1 was a primer for this post. It contained A brief outline of the problems when defaulting to stock Android architecture. An overview of common general architectural concepts. This post is really a short intro to a small library + Wiki I have created. This library fills an architectural hole which I see in the Android dev world. There is no unified approach to generic Android app architecture and this creates a vacuum which sucks in well meaning devs and results is messy codebases strewn across the land. It is also my reponse to the many MVP blog posts out there, which have really helped me think about this issue but also I have my own take on. Plus, I feel sorry for new Android devs who are turning up later to the party and are overwhealmed by the Android ecosystem and need to get up to speed quickly on what these issues are before even getting to the point of thinking about potential solutions. Some of the issues addressed by this approach are solved by fantastic existing libraries, but again, I think for a large chunk of devs these can be difficult concepts to grasp and get running with. These are mentioned in the projects wiki for further reading. In my experience at least there are two core ideas around the center of most apps codebases. From the codebases I have seen & inherited both ideas seem to have too few brain cycles spent on them. 1. State Most apps and views are state-based however the spaghetti-level that captures the state logic is generally very high. 2. Asynchronous code Pretty much every app involves some asynchronous code. Pretty much every app allows this to touch the Android lifecycle. This always leads to sadness. ## Android Architecture: MV? DevFeed: [Android Architecture: MV?]() Original publisher: [Read original article]() Author: SystemDotRun Published: 2015-04-01T00:00:00Z Content type: opinion Language: en Sources: [SystemDotRun]() Topics: [Android](), [Code](), [mvc](), [Development]() Tags: [android](), [app-architecture](), [architecture](), [code](), [mvc]() ### AI overview This article examines how MV* architectural approaches relate to Android development. It argues that placing most application logic in Activities and Fragments can produce code that is difficult to test, read, refactor, reuse, and maintain through configuration changes, and introduces several common Android architecture perspectives. ### Source excerpt How do the MV* ways of thinking relate to Android? Why is this now such a popular way of thinking about Android architecture? The Problem I'm a contractor and I'm often brought on to projects have long since passed their first commit. I feel like I have had a good insight how to the average dev approaches Android app architecture from this, and also from open-source projects, android blog posts, the Android developer site and more. One thing that strikes me about most of the code I see is that there is not much of a notion of a clean, overarching application architecture. By this I mean that people seem genuinely happy to shoehorn their code into Activitys & Fragments with the occasional class named something like MyCrazyController. Why is this an issue? The problem with this is that it results in hard to test code hard to read code hard to refactor code hard to reuse code hard to handle-config changes code hard to write asynchronous code hard to not create loads of edge-case code (i.e. its buggy) hard to hand-over code Its an easy thing to fall into doing because ~99% of all Android examples are written in this way It sort of works most of the time there are framework classes (i.e. Loaders) and librarys (i.e. RoboSpice) around now to work around some of the issues that manifest from using this stock approach. While I have used these approaches in the past I find they can make a code base more complicated than it needs to be. People have got used to hearing that "Android is hard to test" or "just lock it to portrait" and "restart / reconnect to the web service call on rotation" and just think "well thats how it is" I admit, I would also include my past-self into this group, which is why I am here, attempting to atone for my coding sins and mine and others unknowingly devout following of the book of anti-patterns. How has this come to be? MV?, who's in control? I believe a big part of this is that not much thought has gone into the actual generic app architecture app