# platform-teams Published articles for platform-teams. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Why your platform control plane belongs on Temporal DevFeed: [Why your platform control plane belongs on Temporal]() Original publisher: [Read original article]() Author: Joshua Smith Published: 2026-03-31T00:00:00Z Content type: opinion Language: en Sources: [Temporal Blog]() Topics: [control-plane](), [Automation](), [Orchestration](), [Terraform]() Tags: [automation](), [control-plane](), [error](), [infrastructure](), [orchestration](), [platform](), [platform-teams](), [provisioning](), [scripts](), [self-service](), [temporal-voices]() ### AI overview This article argues that Temporal can serve as a durable backbone for platform teams building internal control planes. It describes the difficulty of managing infrastructure across creation, monitoring, upgrades, configuration changes, and decommissioning, and contrasts Temporal's orchestration model with Terraform's declarative provisioning and reconciliation focus. ### Source excerpt Discover why platform teams use Temporal to build resilient internal control planes. Learn how Durable Execution solves brittle infrastructure automation. ## Exploring Temporal Cloud automation features DevFeed: [Exploring Temporal Cloud automation features]() Original publisher: [Read original article]() Author: Irina Belova Published: 2024-03-25T06:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Automation](), [Cloud](), [terraform provider](), [API](), [Infrastructure as code](), [API keys](), [certificates](), [Security](), [Authentication](), [Command-line interface](), [Kubernetes]() Tags: [api](), [api-keys](), [automation](), [certificates](), [cli](), [cloud](), [infrastructure-as-code](), [mtls](), [organizations](), [platform-teams](), [provisioning](), [security](), [temporal](), [temporal-concepts](), [terraform-provider]() ### AI overview Temporal Cloud's automation features support management of namespaces, users, access, account settings, and team onboarding. The article also describes API, Terraform provider, and Temporal Cloud CLI integrations, including automated mTLS certificate rotation and centralized governance for platform teams. ### Source excerpt Temporal Cloud Automation capabilities are transforming the way companies deploy, manage, and scale their operations in the Cloud. ## The Role and Responsibilities of Mobile Platform Teams DevFeed: [The Role and Responsibilities of Mobile Platform Teams]() Original publisher: [Read original article]() Author: Amanjeet Singh Gurtatta Published: 2023-05-03T18:56:29Z Content type: opinion Language: en Sources: [Amanjeet Singh]() Topics: [Mobile](), [Development](), [App]() Tags: [android](), [development](), [engineering](), [ios](), [mobile](), [monitor](), [platform](), [platform-teams]() ### AI overview This article examines how mobile platform teams emerge as organizations scale and encounter recurring issues such as slow app launches, crashes, increasing build times, and declining conversion. It explains that these teams address both technical and prioritization concerns, collaborate with product managers and analysts, and are not solely responsible for fixing every issue. ### Source excerpt Busting myths and bringing the reality of platform teams to light. ## The Fundamentals of Android at Revolut DevFeed: [The Fundamentals of Android at Revolut]() Original publisher: [Read original article]() Author: Revolut Published: 2023-03-17T09:48:42Z Content type: article Language: en Sources: [Revolut Engineering]() Topics: [android-development](), [Mobile](), [Gradle](), [CI/CD](), [Design system]() Tags: [android](), [android-app-development](), [android-development](), [ci-cd](), [design-system](), [fintech](), [gradle](), [mobile](), [mobile-development](), [platform-teams](), [product](), [programming]() ### AI overview The article describes how Revolut organizes and operates its Android development. It covers the Android engineering organization, Platform and Product streams, and the responsibilities of the Mobile Platform and Design System teams, including architecture, Gradle build performance, dependencies, CI/CD, releases, internal tools, libraries, analytics, testing, security, and reusable UI components. ### Source excerpt People deserve more from their money. More visibility, more control, more freedom. Since 2015, Revolut has been on a mission to deliver just that. With an arsenal of awesome products that span spending, saving, travel, transfers, credits, crypto, investing, exchanging, and more, our mobile super app has helped 25+ million customers send, spend, save, and invest smarter. Let's take a look behind the scenes of the Android development at Revolut and learn how we deliver our iconic apps to millions of customers all over the world. Dream team Our Android team is one of the best in the industry -- and we're proud of it. It's one of our driving forces: over a hundred excellent Android engineers work on our key products, such as Revolut for personal customers, Revolut Lite, Revolut Business, and Revolut < 18 for teens. At Revolut, we believe that building diverse, lean teams of brilliant go-getters who break down barriers, is the key to winning. That's why we have around 70 strong teams that split their work across two main streams: Platform and Product. The Platform stream consists of Design System and Mobile Platform teams, while the Product stream includes various product teams, such as the Onboarding team, Payments team, Trading team, Crypto team, Credit team, and more. Each team is made up of Product Owners, Designers, iOS, Android, Backend, and Frontend engineers who work together to deliver exceptional results. To better understand our teams and how they contribute to our success, let's take a closer look at their roles and responsibilities. Mobile Platform Team 👨🔧 Our Mobile Platform team is involved in a broad range of areas, such as building infrastructure, managing releases, maintaining architecture, and owning internal tools and libraries. The team upgrades projects configuration, particularly improve performance of Gradle Builds, maintains architecture, manages dependencies and keeps architecture sustainable, modernises CI/CD pipeline, facilitates mobile releas